Hello, I have used the companion device previously on homeseer ws200, I have 10 new wx300’s and no matter what I do, the companion will not save. I went into var/lib/openhab/ to each device, using the ws200’s, i was able locate the portion that associates another node. On the wx300’s, it states node 1 and will not allow me to change due to permissions.
Any thoughts on this one? Hope to get this figured out soon as I didn’t run 3 way wire lol.
I’m not familiar with the device and do not understand your post very well.
I see two versions in the Zwave database & here with slightly different IDs (4447:4037) & (4447:4036). How was this added to OH(via the Zwave/scan/inbox?) Also these are relatively new additions. What version of OH3 are you on? One version needs 3.2 the other is going to need 3.3M1 or 3.3M2. Is there an xml file in the var/lib/openhab/zwave folder for the nodes? Is there any information on the UI page for the device?
Bob
These were added via scan and add via console. They function otherwise normal but thr companion setting under each device isnt functional. Im on latest stable version of openhabian. Mine state they are manufacture id 4447:4036
Since I do not have the device I do not know what you mean. What is the companion setting?
So is this the release 3.2?
Companion Sync is something that came out I believe on the wd/ws200 series homeseer switches, also is on the wx300 series. I have not seen it on any other zwave devices. It allows you to set another device to allow that device to mirror each other. Works really well, we have used it in multiple rooms with two switches and without 3-way wiring. I’ve attached a screenshot of the setting within the device as well as the xml portion of code from the ws200 stating “node 30” is the “Associated Member”. On the ws200’s, On one device I set the node to the other device’s node to mirror and on the mirror device I would set it to the other devices node. Both would mirror each other with no lag or issues. Currently that device is still functioning fine. I did verify, I’m on 3.2 Release Build -Openhabian.
Ok I understand. My advice is to update to 3.3M2. I see that after 3.2 was released the association on the device was changed a bit and that might explain it. My other thought is that the OH core has been working on strict parameter validation and that may be preventing the assignment of a node to group 2. You might be able to get a Debug message by following my post here.
Bob
Thanks ill see if i can try the debug mode here shortly
Here is what i got saving it in debug mode.
2022-03-16 08:25:59.159 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update received
2022-03-16 08:25:59.162 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_30_1 to 5 (BigDecimal)
2022-03-16 08:25:59.163 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_32_1 to 0 (BigDecimal)
2022-03-16 08:25:59.163 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_00000077 to 0 (BigDecimal)
2022-03-16 08:25:59.163 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_11_1 to 2 (BigDecimal)
2022-03-16 08:25:59.164 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000007B to 0 (BigDecimal)
2022-03-16 08:25:59.164 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored group_1 to [controller, node_36] (ArrayList)
2022-03-16 08:25:59.165 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000007D to 0 (BigDecimal)
2022-03-16 08:25:59.165 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update set group_2 to [node_36] (ArrayList)
2022-03-16 08:25:59.166 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Association 2 consolidated to [node_36]
2022-03-16 08:25:59.166 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Unknown association group 2
2022-03-16 08:25:59.167 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored switchall_mode to 255 (BigDecimal)
2022-03-16 08:25:59.167 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored action_reinit to false (Boolean)
2022-03-16 08:25:59.167 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000006F to 0 (BigDecimal)
2022-03-16 08:25:59.168 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_12_1 to 2 (BigDecimal)
2022-03-16 08:25:59.168 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_13_1 to 0 (BigDecimal)
2022-03-16 08:25:59.169 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_14_1 to 0 (BigDecimal)
2022-03-16 08:25:59.169 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_21_1 to 0 (BigDecimal)
2022-03-16 08:25:59.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_22_1 to 0 (BigDecimal)
2022-03-16 08:25:59.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored action_failed to false (Boolean)
2022-03-16 08:25:59.170 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored action_heal to false (Boolean)
2022-03-16 08:25:59.171 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000007E to 0 (BigDecimal)
2022-03-16 08:25:59.171 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000005F to 0 (BigDecimal)
2022-03-16 08:25:59.172 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_31_1_0000003F to 0 (BigDecimal)
2022-03-16 08:25:59.172 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_27_1 to 0 (BigDecimal)
2022-03-16 08:25:59.173 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_23_1 to 0 (BigDecimal)
2022-03-16 08:25:59.173 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_24_0 to 0 (BigDecimal)
2022-03-16 08:25:59.174 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_3_1 to 0 (BigDecimal)
2022-03-16 08:25:59.174 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_4_1 to 0 (BigDecimal)
2022-03-16 08:25:59.174 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_25_1 to 0 (BigDecimal)
2022-03-16 08:25:59.175 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_5_1 to 1 (BigDecimal)
2022-03-16 08:25:59.175 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_26_1 to 0 (BigDecimal)
2022-03-16 08:25:59.176 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored config_6_1 to 0 (BigDecimal)
2022-03-16 08:25:59.176 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 40: Configuration update ignored node_id to 40 (BigDecimal)
I got this working, I found another post about similar error. They reinitialized the device and it took to saving the associated sync. I did the same on both devices, then tried saving it. It stated Pending, which i let it sit on. Then I exited out of the device and back in through the UI, both stated. I then rebooted, it stayed again. Then went and tested, all is well. Thanks for all of the advise, much appreciated of the OH community always giving quick support. This is why OH is the best device out there for home automation.