-
Notifications
You must be signed in to change notification settings - Fork 480
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
Support info for implementing Fan coil Thermostat, Beok TGR87G-WIFI-AC2 #465
Comments
Hi, I'm trying to develope the support for this Thermostat, and currently using the Hysen climade device as a reference. I'm able to send requests with the send_request() and some are working, like set_power(), but most of the reading information, like get_full_status(), or get_temp() is readback but not valid (temps, times, ...). I don't know where to get the information on how the response_payload is coded and structured in the frame. Is there any Broadlink documentation available? Could someone guide me on how to get the payload information codification, so I can implemented the decodification and usage in the library? How people does for other Broadlink devices? Thanks a lot for the support! |
Hi there. Thanks for your dedication to this. The official documentation serves us better to understand what they are doing than how they are doing it. There is no shortcut, you need to look at the bytes and try to understand what they mean. One thing I usually do is to compare an old message with the new message to understand the changes. It usually doesn't change much. A pattern that I am seeing over and over: in the new devices the payload is being preceded by its length, example: b'\x04\x00\x00\x00' Becomes: b'\x04\x00\x04\x00\x00\x00' This is what happened to RM2/RM4 and SP4/SP4B, and it will continue to happen because this is how the new version of the protocol works. So that's where I would start looking. |
lockmode = (payload[3] & 0x0f); |
Hi,
I have a Fan coil Thermostat, Beok TGR87G-WIFI-AC2, which is not supported by the library. Is there any plan to add support to this Broardlink Thermostat?
I debugged a little bit the library with my Thermostat and “devtype” reported is 0x4F5B. I can provide more debug information from the device, if needed! But I don't know what else should be checked, or done, to add support to it.
Thanks for your support!
The text was updated successfully, but these errors were encountered: