-
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Looks like protocol is changed in newest devices #6
Comments
Taken from the readme:
What is the model ID of your device? |
@yobushka you can try this forked version @Hypfer Thank you for your great work! AFAIK the model ID and packaging label of this device not changed, but internal hardware and software changed a little with time. I have two of this with different manufacturing dates. Older one working OK with your firmware, newer one works only with this fork. I have patched it to get back Homeassistant integration and device naming scheme. |
Hi! I have the same issue with home assistant. One more thing: it would be nice, if the devices web page had at least a power button. |
i turn esp82xx device into web-terminal, and try to figure out, - why control messages is not working, and status is also, not updating...
so on terminal line (after inital steps with my typing of "ok" and "cloud"), i found something like this:
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 2 1 truee
properties_changed 7 1 false
and many lines like that...
there is no long string containg status anymore...
So i think it's no working with newer devices anymore...
The text was updated successfully, but these errors were encountered: