KC
KC
same thing here, but with docker@debian and using mode:host.
already done...
> What do you mean with misunderstood? This info comes from the device, it seems the changed the numbering scheme. Installed version date: 07/07/2020 new available firmware date: 05/30/2023 but...
``` Debug 2023-06-14 20:32:29Received MQTT message on 'zigbee2mqtt/bridge/request/device/ota_update/check' with data '{"id":"ikea_switch_1","transaction":"cp5ya-1"}' Info 2023-06-14 20:32:29Checking if update available for 'ikea_switch_1' Info 2023-06-14 20:32:29MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Checking if update available...
you're right, sorry. ``` Debug 2023-06-14 20:42:15Received Zigbee message from '0xa4c138c6273ef6db', type 'attributeReport', cluster 'haElectricalMeasurement', data '{"rmsCurrent":35}' from endpoint 1 with groupID 0 Info 2023-06-14 20:42:15MQTT publish: topic 'zigbee2mqtt/0xa4c138c6273ef6db', payload...
surely that's an anomaly - not z2m side, I mean. ok, I'll try
> Thanks for the fast reply. > > Yes I'm sure (tripple checked) that I've used the NCP build. Right now I'm on 8.0.2 and it looks stable, so sticking...
will test it very soon!