* Added function to override payloads for non-conforming devices
* override implementation for Bosch BTH-RA
* unit test including mockup for this device
* Experimental and broken integration of overrideHaConfig
* Not working experiments; mqtt publish debug output
* fixes
* Updates
* fix
---------
Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* fix: OTA loses version info for develco/frient
This fix is not perfect, as it will still print that it got updated from null to null.
We just moved the reconfigure later, which will trigger this https://github.com/Koenkk/zigbee-herdsman-converters/blob/000041cba216822dab151151c493b560678da91a/src/devices/develco.ts#L36
for develco/frient devices that have it in their configure. (Which should be all of them)
Of note though, ZCL marks both dateCode and swBuildId as optional attributes, so Develco/Frient returning UNSUPPORTED_ATTRIBUTE here is not outside of spec. Although I'm not sure there is a cleaner way to do this.
* Update otaUpdate.test.js
* Update otaUpdate.ts
---------
Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* exclude homeassistant entries from null cleanup
* Add a test
* Don't hardcode the exclude list, add one more test
* implement suggested changes as per review
* Differentiate the spammy "MQTT publish"/"received MQTT message" from regular logs
Rather than creating subnamespaces, keep the z2m:mqtt logger namespace only for those 2 , move back to z2m default for the rest.
* fix tests
* POC: Allow hierarchical filtering of logger namespaces
matches the closes defined namespace log level:
advanced:
log_namespaced_levels:
'zh:zstack:unpi': info
would also apply to zh:zstack:unpi:write and zh:zstack:unpi:parse
To limit runtime penalty uses the namespacedLevels as a lazy cache
* Move namespace levels to separate cache
Avoid poluting the namespacedLevel in the config / UI
Add cache reset on config time log level change
* Actually use the cache
* Optimize/Cleanup
* Add some namespace hierarchy filter tests
* More coverage.
* Fix#22935
---------
Co-authored-by: Nerivec <62446222+Nerivec@users.noreply.github.com>
'occupancy' matches the zigbee terminology more closely and is more
consistent with other Home Assistant entities of this type.
https://www.home-assistant.io/integrations/binary_sensor/
In general, it looks like 'motion' is more for alarms, and 'occupancy'
for non-alarm situations. Z2M currently makes no distinction between
these concepts, but they could be separated (with a fair amount of work).
* feat: add api for device re-interview
- Adds an API that allows for the re-interview of a device. This can be
useful a device firmware upgrade adds new device endpoints (as is the case
when upgrading an Inovelli VZM31-SN to 2.18). Without the ability to
re-interview, one must remove and re-add the device.
* rename from reinterview to interview
* publish devices after interview.
* only allow device ids or names, not endpoints
* (feat) Expose Custom Clusters in MQTT
- Introducing bridge/definitions
- Updating test case for custom clusters
- Updating new path after ZCL revamp with 0.47.0
This change is needed for nurikk/zigbee2mqtt-frontend#2001
* Fixing test case
* Update lib/model/device.ts
Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* Update test/bridge.test.js
Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
* Removing the publishDefinition call from some events. updating tests
---------
Co-authored-by: Koen Kanters <koenkanters94@gmail.com>
Koen Kanters