@IAmTheDude I used to use NR with the native plugins too - ie used HUE, TPLINK, etc; It was practically standalone from HA.
However, about 6 months ago I just moved everything over to use the HA plugin so I use the entities from HA and NR does the automations. I run NR in a Linux container (LXC in proxmox not Docker) and the CPU has gone form a constant 50% to around 1% now too.
The only drawback is that some HA releases do break the connection…oh and the fun I had when legacy passwords were depreciated
Basically HA runs everything now and NR is for my automations based on HA entities. Not sure how others run it, but it works for me
mb
I want to keep HA ‘in the loop’ and talking to NR. Some of the tuts Ive seen/watched use the HA entities but then others are independent of HA and it got a little confusing when first trying it out.
I plan to eventually have HA running on a more beefier box but still use the Pi’s around the house as bluetooth (for flic) and z2m access points depending on things pan out when I kit out all my Xiaomi and Hue stuff around the house.
I don’t intended to go full Hue and after using z2m for a while have no intentions of using any other hubs!
Everywhere I look makes NR look SO easy until I sat down to play with it
My zigbee xiaomi switches do not automatically turn back on after a power outage. Is there anything specific I need to setup so they retain their last setting when power is restored?
My mqtt config is as follows:
Thanks @ryanbeaton - I have upgraded to 1.2.1 and still the same - the zigbee xiaomi sockets do not automatically switch on after power is restored. What happens is when power power input is lost to the zigbee switch and that switch is turned on, the device/switch goes to “Unavailable” after the availability timeout figure of 15 seconds or so. When power is restored, the zigbee switch is detected as online again, and the switch remains OFF. Here is part of my relevant configuration.yaml for zigbee2mqtt
I couldn’t find someone with a similar problem in this thread so here it goes.
I’m using zigbee2mqtt with nodered and home assistant. Everything works as it should. However, in node red i use a state change node to trigger an notification and it triggers even when the state hasn’t changed.
I’ve seen that when this happens mqtt does send an mqtt message with the state of the sensor and homeassistant doesn’t update this because the state is still the same. However, node red does pick up the “state change” and triggers my notification.
Thank you that would definitely solve the problem. However, why does this happen? The state change node should only pick up state changed events send out by homeassistant.
Does the state change event also trigger when an mqtt message with the same payload is send by zigbee2mqtt?
Just an update in case anyone has any suggestions. Still having trouble with this motion sensor. When I re-pair it, it will work for a few hours then it gets ‘stuck’ and wont detect motion. It sends an MQTT message about once per minute saying ‘occupancy: true’ etc. As I mentioned before this happens even when placed next to the controller, so I don’t think it is linkstate.
I bought 2 of them about 3 months ago, they worked perfectly. Then I decided to buy 2 more and with one of the last 2 I had the same issues you are having, it would see motion when there was no movement etc… I marked is as DOA and bought a new one which worked perfectly.
Before marking it as DOA did you tried to use a new battery? If so do you only have one motion sensor or more?
Thanks - good suggestion to try a new battery (and good to know it probably isn’t just me doing something stupid). I have another one on the way from china (but the model without luminance) so hopefully that will work.
Hey guys, i have a problem with one of my osram blubs. It turns on in the middle of the night. Seems that it looses connection.
In the log i can see that when it reconnects, a message is published and it looks like the default value for the blub is “on”
Any way to prevent this?
zigbee2mqtt:info 3/21/2019, 6:34:36 PM Zigbee publish to device '0x7cb03eaa00ac34e2', genOnOff - on - {} - {"manufSpec":0,"disDefaultRsp":0} - null
Hello,
Sorry for maybe stupid question. I’ve connected ikea bulb and I see in log and in configuration.yaml that it is connected. But I quite confused what to do next. I can not find how to control it in hass.io. How to show it as an entity?