Closed dshokouhi closed 1 year ago
bdraco
commented
2 years ago Since we don't have a parser for this model yet, to add support usually it means plugging in a probe, warming it up and seeing what changes, then doing that for the next one until you can identify where all the data is in the advertisement
bdraco
commented
2 years ago Or find a lib that has already added support for it and use that as a template
dshokouhi
commented
2 years ago I just found this issue, seems like this model may not be able to be supported?
bdraco
commented
2 years ago 16473: b'[\x00d\x81 \xff\xff\xff\xff\xff\xff \xff\xff\xff\xff\xff\xff\x00\x00' sure looks like its the temp data but you'd have to experiment to see if it changes
dshokouhi
commented
2 years ago ok I think I got the data right but not 100%, I did some hand warming to take the temp from 84 to 93 😂
bdraco
commented
2 years ago It does look like the data is changing in response but reading it isn't obvious like some of the other devices.
I think its rotating the data like the H5184
This one isn't strait-forward to add support for unfortunately. I'd probably need the device and a few hours to figure it out. That is a bit more time than I'm willing to commit to this, but I'm happy to review and merge a PR to add support for it if you are motivated to figure it out
dshokouhi
commented
2 years ago no problem appreciate the time you already took on this 🙏
DigiH
commented
1 year ago Hi all,
we've had the H5055 implemented for a while now, and yes, it is a bit awkward as it only ever sends two temperatures per message, rotating three messages for all six probes (1&2, 3&4, 5&6), indicating which probes are being sent by two bits (bit[3-2] of index 10 in our case, likely index 6 for you!?). Also sending "ffff" for the two temperature octets when no probe is connected to the appropriate socket.
https://github.com/theengs/decoder/blob/development/src/devices/H5055_json.h
Hope this helps.
ADDENDUM: Actually looking at the above data from @dshokouhi , with the first likely having all 6 probes not connected and the second only with probe 1, and so on
5b00648120ffffffffffff20ffffffffffff0000 all probes disconnected
5b006401201c00ffffffff20ffffffffffff0000 - probe 1 = 28ºC
5b00644820ffffffffffff201f00ffffffff0000 - probe 4 = 31ºC
…
it seems that this model does send all 6 probe temperatures in one go. Likely a new format for the H5055 models, indicated by the device id 20 at index 8 and index 22, where previously these two had the device id 06.
@dshokouhi could you also connect probe 3 and 5 only, Probe 1&2 (will index 7 be 3?), 3&4 and 5&6 and give some readings, as it seems that there is also the same two probe temperatures only message rotation here?
Extrapolating from how I think the bits of index 6 and 7 (10 and 11 in our case) - bits[5-0] indicating each probe 6-1 - indicate the probe rotation in this new format I have extended our decoder as a test
Would need more confirmation with the requested readings above.
Actually seems to be the very same decoder as our previous implementation, just with the new device identifying 20. Needed to fully get my head around this again as well :)
https://github.com/theengs/decoder/commit/9c80ee80935ea77267c48f9b6dbf65a3fbd37ec5
And credit where credit is due - with @BastiJoe's very helpful diagram for implementing the original decoder https://github.com/BastiJoe/govee_h5055_mqtt/blob/main/govee_2.png
Describe the bug A clear and concise description of what the bug is.
Just got a new device but it did not get picked up
To Reproduce Steps to reproduce the behavior:
Just turn on the device
Additional context Add any other context about the problem here.
Not sure what other data is needed, hopefully this can be added :) please let me know if I am missing anything.