So you still need to pull the properties to get that reported. An example is that the lock gives all the info that we would need in home assistant in the device list, except p2002 which reports the jammed status. Ie: hitting one endpoint once every x seconds vice once per device every x seconds (obvious exponential load). Ideally, the home assistant integration could just query the device list to populate the states for all the devices at once. Unfortunately, not all off the pertinent states that are returned from the device properties endpoint are populated there. Ultimately, the easiest way would be to query the device list endpoint and extract the states from the device_params field. Sorry, I hurt your feelings but there is a correct way to air your grievances and this is not been trying to help come up with a way to limit the load that this HA integration has caused. I hope that I do not need to continue to defend myself in public from someone who seems to have no problem lying about me to anyone who will listen. Since you didn’t bother to run MOSS I have to assume that it did not show the result that you want. When two people reverse-engineer (rip-off) an algorithm from another piece of code it is obvious that they would be the same. If even one step is wrong it will not work. The signiture2 code is a cryptographic dance that takes place to generate the exact string that the Wyze servers are expecting. The similarity that you are seeing is likely that both algorithms have to produce the same outcome. so file, and opening it up in hopper to try to understand the assembly. I ended up purchasing Hopper disassembler and going down the same route that you took, decompiling the android apk, finding the. Please do make a ha integration and no need to credit me. Maybe I’ll “go in a different direction” and write my own Home Assistant plugin that copies all your code and any missing attribution will just be “an oversight.” Except, you “forgot” to do that while copying and pasting my algorithm and all of the understanding of the newer wyze endpoints that I figured out. Things were left amicable between us with the understanding that you would credit all of my work wherever you used it. certainly didn’t do that work and even stated that he wasn’t able to (see Wyze Vacuum I challenge anyone else to outline where in the wyze app that all came from and how it was cracked. The entire signing algorithm (hmac’ing the hashed concatenated key and secret) for the Signature2 header (which is the crucial part of being able to use all the newer endpoints) is ENTIRELY my work. The only thing that I used from your investigations was the signing secret and app id OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,ĮXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF Relinquishment in perpetuity of all present and future rights to this We intend this dedication to be an overt act of Of the public at large and to the detriment of our heirs and Of this software dedicate any and all copyright interest in the In jurisdictions that recognize copyright laws, the author or authors Your accusations against don’t seem particularly compatible with the license you used for your code shauntarves/wyze-sdk/blob/master/LICENSE This is free and unencumbered software released into the public domain.Īnyone is free to copy, modify, publish, use, compile, sell, orĭistribute this software, either in source code form or as a compiledīinary, for any purpose, commercial or non-commercial, and by any I wish that my oversight had not damaged your opinion of me but it appears that feelings have festered. You have my personal contact information and could have addressed this with me 1 on 1. OLIVE_APP_ID = '9319141212m2ik' # Required for the thermostatĪddressing the concern that I “ripped off all your code” I would suggest that you run the MOSS system on our codebases and see for yourself Detecting Plagiarism. OLIVE_SIGNING_SECRET = 'wyze_app_secret_key_132' # Required for the thermostat I apologize that you were not recognized for this contribution and will add your name to the readme. I ended up doing significant work on reverse engineering on my own the only thing that I used from your investigations was the signing secret and app id (I had a hard time deriving this). I have not stolen any of your intellectual property… whatever that means in the case of open source. I thought that we ended our discussions amicably however that must not be the case. The code for wyzeapy has been public for a long time.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |