Good to know, It must be coding in HA then thats not pulling in/allowing the data for binary_sensors.
I dont have any other binary_sensors that use a battery level to test with.
Good to know, It must be coding in HA then thats not pulling in/allowing the data for binary_sensors.
I dont have any other binary_sensors that use a battery level to test with.
retain: true
for the TRADFRI bulb to have the state on startup. See link
Hi, yes I added the retain: true and it seems to have done the trick thanks!
Thanks @Koenkk,
could you possibly review this other post that I made after that one: Zigbee2mqtt: getting rid of your proprietary Zigbee bridges (Xiaomi, Hue, TRADFRI) ?
Would like to know your feedback?
Hello everyone,
I have 2 ikea bulbs that were correctly paired but have started to act up a bit. Is there anyway one can double check whether they are still in the network? a sort of a āzigbee layer pingā?
The z2mqtt addon does see them while starting up.
thanks
Thatās what I thought, but today I came across this video and all of the sudden I started to wonder whether I was doing something wrong: https://youtu.be/uhMrcIAdGxg
Good tip!! many thanks @Koenkk
@Koenkk, there is something fishy with the uplink from my home system towards my router devices. Initially I thought that the problem was limited to IKEA bulbs acting up a bit, but Iām now just through with setting up a Xiaomi power switch, with same results.
Here you can see how the two bulbs wonāt accept orders comming from HA
2018-7-30 02:03:24 WARN Cannot handle MQTT message with topic āzigbee2mqtt/kitchen.light.1.tradfri/setā and message ā{āstateā: āONā}ā
2018-7-30 02:03:48 INFO MQTT publish, topic: āzigbee2mqtt/kitchen.occupancy.xiaomiā, payload: ā{āoccupancyā:false}ā
2018-7-30 02:04:45 WARN Cannot handle MQTT message with topic āzigbee2mqtt/corridor.light.1.tradfri/setā and message ā{āstateā: āONā}ā
2018-7-30 02:04:45 WARN Cannot handle MQTT message with topic āzigbee2mqtt/corridor.light.1.tradfri/setā and message ā{āstateā: āONā}ā
Zigbee2MQTT seems to recognize them as valid devices when it starts up:
2018-7-30 01:13:18 INFO kitchen.light.1.tradfri (0x000b57fffedc1058): LED1623G12 - IKEA TRADFRI LED bulb E27 1000 lumen, dimmable, opal white (Router)
2018-7-30 01:13:18 INFO corridor.light.1.tradfri (0x90fd9ffffe4bf6fd): LED1545G12 - IKEA TRADFRI LED bulb E26/E27 980 lumen, dimmable, white spectrum, opal white (Router)
same with the freshly installed power switch:
2018-7-30 02:53:03 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
2018-7-30 02:53:10 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
2018-7-30 02:53:18 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
2018-7-30 02:53:43 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
2018-7-30 02:53:43 INFO Zigbee: allowing new devices to join.
2018-7-30 02:53:48 INFO Zigbee: disabling joining new devices.
2018-7-30 02:53:56 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
but when I manually switch the power switch on, HA gets updated (the UI reflects it by flapping the radio button). This is what leds me to think that the communication path between the usb stick and the devices is somehow experiencing problems, while the retune path seems to work just fine: I see accupancy sensors information being displayed in HA, door sensors do appear in HA just right too, and now seeing that the power switch informs HA as well.
Iāve now switched the debug level to ādebugā but I donāt get much more information on what is going on, apart of the message I reported earlier:
2018-7-30 10:37:42 INFO Switching log level to 'debug'
2018-7-30 10:37:50 DEBUG Check online 0x000b57fffedc1058
2018-7-30 10:37:50 DEBUG Check online 0x90fd9ffffe4bf6fd
2018-7-30 10:37:50 DEBUG Check online 0x00158d00022f35ca
2018-7-30 10:37:56 DEBUG Recieved mqtt message on topic 'zigbee2mqtt/power-plug.1.xiaomi/set' with data 'ON'
2018-7-30 10:37:56 WARN Cannot handle MQTT message with topic 'zigbee2mqtt/power-plug.1.xiaomi/set' and message 'ON'
2018-7-30 10:38:50 DEBUG Check online 0x000b57fffedc1058
2018-7-30 10:38:50 DEBUG Check online 0x90fd9ffffe4bf6fd
2018-7-30 10:38:50 DEBUG Check online 0x00158d00022f35ca
2018-7-30 10:39:50 DEBUG Check online 0x000b57fffedc1058
2018-7-30 10:39:50 DEBUG Check online 0x90fd9ffffe4bf6fd
2018-7-30 10:39:50 DEBUG Check online 0x00158d00022f35ca
2018-7-30 10:40:50 DEBUG Check online 0x000b57fffedc1058
2018-7-30 10:40:50 DEBUG Check online 0x90fd9ffffe4bf6fd
2018-7-30 10:40:50 DEBUG Check online 0x00158d00022f35ca
2018-7-30 10:40:55 DEBUG Recieved zigbee message with data {"cid":"genBasic","data":{"65281":{"3":34,"5":12,"7":"0x0000000000000000","8":4886,"9":256,"100":0,"149":0.0014568129554390907,"150":2240,"152":0,"154":16}}}
2018-7-30 10:40:55 INFO MQTT publish, topic: 'zigbee2mqtt/power-plug.1.xiaomi', payload: '{"state":"OFF","power":0,"voltage":224,"consumption":0,"temperature":34}'
2018-7-30 10:40:55 DEBUG Recieved zigbee message with data {"cid":"genBasic","data":{"65281":[null,null,null,null,null,12,null,"0x0000000000000000",4886,256,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,0,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,null,2240,null,0,null,16]}}
2018-7-30 10:41:50 DEBUG Check online 0x000b57fffedc1058
I donāt see much information around the relevant message:
2018-7-30 10:37:56 WARN Cannot handle MQTT message with topic āzigbee2mqtt/power-plug.1.xiaomi/setā and message 'ONā
Does anybody have any experience with similar behaviour with Routers? Can anybody please advice what to do?
Thanks
Iāve been having 2 issues with my TRADFRI lights so far.
First of all, some of my lights keep trying to repair with my zigbee router and flashing.
This shows up in the log:
spinlock: false []
device already in network
Any ideas why this is happening?
Second of all, Iāve been having quite a bit of lag with some of the lights. When I try to turn on/off a light group, most of the time, only a few of the lights in the group turn off, while the rest need a few tries to actually turn on/off. Iāve checked the wifi channel in my apartment and itās on 1, but due to living in a small apartment, there is a lot of other 2.4GHz wifi channels in the area, some on channel 11 too. Is there anything I can do to reduce the lag? It didnāt seem to happen when I used the TRADFRI gateway though.
My Ikea bulbs do that I think, along with this too. Can you confirm?
2018-7-29 10:56:48 INFO Device incomingā¦
2018-7-29 10:56:48 INFO MQTT publish, topic: āzigbee2mqtt/bridge/logā, payload: ā{ātypeā:āpairingā,āmessageā:ādevice incomingā}ā
Big shout-out to @Koenkk!! Apparently z2mqtt did not digest friendly names with either dots in between (or maybe they were simply too long or a combination of both). Iām back up and running and also the problem with the IKEA bulbs has been also solved along the way.
Hi Guys!
Anyone else with problems regarding release 0.1.1?
Iāve updated Z2M by updating github checkout, but didnt flashed the CC2531, since there is no new versionā¦
The only change was setting ādisable_led: trueā under serialā¦ Will try reflashing CC2531 just in case if the command messed the dongle.
Z2M starts normally but it stopped receiving messages at all.
Any hints?
Thanks in advace!
Troitino
Has anyone followed the instructions for Linux? I believe I have installed the dependencies but I still get a compile error.
checking for Boost headers version >= 1.39.0... no
configure: error: cannot find Boost headers version >= 1.39.0
Anyone else having issues with latest Hassio addon update 0.1.1?
Iām getting the following:
Thanks. Any way to roll back to a previous version?
It all worked pretty flawlessly using hassio and danielwelchās add-on.
I have enabled mqtt autodiscovery and connected my first sensor, a xiaomi open/close door/window sensor. I notice that in the mqtt stream my my broker it shows the correct state
For some reason the status is reversed in HA so I end up with
mqtt : "true" = HA state: "off"
mqtt : "false" = HA state: "on"
Any ideas what I might have done wrong?
How are you placing the xiaomi sensor. Itās default close state is when the sensor and the magnet are next to each other.