Hue plug-in flips the fault status all the time

ebaauw / homebridge-hue

Homebridge plugin for Philips Hue

Apache License 2.0

894 stars 91 forks source link

Hue plug-in flips the fault status all the time #1153

Closed oilcan-productions closed 1 year ago

oilcan-productions commented 1 year ago

Issue

Looking at my log I see the fault status flip from 0 to 1 and back to 0 constantly,

Log Messages

[4/21/2023, 1:43:28 PM] [Hue] Nightstand 2: set homekit status fault from 1 to 0
[4/21/2023, 1:43:35 PM] [Hue] Middle outside: set homekit status fault from 0 to 1
[4/21/2023, 1:43:45 PM] [Hue] Middle outside: set homekit status fault from 1 to 0
[4/21/2023, 1:44:08 PM] [Hue] Right outside: set homekit status fault from 0 to 1
[4/21/2023, 1:44:23 PM] [Hue] Left outside: set homekit status fault from 0 to 1
[4/21/2023, 1:44:24 PM] [Hue] Right outside: set homekit status fault from 1 to 0
[4/21/2023, 1:44:30 PM] [Hue] Middle outside: set homekit status fault from 0 to 1
[4/21/2023, 1:44:53 PM] [Hue] Left outside: set homekit status fault from 1 to 0
[4/21/2023, 1:45:11 PM] [Hue] Left outside: set homekit status fault from 0 to 1

Debug Files

ebaauw commented 1 year ago

This is the result of the Hue bridge flipping the reachable state of the devices.

oilcan-productions commented 1 year ago

But why is it doing that continuously?

Get Outlook for iOShttps://aka.ms/o0ukef

From: Erik Baauw @.> Sent: Friday, April 21, 2023 2:50:01 PM To: ebaauw/homebridge-hue @.> Cc: Mike Kostersitz @.>; Author @.> Subject: Re: [ebaauw/homebridge-hue] Hue plug-in flips the fault status all the time (Issue #1153)

This is the result of the Hue bridge flipping the reachable state of the devices.

— Reply to this email directly, view it on GitHubhttps://github.com/ebaauw/homebridge-hue/issues/1153#issuecomment-1518364906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASO6P5KJBGY2N3SC645ZV23XCL6ITANCNFSM6AAAAAAXHJ24N4. You are receiving this because you authored the thread.Message ID: @.***>

ebaauw commented 1 year ago

You would have to ask the Hue bridge.

In my experience, the Hue bridge marks a device (light) as unreachable, when it doesn’t receive a timely answer from it. This can have several causes:

The device is powered off (typically using a 20th century wall switch);
The radio signal to/from the device from/to the bridge is too weak, or suffering from interference;
The device and the Hue bridge don’t play nice together. I’ve seen this more often with non-Hue lights.

Afaik, the Hue bridge provides no information whatsoever to understand what’s going on. You might try a Zigbee sniffer to analyse the communication between the bridge and the device.

jotzet79 commented 1 year ago

Hmmm, I have a similar behaviour on deConz

0|homebrid | [22.4.2023, 10:51:53] [Hue] FYRTUR block-out roller blind: set homekit status fault from 0 to 1
0|homebrid | [22.4.2023, 10:51:55] [Hue] FYRTUR block-out roller blind: set homekit status fault from 1 to 0
...
.
.
.
...
0|homebrid | [22.4.2023, 11:17:50] [Hue] myHome ZigBee Sensor TempHum 1: set homekit status fault from 0 to 1
0|homebrid | [22.4.2023, 11:17:50] [Hue] myHome ZigBee Sensor TempHum 1: set homekit status fault from 0 to 1
0|homebrid | [22.4.2023, 11:17:50] [Hue] myHome ZigBee Sensor TempHum 1: set homekit status fault from 0 to 1