Added error handling for invalid or corrupt address in sensor responses & fixed _ClimateParser incorrect data format

[sdegeorgio]

This pull request adds exception handling for three issues I experienced when I tried using bridge_tool_cli.py.

1. When opening the /dev/hidraw0 the Dongle would send an event log with timestamp=0 (clock not yet synchronised) which would throw an exception immediately on startup.
2. I had a sensor which had a corrupt MAC address programmed into it. When attempting to scan / pair it would cause the script to throw various exceptions and these are all addressed.
3. Fixed _ClimateParser incorrect data format, an exception was previously being thrown when a climate event occurred.

[raetha]

@sdegeorgio I'm going to merge this into the devel branch now. If you could do one final check from that branch that everything still works as expected I'll roll this into the master branch shortly after.

[sdegeorgio]

I've just tested the bridge_tool_cli and its working with no crashes but the leak/humidity sensor alarm is not handled, and this is the output:
Action:WARNING 2025-11-12 11:13:54,751 Unexpected sensor (03) for event E8
[2025-11-12 11:13:54][79F732CE]: type=unknown:E8

I've also tested the devel branch copied into the docker container to run with HA, with and without this pull request and I am seeing a crash when my leak/humidity sensor sends a humidity alarm, whereas on master the crash does not happen. I'll dig into it some more, but I probably wouldn't promote until this is fixed.

FYI I am using WyzeSense V1 NEOS door/window, PIR and leak/humidity sensors and dongle.

[raetha]

That’s sounds like one of the changes for v3.1 that I staged a couple days ago from devel must have an issue. I haven’t tagged that yet in the main branch so it’s still pushing 3.0.x via Docker. If you switch your Docker tag to “devel” you can skip copying stuff into the container, though backup your config first just in case.I’ll glance through the commits that were originally queued up for 3.1 and see if something looks off.Could use help though as I don’t have a NEOS setup to test with, and definitely want to keep that working. Worst case I can roll back the 3.1 changes and then apply your fixes to get stable in main.-eli--Sent from my iPhoneOn Nov 12, 2025, at 06:18, Stephan de Georgio ***@***.***> wrote:sdegeorgio left a comment (raetha/wyzesense2mqtt#92) I've just tested the bridge_tool_cli and its working with no crashes but the leak/humidity sensor alarm is not handled, and this is the output: Action:WARNING 2025-11-12 11:13:54,751 Unexpected sensor (03) for event E8 [2025-11-12 11:13:54][79F732CE]: type=unknown:E8 I've also tested the devel branch copied into the docker container to run with HA, with and without this pull request and I am seeing a crash when my leak/humidity sensor sends a humidity alarm, whereas on master the crash does not happen. I'll dig into it some more, but I probably wouldn't promote until this is fixed. FYI I am using WyzeSense V1 NEOS door/window, PIR and leak/humidity sensors and dongle. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you modified the open/close state.Message ID: ***@***.***>