Yeelight issue turning on automatically

Add-ons Bindings
1

Since I added my yeelight to openhab2, it turns itself on like every hour. I tried to find something in the logs but it is not so easy, since I don’t know exactly when this happens. Sometimes when the light is on it flickers also for a second or two.

Does anyone of you had the same issue and knows what to do?

Here are the logs:

2019-03-16 11:32:30.227 [vent.ItemStateChangedEvent] - miNetLife changed from 28589 to 28650

2019-03-16 11:33:30.251 [vent.ItemStateChangedEvent] - miNetLife changed from 28650 to 28710

2019-03-16 11:34:30.345 [vent.ItemStateChangedEvent] - miNetLife changed from 28710 to 28770

2019-03-16 11:34:39.839 [vent.ItemStateChangedEvent] - l_masbedroom changed from OFF to ON

2019-03-16 11:34:39.851 [vent.ItemStateChangedEvent] - yee_power changed from OFF to ON

and this one:
2019-03-16 14:54:55.246 [vent.ItemStateChangedEvent] - yee_nightlightBrightness changed from NULL to 100

Thanks in advance!

2

You can use the log Filter (top right) to show logs for filtered items only.

Setting the log to DEBUG it may help identify whats causing the issue but the downside is you will end up with a bunch of logs.

Are you using any rules to control the problem item?

3

Thanks for the answer. No I used the item in a rule but not anymore.

4

OH may still have the rule in cache so cleaning cache would be the first step to troubleshoot the issue.

sudo systemctl stop openhab2

sudo openhab-cli clean-cache

sudo systemctl start openhab2

1 Like
5

I’ll go ahead and do that then. I restarted several times already.

6

Unfortunately this did not solve the problem. But thanks.

7

Ok I’ll tried to turn openhab off and the issue did not occur, the light did not turn on by itself. So I waited for it to happen again and seems that this thing is triggering it it the logs:

2019-06-10 15:53:53.084 [vent.ItemStateChangedEvent] - miNetLife changed from 44273 to 44333

strange but this must be something else because the miNetLife is coming from my vacuum not from the light.

8

Hmh, just want to let you know that I still have the same issue. I’m readding the lamp now.

9

I found this in the log, this happend the same moment the light blinked. But this should actually not affect the lamp at all. She isn’t even Zigbee connected.

2019-07-03 23:39:51.597 [DEBUG] [converter.ZigBeeConverterSwitchLevel] - 90FD9FFFFE88B7DA: ZigBee attribute reports ZclAttribute [cluster=ON_OFF, id=0, name=OnOff, dataType=BOOLEAN, lastValue=true, lastReportTime=Wed Jul 03 23:39:51 CEST 2019]

2019-07-03 23:39:51.600 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 90FD9FFFFE88B7DA: Channel zigbee:device:4e268c39:90fd9ffffe88b7da:90FD9FFFFE88B7DA_1_dimmer updated to 95

2019-07-03 23:39:51.602 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE88B7DA: Updating ZigBee channel state zigbee:device:4e268c39:90fd9ffffe88b7da:90FD9FFFFE88B7DA_1_dimmer to 95

2019-07-03 23:39:51.785 [DEBUG] [converter.ZigBeeConverterSwitchLevel] - 90FD9FFFFE88B7DA: ZigBee attribute reports ZclAttribute [cluster=LEVEL_CONTROL, id=0, name=CurrentLevel, dataType=UNSIGNED_8_BIT_INTEGER, lastValue=241, lastReportTime=Wed Jul 03 23:39:51 CEST 2019]

2019-07-03 23:39:51.788 [DEBUG] [converter.ZigBeeBaseChannelConverter] - 90FD9FFFFE88B7DA: Channel zigbee:device:4e268c39:90fd9ffffe88b7da:90FD9FFFFE88B7DA_1_dimmer updated to 95

2019-07-03 23:39:51.791 [DEBUG] [ng.zigbee.handler.ZigBeeThingHandler] - 90FD9FFFFE88B7DA: Updating ZigBee channel state zigbee:device:4e268c39:90fd9ffffe88b7da:90FD9FFFFE88B7DA_1_dimmer to 95
10

You should at least share your suspect Item, channel, and Thing configurations in case someone can spot something odd,

If you’re not seeing commands in the log, it probably isn’t originating in openHAB? State updates in your events.log would be expected wherever the action came from, guessing your suspect uses yee_xxx names…

This is old complaints but suspiciously similar …

1 Like
11

OK good advice will do that tomorrow. No it’s definitly coming from openhab i checked this. With shutting down openhab for several days and it never occured.

12

I found the issue. Strangely it has nothing to do with the Yeelight app nor the Openhab system. It seems that it was just a coincidence that it did not occur when the openhab was off. It is my houses powerline, there something wrong with it, at least it seems like it. It crossed my mind yesterday and I directly did go ahead to try it and it worked. I enabled, under the Lamp and “Default State” the option “Save light state automatically” this did the trick. So it seems like there are some minimalistic very short powerlosses on the line where the lamp is connected (or at least the lamp thinks that) and thats why she turned always on again because “Auto on upon power resumption” was enabled.

2 Likes