Open robvanoostenrijk opened 2 months ago
Thank you!
'genPollCtrl' is disabled. Some coordinates set a constant "longPollInterval" period of 6 seconds or less, ignoring the "longPollIntervalMin" value (=10 sec). This greatly affects consumption. Current implementations of Zigbee programs are a complete mess. 'genPollCtrl' has been removed and a fixed value equal to "measurement Interval" has been applied. And this can lead to other consequences for some coordinators and routers... Z2M and ZHA do not fully support the Zigbee 3.0 specification.
In Z2M, settings are made by device name, and not by program version, manufacturer identifiers and device hardware version. Although OTA works based on the device's digital identifiers. This causes conflicts with different versions of Zigbee devices, including Tuya and devices from other manufacturers. There are no such problems in ZHA. And users do not need to be able to program special scripts for typical Zigbee 3.0 devices. Users need to beg to register a new Zigbee 3.0 device in Z2M :)
@pvvx,
I've updated and consolidated the external converter code for Z2M and aligned it to v.0.1.2.1+ specifications:
This is tested against CGDK2 and TS0201_TZ3000. However, I already put in the definitions for devices with comfort display (but unable to test). Someone with such a device should be easy able to create the definition with the below code however.
Additionally it should support both '-z' and '-bz' devices.
pvvx-zigbeetlc.js.txt