is there anyway to have HA notice that a light is still on, and have it mark it as switched on on the front-end?
So for example, if I reboot HA and a light is on already, it won’t be reflected that way in HA.
thoughts?
I did not set retain eee to enabled (as in the flash docs) but my devices still work (did not have to repair.
Do does this really make a difference?
Apparantly not as all your devices are still working 
I have read somewhere in the forum that this settings needs to be enabled when flashing a new firmware version, but maybe that’s was only needed with the old method.
It will be reflected that way.
I have one ikea TRÅDFRI bulb. Unfortunately, I still have a dumb wall switch. If I switch on the bulb, HA won’t notice it in my case. I must manually slide the item in HA, and then it will pick the state up.
I understand from your response that HA should pick it up automatically whenever the light turns on?? In my case it doesn’t apparently.
AFAIK that issue hasn’t been solved yet.
If you’d mentioned the dumb wall switch to start with it might have been clearer.
Well, isn’t it the same case with rebooting HA and switching on a light?
Yes there is a way! In the config file of zigbee2mqtt you have to set your bulb to “retain: true”:
https://www.zigbee2mqtt.io/configuration/device_specific_configuration.html
In fact I have some troubles with my zigbee map now.
All devices work but they don’t show a connection in the map.
I can solve this by re-pairing the devices.
Do you think this could be avoided when setting ieee to retain?
I have exactly the same thing. Reflashed with the new controller, and I retained the IEEE.
The Zigbee devices work however… It´s just the map not showing the link and the signal strength.
No problem.
The flashing process is exactly the same as with the other devices (like the most common CC2531 stick, which I also have several of). The one difference is it uses a standard-pitch header (0.1 inch, if I’m not mistaken) rather than that mini header on the USB stick. So you don’t need the extra converter cable that’s needed for the CC2531.
You just need the XCore2530 module, the ZB502 motherboard, and the usual CC Debugger, which plugs right in.
All of the flashing commands are exactly the same, but you need to use the CC2530_CC2591 coordinator firmware.
I’m still super pleased with the performance. It’s an ugly pile of circuit boards, though, so I found an enclosure that fits it perfectly:
https://www.amazon.com/gp/product/B07HBWLZDQ
You’ll need to do your own drilling and cutting for the mounting standoffs and the antenna mount. Fortunately it’s soft enough aluminum that it’s pretty easy.
I’ll post a picture of the final “box” when it’s completely done.
1 Like
Hi,
I’m running zigbee2mqtt on a raspberry pi zero w with a CC2531 as a coordinator. Now, I’d like to extend the network with an additional router. I’ve been reading this thread for a while and could not find the answer to my questions…
The idea is to use a CC2531 with the router firmware, but I have one doubt: does the CC2531 router should be connected to a new RPI with another instance of zigbee2mqtt, or just powered on by a USB adapter?
In case I need a new instance, what should be on the configuration.yaml to tell the stick it is a router?
thanks
Just needs powered by a USB adapter.
1 Like
Will not that only solve the problem in case I had used z2m to activate bulb in the past session/run?
Don’t think so. I have set ieee to retain and also don’t have correct corrections in the map.
My Xiaomi sensors for example are not connected in the map, but they work fine.
Looks like there are still some issues with the map, but as long as all devices are working fine I wouldn’t bother about that.
Did someone here update to the newest firmware and still have the connections visible in the zigbee map?
Alright,
so i have just reveived and installed an iCasa Zigbee 3.0 Dimmer (ICZB-IW11D). Great Dimmer! Working fine. Dims LED bulbs without buzzing or flickering. Perfect… but there is one little thing that i discovered.
The dimmer doesn’t seem to give any feedback when it being operated (on/ off/ brightness) neither by the buttons on the dimmer or by an external switch connected to it. And second, it appears to be offline al the time when i look in network map.
Is this due to the hardware or is it because it’s not fully supported by z2m yet?
Hi all.
I attempting to move my HA system from raspberri py to virtual environment hoping my installation will be more stable.
I am running Hassbian in VM on debian 9.8.0
For some reason that i don’t understand my zigbee2mqtt is not working
in get this permission error and i have no idea on how to fix it.
xxxxx@debian-HA:~$ sudo systemctl status zigbee2mqtt
zigbee2mqtt.service - zigbee2mqtt
Loaded: loaded (/etc/systemd/system/zigbee2mqtt.service; disabled; vendor preset: enabled)
Active: active (running) since Fri 2019-02-22 21:31:58 EET; 1min 11s ago
Main PID: 414 (npm)
Tasks: 23 (limit: 4915)
CGroup: /system.slice/zigbee2mqtt.service
├─414 npm
├─428 sh -c node index.js
└─429 node index.js
Feb 22 21:32:00 debian-HA npm[414]: > node index.js
Feb 22 21:32:02 debian-HA npm[414]: zigbee2mqtt:info 2/22/2019, 9:32:02 PM Logging to directory: '/opt/zigbee2mqtt/data/log/2019-02-22.21-32-02'
Feb 22 21:32:03 debian-HA npm[414]: zigbee2mqtt:info 2/22/2019, 9:32:03 PM Starting zigbee2mqtt version 1.1.1 (commit #92d88b6)
Feb 22 21:32:03 debian-HA npm[414]: zigbee2mqtt:info 2/22/2019, 9:32:03 PM Starting zigbee-shepherd
Feb 22 21:32:03 debian-HA npm[414]: zigbee2mqtt:info 2/22/2019, 9:32:03 PM Error while starting zigbee-shepherd, attemping to fix... (takes 60 seconds)
Feb 22 21:33:03 debian-HA npm[414]: zigbee2mqtt:info 2/22/2019, 9:33:03 PM Starting zigbee-shepherd
Feb 22 21:33:03 debian-HA npm[414]: zigbee2mqtt:error 2/22/2019, 9:33:03 PM Error while starting zigbee-shepherd!
Feb 22 21:33:03 debian-HA npm[414]: zigbee2mqtt:error 2/22/2019, 9:33:03 PM Press the reset button on the stick (the one closest to the USB) and start again
Feb 22 21:33:03 debian-HA npm[414]: zigbee2mqtt:error 2/22/2019, 9:33:03 PM Failed to start
Feb 22 21:33:03 debian-HA npm[414]: {"message":"Error: Permission denied, cannot open /dev/ttyACM0","stack":"Error: Error: Permission denied, cannot open /dev/ttyACM0"}
xxxxx@debian-HA:~$ ls -l /dev/ttyACM0
crw-rw---- 1 root dialout 166, 0 Feb 22 21:31 /dev/ttyACM0
If i go in to the directory and start npm it starts and finds the USB sniffer and it works fine.
If anyone has an idea on how to fix this is quite appreciated.
Thanks
Possibly the user that systemctl is starting npm with is different user to the one when you do it manually.