Skip to content
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

Correct datatypes for MsgID 30, 38, 78 and 107 #21

Closed
BernoldNL opened this issue Jan 20, 2023 · 2 comments
Closed

Correct datatypes for MsgID 30, 38, 78 and 107 #21

BernoldNL opened this issue Jan 20, 2023 · 2 comments

Comments

@BernoldNL
Copy link

Hi Schelte,

Please let me introduce myself first. I wrote a free OTGW plugin for HomeSeer HS4, based on the realtime (PS=0) messages. It just got released by HS. The plugin supports as many MsgIDs as possible.

During development I came across a few MsgIDs that did not entirely make sense: 38, 78 and 107. The register data types are defined as u8/u8, while their description only has 1 value. In my code for now I have assumed MsgID38 and MsgID78 (humidity) are f8.8 and MsgID107HB is u8, comparable to MsgID12.

And then there is MsgID30, which is defined as both s16 and f8.8 in the old 2.2 protocol. i think f8.8 is a copy/paste error, as s16 matches the -40..250 range which is unique and therefore less likely a copy/paste error.

Do you possibly have more information on these MsgIDs? Maybe from uploaded logs on your website? (Or newer protocol documents?)

Best regards,
Bernold

@hvxl
Copy link
Owner

hvxl commented Jan 21, 2023

You are correct that those MsgIDs should not be u8/u8. Your guesses of what they should be are mostly correct too. The exception is MsgID 78. That is nu/u8.

Information in the spec about MsgID 30 is indeed contradictory. But the range doesn't fit in any number format other than s16. So I agree that must be the correct format.

I will update otmonitor. Thanks.

@BernoldNL
Copy link
Author

Thank you for your quick response and your information. I will update my plugin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants