zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

Published 20 hours ago • verified publisher icon Koenkk

Unavailable entities from operational device

Open dankarization opened this issue 1 year ago • 10 comments
trafficstars

What happened?

I have a few devices throughout the house with this problem: image

  1. They are fully operational from Z2M frontend, have more than good coverage (first 4 in the list below are directly under the coordinator in the same room with it), report nicely and had no such problems before as i believe.
  2. They have several entities, but some of them (of course, by the will of fate, not the ones I really need) are operational from home assistant
  3. All entities were working lately, and just became unavailable for some reason

image image image

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

Idk, maybe turn off MQTT addon for some time.

Zigbee2MQTT version

1.37.0-1

Adapter firmware version

20240315

Adapter

TZT HamGeek POE (ZigStarGW) with cc2652p2 chip

Setup

Home Assistant OS with 2 addons for each floor and coordinator

Debug log

In these logs look for problems with devices:

  • Island LED
  • Island floor
  • Подсветка кухня шкаф
  • Kitchen. Working light
  • Led light. Sauna
  • Wine cellar chandelier (it's a group of 3 lights: Люстра 1, Люстра 2, Люстра 3)

log.log log1.log log2.log

Failed to ping for all '(отключен)' ones is ok'ish as they are physically disconnected from power.

log1.log file, line 7892, I see MQTT connection problems that were quickly resolved by itself. Aproximately at this time entities I talk about became unavailable and never came back (but almost all others are ok)

System restart (full system, not only HA) also does not help.

dankarization avatar May 05 '24 08:05 dankarization

UPD: restored 1.36.1-1 version backup and the problem is gone, but on the 1.36.1-1 i have a problem with brightness:1000 as many other people, why I updated to 1.37.0-1

dankarization avatar May 05 '24 09:05 dankarization

Yep same problem

cloudbr34k84 avatar May 05 '24 10:05 cloudbr34k84

What home assistant version are you using? Make sure to use at least 2024.4 as mentioned in the Z2M release notes.

Koenkk avatar May 05 '24 20:05 Koenkk

Hasos 2024.5.1 here.

Thanks, Craig

On Sun, May 5, 2024, 4:13 PM Koen Kanters @.***> wrote:

What home assistant version are you using? Make sure to use at least 2024.4 as mentioned in the Z2M release notes.

— Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/22460#issuecomment-2094934486, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADDNYG7DYIRC5ZO4YK6JLYLZA2HHRAVCNFSM6AAAAABHHQ3ZPSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJUHEZTINBYGY . You are receiving this because you are subscribed to this thread.Message ID: @.***>

craigwitter avatar May 05 '24 20:05 craigwitter

I'm running beta

cloudbr34k84 avatar May 05 '24 20:05 cloudbr34k84

@Koenkk does this help? https://github.com/home-assistant/core/issues/116914

craigwitter avatar May 07 '24 00:05 craigwitter

@craigwitter that's not about entities becoming unavailable as far as I can see

Koenkk avatar May 07 '24 20:05 Koenkk

Use EMQX broker instead of mosquitto. See here: https://github.com/Koenkk/zigbee2mqtt/issues/18862

popy2k14 avatar May 09 '24 12:05 popy2k14

@popy2k14 Thanks, that really helped. I used to use Mosquitto and had the same issue as described here. I swapped Mosquitto with EMQX, now a reboot of home assistant always restores all entities and no entities become unavailable anymore.

MarcoGos avatar May 09 '24 18:05 MarcoGos

@MarcoGos You're welcome. Nice that it also solved the issue for you. Running EMQX for over a month now without a issue.

popy2k14 avatar May 09 '24 18:05 popy2k14