Check out the other video I made, linked in the description, which gives more tips on how to make your network more stable and reliable.

Thank you so much ❤️

Thanks for the tip! I didn't know that!

I wish I had read this earlier. The config file did not work for me and so I tediously enabled the last_seen entity 56 times.

Glad it was helpful!

Glad it was helpful!

Much appreciated!

Thank you!

Naw thanks 🙏

Glad it was helpful!

Do you have that full code online anywhere David?

@@xbmcnut If you mean the template sensor, its identical to what is in the video (and can be copied in the blog post), except the final line, which is replaced by {{ result.sensors | join(' ') | truncate(254, True) }} As for the automation, that is also identical to the video and blog post except for what I posted in my original comment. My full automation is below, just change sensor.offline_zigbee_devices to whatever your template sensor is called, and notify.phone to whatever device you want to send the notificaiton to. alias: Notify Change in Offline Zigbee Devices description: >- Send a notification to a device when 1 or more zigbee devices are deemed to be offline, or all come back online. trigger: - platform: state entity_id: - sensor.offline_zigbee_devices condition: [] action: - service: notify.phone metadata: {} data: message: |- {% if not states('sensor.offline_zigbee_devices') %} All Zigbee Devices Online! {% else %} The following Zigbee Devices are offline: {{ states('sensor.offline_zigbee_devices') }} {% endif %} mode: single

Those are really great additions to the template sensors. I'm gonna steal those and update my article! (With full credit to you of course) ❤️

Wow! Thank you so much for your support 🙏

Thanks for the clarification! 🙏

Thank you so much for your donation! I really appreciate the support 🙏

I use the standard version of the app on my mobile. I am sure it tracks some of my usage, but I use so many Google products that this is unavoidable for me. I'm trying to limit the amount that I am tracked, rather than try to eliminate it entirely.

Take a look at the "Creating a rock solid Zigbee network" video which is linked in the description. It mentions the top reasons why they go offline.

Possibly! I'm still learning the best way to play with these.

You can add this to your notification automation to alert you when all devices come back online, but not each one individually without doing way more code magic: {% if not states('sensor.offline_zigbee_devices') %} All Zigbee Devices Online! {% else %} The following Zigbee Devices are offline: {{ states('sensor.offline_zigbee_devices') }} {% endif %} Props to @davidgeorge4 for this extra piece of logic elsewhere in the comments.

They've been performing great! I have to use Home Assistant to "Simulate" the two way switching with Automations, and that is a pain. But I honestly never use the switches, all the lights are triggered by automations. I left the two way switching cables in the walls in case I move out or want to replace the switches in future.

@@HomeAutomationGuy Thanks for the reply. i have the switches but the 2 way situation is really annoying and would like dumb switches to work still for WAF. Also had to get a hub because HA didn't want to play ball, decoupled mode seems to just make them not work. love your videos, keep them coming.

I am unfortunately not sure how to make it work with ZHA as I don't use it in my smart home. If someone knows how hopefully they share it in the comments!

I think so? The Zigbee2mqtt documentation seems to suggest that

Almost. It has to be indented correctly and not nested under another important thing. I'd try and stick it right at the end to be safe.

I recently updated the article with some feedback from another commenter on my video to fix this. If you change the last line you can truncate it to fit. You should see this updated on the linked article too. {{ result.sensors | join(' ') | truncate(254, True) }}

More info: z2MQTT reports nothing offline. When I deliberately unplug a router device, it shows up as unavailable in z2MQTT but not in the template sensor preview.

I think you can use join(' ') to get seperate lines. Also HTML should be possible, but I think Jinja auto-escapes HTML (check the docs on that). Answering from phone, so not able to test atm.

try this in the notify, w/o changing anything else: message: >- "The following Zigbee Device(s) are Offline: - " {{ states('sensor.z2m_offline_devices') |replace(", "," - ") }}

@@HomeAutomationGuy This ended up under my question, I dont´t think it was intended as an answer to me??

Nope! I typed into the wrong box sorry 🤦‍♂️ I don't think a 24 hour clock should cause any problems. I'm sorry I don't know why it's not working

