BHT-002-GCLZB Floods with identical messages

Hello,

i have been testing a BHT-002-GCLZB room thermostat for a while now. Overall, it is a nice device and seems to work reasonably well, but it does flood the controller with near identical messages.

I found chains of 50 messages within 2.5 s (roughly 50 ms between two messages) with a payload with is identical save for the ‘transid’ entry, which increases by one for each message (as it must, as far as i understand the protocol)

I have seen this happen with two messages, one reporting the ‘current_heating_setpoint’, the other one reporting the ‘heat’ setpoint.

Any suggestions on how to stop this flood of messages to reach the application ?

I have attached 2 files below - one a raw Log file from the application, run for about 1 minute and a second where i edited the log to only show the message and the effect it has on the application.

An ideal way would be if we could somehow stop this flood on the device, but seeing that it is a TuYa based design i have low hope of that. Is there any way for the converters to drop the repeat messages ?

I have been playing around with storing the message id and checking against the previous to block the repeat messages in the converter, but that is rather late in the chain, and i was wondering if there was a better way to do this.

The code i added was this (inside the moesThermostat function, and of course the lastMoesThermostatMessage variable is defined globally)

if (lastMoesThermostatMessage && lastMoesThermostatMessage.dp == dp) { lastMoesThermostatMessage = msg.data; return; } lastMoesThermostatMessage = msg.data;

Zigbee_Log_edited.txt Zigbee_Log_raw.txt

[asgothian]

Seems this is known and not fixable. I made an attempt to reach technical people at the manufacturer but was not successful. Closing the issue.

[AndrelaS]

For BHT-002-GBLZBW topic …/sensor: 0 - IN, 1 - AL, 2 - OU