I’m hoping someone has some insight into the issue I am having with a Homeseer WS-WD200+ dimmer. Rules based on “received update” are firing multiple times. This is occurring on multiple dimmers of the same model. There are no other rules for this item. The only other dimmer that I have is a GE/Jasco and it is working ok.
My item definition is:
Dimmer FoyerLight "Foyer Light" (gDimmers) {channel="zwave:device:7461b9e4:node16:switch_dimmer"}
Number FoyerScene "Foyer Scene number" {channel="zwave:device:7461b9e4:node16:scene_number"}
The rule is as simple one made just for this test::
rule FoyerLightDoubleTap
when Item FoyerScene received update
then logInfo("FoyerLightDoubleTap","Foyer light scene changed to {}", FoyerScene.state.toString)
end
I pressed single tap up, double up, triple up, quadruple up, quadruple tap down, triple, double and single down and received the following log entries:.
2020-08-01 19:49:05.756 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.0
2020-08-01 19:49:05.770 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.0
2020-08-01 19:49:05.908 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.0
2020-08-01 19:49:10.818 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.3
2020-08-01 19:49:10.835 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.3
2020-08-01 19:49:19.634 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.4
2020-08-01 19:49:19.650 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.4
2020-08-01 19:49:28.142 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.5
2020-08-01 19:49:28.157 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 1.5
2020-08-01 19:49:38.682 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.5
2020-08-01 19:49:38.697 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.5
2020-08-01 19:49:49.086 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 19:49:49.102 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 19:50:00.025 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 19:50:00.041 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 19:50:10.783 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.3
2020-08-01 19:50:10.801 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.3
2020-08-01 19:50:21.366 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.0
2020-08-01 19:50:21.382 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.0
If anyone has suggestions i would appreciate it.
OpenHab 2.5.0.000 running on a Synology DS1812+
Aeotec zStick Gen 5.
HS-WD200+ version 5.14.
Thanks for your help. I read through that post and I believe I’ve tried everything suggested. Rebooting OpenHab didn’t help, and I’ve never used any zWave associations.
A quick test of just the double, triple and quad “down” paddle shows a single entry for each in events.log but double entries in openhab.log
events.log:
2020-08-01 21:00:45.764 [vent.ItemStateChangedEvent] - FoyerScene changed from NULL to 2.3
2020-08-01 21:00:45.790 [ome.event.ItemCommandEvent] - Item 'FoyerLight' received command OFF
2020-08-01 21:00:45.792 [nt.ItemStatePredictedEvent] - FoyerLight predicted to become OFF
2020-08-01 21:00:45.827 [ome.event.ItemCommandEvent] - Item 'FoyerLight' received command OFF
2020-08-01 21:00:45.828 [nt.ItemStatePredictedEvent] - FoyerLight predicted to become OFF
2020-08-01 21:00:55.769 [vent.ItemStateChangedEvent] - FoyerScene changed from 2.3 to 2.4
2020-08-01 21:01:18.539 [vent.ItemStateChangedEvent] - FoyerScene changed from 2.4 to 2.5
openhab.log
2020-08-01 21:00:45.771 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.3
2020-08-01 21:00:45.805 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.3
2020-08-01 21:00:55.772 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 21:00:55.785 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 21:01:07.332 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 21:01:07.345 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.4
2020-08-01 21:01:18.542 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.5
2020-08-01 21:01:18.555 [INFO ] [ome.model.script.FoyerLightDoubleTap] - Foyer light scene changed to 2.5
The rule is a little different now, turning the light off on a double tap.
rule FoyerLightDoubleTap
when Item FoyerScene received update
then logInfo("FoyerLightDoubleTap","Foyer light scene changed to {}", FoyerScene.state.toString)
if (FoyerScene.state == 2.3) {
sendCommand(FoyerLight, OFF)
}
end
Yes. I think you missed that updates-to-same-state don’t normally appear in your events.log. This part is expected behaviour. Your ‘surprise’ is in getting the multiple updates.
Nevertheless, they exist in your devices. The interest here would be what (if anything) they are set to, not whether it was you that set them. Unless I’ve misunderstood and you have checked each suspect device.
How are the associations configured? The only association that should be used is the lifeline - if you link multiple groups, you will get multiple notifications.
Thanks @Chris and @rossko57, looks like I’m getting a lesson in associations.
Lifeline was the only association used, but on about half of my items Lifeline had two values, the controller and node3. I’m fairly certain that node3 is my Harmony Hub - it keeps showing up in my inbox when I do a zWave discovery, but I don’t add it as a Thing to OpenHab. I was expecting a second association field in the configuration, the “2 - companion syc” in the screenshot below?) I have no idea how node3 got into the Lifeline association but I removed node3 from all of the Items that had it and everything is working well now.
Harmony Hubs don’t have ZWave (unless you have the Home Hub Extender), so it can’t be a ZWave node. It’s probably just showing up in your inbox due to openHAB scanning for devices (even though you’re only intentionally scanning for ZWave).
Did you add and remove a ZWave device in the past? That results in unused nodes. I only have three ZWave devices, but they’re numbered 5, 8, and 10 due to past monkeying around.
I do have the extender. For some reason it was assigned to the Lifeline (along with the controller) on about half of my items. Removing the Extender from the Lifeline fixed the issue.
Well then, that makes way more sense. I’m surprised that it got assigned a node if you didn’t actually add the thing, but I guess that’s part of the discovery process.
On a semi-related note, do you find the Extender useful?
The controller stick needs to know about it. Once it does, it’s exposed to openHAB discovery.
It is curious that openHAB seems here to “eavesdrop” on lifeline traffic intended for another box, but I know nothing about how these messages work. Maybe it’s a consequence of expecting only one controller in a mesh. @chris is that expected behaviour, something special about llifeline?
@JimH I would guess it is the Harmony hub that inserted itself into associations, let’s assume during some initialization or setup process. It might happen again …
I believe Lifeline is for the main controller in a network only. I suspect this condition was not part of the binding design. which was the first controller in the network? Homeseer or openHAB?
All nodes in a network must have a node id - otherwise they cannot participate in the network. An extender is a router - it performs routing, and to be included in routing it needs an address - this is the node id.
It doesn’t - it will only receive the data addressed to the binding.
Sorry - I can’t quite correlate this question with comments above. What is “that” that is expected behaviour?
Likewise - I’m not sure what condition you’re referring to here? Probably the same thing as @rossko57 so probably my bad that I can’t tie these questions up with the above…
There’s nothing special about the lifeline, and the binding don’t receive data addressed to other nodes. Many devices only allow a single node in the lifeline, in which case someone needs to decide what controller is the primary in the event there are multiple systems on the network.
Without seeing logs of what was being received, and probably also the association configuration, it’s really hard to know what was happening. It could also be something specific about this device maybe.
