I have a z-wave light that is automatically turning on at around 2.15am every day and off a few minutes later. I have no rule set up to turn on this light and no one is awake flipping the switch manually! In the event.log I see this entry:
2019-05-17 02:20:25.246 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from OFF to ON
2019-05-17 02:20:25.247 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 0 to 75
2019-05-17 02:59:04.529 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from ON to OFF
2019-05-17 02:59:04.530 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 75 to 0
Can anyone help me understand what might be causing this device to turn on/off given there are no rules?
Thanks. The z-wave device is a Fibaro FGD212 Dimmer 2 and therefore controls both the switch and the light. There is a single association to another light, such that when the manual switch is used to turn on the ‘back wall’ light, the ‘front wall’ light turns on as well.
Interestingly, at night, when the back wall light automatically turns on, the front light does not - suggesting it’s again not the manual switch turning on the light - which I already knew! No inbuilt device timer
Thanks. WRT timer - you are absolutely correct - thank you for highlighting that. I wasn’t aware of it. Sadly it’s only auto-off after a certain period of time, and it’s not set. I’m more concerned about why it’s turning on in the first place TBH.
I know I could increase debugging levels. But not sure which module (or how) as I think something else is telling the z-wave device to turn on.
Well, the off remains a mystery as well, and you need clues, don’t discard them.
Is it always ghost-off 40 minutes after ghost-on? That suggests a deliberate (if hidden) control at work, not random events. If you switch on by hand, does it ever turn off unexpectedly?
Good question! Here is another example, this time a little later in the early hours of the morning.
events.log.7:2019-05-16 03:33:12.423 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from OFF to ON
events.log.7:2019-05-16 03:33:12.424 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 0 to 75
events.log.7:2019-05-16 03:55:15.220 [ome.event.ItemCommandEvent] - Item 'light_back_wall_dm' received command 100
events.log.7:2019-05-16 03:55:15.221 [nt.ItemStatePredictedEvent] - light_back_wall_dm predicted to become 100
events.log.7:2019-05-16 03:55:15.222 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 75 to 100
events.log.7:2019-05-16 03:55:17.286 [ome.event.ItemCommandEvent] - Item 'light_back_wall_dm' received command 0
events.log.7:2019-05-16 03:55:17.290 [nt.ItemStatePredictedEvent] - light_back_wall_dm predicted to become 0
events.log.7:2019-05-16 03:55:17.292 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 100 to 0
events.log.7:2019-05-16 03:55:18.384 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from ON to OFF
This time just a 22 minute gap between the on and off events. I will try your suggestion of seeing if an auto-off occurs after manually left on over the weekend. Tonight I’m running the z-wave log in DEBUG to see what treasures that reveals!
Woah, just a minute … where has that come from? A command means it is something that openHAB has done - originating from a UI, or a rule, or (rarely) a binding.
Time to show us Item, channel, Thing definitions.
Ahh. My bad. Bad example. That was one occasion when I woke up and saw the light was on - proceeding then to turn the light off myself - hence the command! A better example would be:
2019-05-04 01:39:35.309 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from OFF to ON
2019-05-04 01:39:35.310 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 0 to 75
2019-05-04 02:23:45.381 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from ON to OFF
2019-05-04 02:23:45.382 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 75 to 0
Same thing again last night. Entries from events.log are:
2019-05-18 02:45:12.735 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from OFF to ON
2019-05-18 02:45:12.735 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 0 to 75
2019-05-18 03:24:21.208 [vent.ItemStateChangedEvent] - light_back_wall_sw changed from ON to OFF
2019-05-18 03:24:21.209 [vent.ItemStateChangedEvent] - light_back_wall_dm changed from 75 to 0
Does your switch have a good wall connection. I had some ghost switches on my insteon. I believe the wire nuts may have been loose. The keypad reset cause a few false switch events. Only thing I could come up with.
I redid the connection and problem seems to have gone away.
Have you tried to reboot your openHAB server already? I face the same situation with one light in my house after my openHAB server has not been rebootet for several weeks/some months. I had no time yet to really get into it. But everything I checked so far, did not bring me closer to a solution. But I noticed that the ghost in my house goes on vacation for a longer time whenever I have to reboot my server.
Thanks all - sorry for delayed response. After a lot of testing, I finally identified that the problem was nothing to do with OH2 at all! I disconnected all channels, items and things, then removed the zWave device (Fibaro dimmer) from the zWave network. Still the problem carried on. Put this down to a faulty device and have replaced.