@@HomeAutomationGuy Whe I stated adding the units one by one, they showed up!

All my powered Zigbee devices work as repeaters, I don't use a specific device as a repeater.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 2047, in forgiving_as_timestamp raise_no_default("as_timestamp", value) File "/usr/src/homeassistant/homeassistant/helpers/template.py", line 1849, in raise_no_default raise ValueError( ValueError: Template error: as_timestamp got invalid input 'unknown' when rendering template '{% set result = namespace(sensors=[]) %}

Not entirely sure if I understand what you are running into, but I use the HACS integration "adaptive lighting" to automatically change the color temperature of my lights. I both wifi and Zigbee lights from multiple vendors (wled, Philips, ikea, Aqara, MiBoxer), and so far have not run into any major issues.

@@BeardAndCap I use adaptive lighting too, that works awesome if you leave your lights on through the day. However if you turn them off, then on again hours later they will start with the previous colour before adaptive lighting kicks in and changes to the new

@@Whoop0 Ahh, yes that is true. However for me the "old state" always transitions to the new state quite smooth without any flashes. On occasion I do run into a unresponsive light where the light won't turn off (forcing me to do a "turn off", "turn on") before the light is responsive again.

@@BeardAndCap even if smooth it’s pretty horrible if you for example turn on at 7am then next 11pm, blinded before it transitions. Wish I could work out how to fix, native Hue doesn’t have this problem.

My Hue lights and Candeo zigbee dimmers don't seem to do that. I use the light.turn_on service in Home Assistant, and assign a brightness level in that.

That's frustrating! I would be careful about ruling out battery, because I often have things report 100%, and then the next day report 2%, and then 20% etc. Try replacing the battery in one of them to see if that fixes it. Otherwise I'd see if you can add a router device nearby, like a smart bulb or something else that is mains powered, to see if strengthening the network makes it more reliable.

@@HomeAutomationGuy i found out what it was. i set the timeout for battery powered devices to 2 hours but if nothing changes the sensors only report in every 3 hours. so after 2 hours home assistant considered them unavailable even though they were just doing their normal thing. now i've set the timeout to 4 hours, and they work normally again. but this doesn't explain why my synology add-on keeps reporting its entities as unavailable (and this one doesn't come back by itself).

Unfortunately that's hard for me to help with since I'm not able to see your environment or devices. I'd try playing with the template in Developer Tools in Home Assistant and seeing if you can get results in there. Sorry I can't be more helpful!

@@HomeAutomationGuy I figured it out. Apparently over the last couple of years both the last seen entity and link quality of ZigBee devices has been disabled by default in HA, so you need to enable them in your entities list by filtering it by disabled and then using those search options. Works like a charm now. Thanks!

@@HomeAutomationGuy - I’ve got the sensor working but any idea why I get bombarded every couple of days with the notification? I get a bunch of devices saying they’re unavailable all at once. What might be happening within might network to cause that? They don’t go offline, they just say they’re unavailable but that changes once they triggered again.

I noticed in Mr. Groch Blueprint, needed to set to ISO8601_Local, and then I needed to double check when I added the yaml lines to the Configuration.yaml for zigbee2mgtt that it was saved. Restarted Zigbee2mqtt and the sensor is now there :) Hope that helps!

It works thanks

What's the error?

@@HomeAutomationGuy I tried to follow your video and blog but got confused in the "Then" part of your automation. I didn't understand how to do this part. I tried to copy the code you put in the video (replacing the name of the ID). However, some kind of syntax error occurred: "template value should be a string for dictionary value @ data['message']. Got None". Could you explain this part again, please?

@@rodrigomarins273 Sorry about that, I've edited the post to try and make it clearer. You’ll need to select the right service from the list for your Home Assistant mobile app notification service to send the notification, and then in the message part you’ll need to make sure you edit the {{ states(‘sensor.z2m_offline_devices’) }} part to use the sensor you created earlier. I hope this helps

@@HomeAutomationGuy Thanks so much! 😀🙏