Closed adriannowaq closed 2 years ago
Try changing the values for payload1 - at that setting, any change in the sensor will be reported.
You probably want to crank up the maximum report interval on payload2 and change your reportable change to something more meaningful...
I'd suggest the following:
const payload1 = [{
attribute: 'measuredValue',
minimumReportInterval: 10,
maximumReportInterval: 3600,
reportableChange: 100,
}];
const payload2 = [{
attribute: 'measuredValue',
minimumReportInterval: 10,
maximumReportInterval: 3600,
reportableChange: 100,
}];
This would report changes between 10 seconds and 1 hour with a change in value of +/- >100 units
Testing right now, and there is no difference
Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msTemperatureMeasurement', data '{"measuredValue":2817}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0 Debug Received Zigbee message from '0x60a423fffe44d3f3', type 'attributeReport', cluster 'msRelativeHumidity', data '{"measuredValue":6469}' from endpoint 1 with groupID 0
The same situation occurs when I click button on device once, or while paring. It keeps spamming, my CC2531 crashes because of that
Have you removed your device from the network and restarted Zigbee2MQTT then re-added it? It will have to go through the configuration process in order to change the values from what you have set
Of course I did
Do you have access to the Zigbee2MQTT frontend? could click on the device in question, go to the reporting tab, and post up a screenshot?
Bear in mind that this sensor is spaming when it's pairing and when I click button on it, but also sometimes when I do nothing.
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days
I have an issue with RH3052, it's randomly spamming with messages:
My converter:
Because of that, my CC2531 crashes, with BUFFER_FULL error, How can I fix it?