Z-wave.me WallC-2 inclusion problem

Add-ons Bindings
,
1

Hi!

I’m running Openhab 1.8, with z-wave.me USB controller, and Habmin 1. Since earlier I have a pair of WallC-2 paddle switches that works just fine.

I have just bought four more WallC-2 switches, but no matter what I do I can’t seem to include them into my zwave network.

Also, looking at the old switches inside habmin, when I click the little plus to expand the Configuration of those, the plus turns into a minus, but no information shows up. It has done so before.

My zwave log looks like this when I try to include any on of my four new switches (the node number increases by one every time I try):

2018-04-14 11:29:34.319 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:44  ]- Setting controller into INCLUSION mode.
2018-04-14 11:29:34.320 [DEBUG] [o.b.z.i.protocol.SerialMessage:115 ]- NODE 255: Creating empty message of class = AddNodeToNetwork (0x4A), type = Request (0x00)
2018-04-14 11:29:34.320 [DEBUG] [WaveController$ZWaveSendThread:1295]- Took message from queue for sending. Queue length = 0
2018-04-14 11:29:34.321 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 05 00 4A 81 FF CE 
2018-04-14 11:29:34.321 [DEBUG] [WaveController$ZWaveSendThread:1355]- NODE 255: Sending REQUEST Message = 01 05 00 4A 81 FF CE 
2018-04-14 11:29:34.321 [DEBUG] [b.z.i.protocol.ZWaveController:651 ]- Enqueueing message. Queue length = 0
2018-04-14 11:29:34.322 [INFO ] [b.z.i.protocol.ZWaveController:854 ]- Starting inclusion mode
2018-04-14 11:29:34.325 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 07 00 4A FF 01 00 00 4C 
2018-04-14 11:29:34.327 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:29:34.327 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:29:34.328 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 07 00 4A FF 01 00 00 4C 
2018-04-14 11:29:34.328 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 07 00 4A FF 01 00 00 4C 
2018-04-14 11:29:34.328 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 01 00 00 , callbackid = 0
2018-04-14 11:29:34.328 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:77  ]- Add Node: Learn ready.
2018-04-14 11:29:34.328 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveInclusionEvent
2018-04-14 11:29:34.329 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:29:34.329 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:34.329 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 01 00 00 , callbackid = 0
2018-04-14 11:29:34.329 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:34.330 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 01 00 00 , callbackid = 0
2018-04-14 11:29:34.330 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99  ]- Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-04-14 11:29:34.330 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveTransactionCompletedEvent
2018-04-14 11:29:34.330 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:29:34.330 [DEBUG] [WaveController$ZWaveSendThread:1430]- NODE 255: Response processed for callback id 0 after 9ms/4920ms.
2018-04-14 11:29:38.788 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 07 00 4A FF 02 00 00 4F 
2018-04-14 11:29:38.789 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:29:38.790 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:29:38.790 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 07 00 4A FF 02 00 00 4F 
2018-04-14 11:29:38.790 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 07 00 4A FF 02 00 00 4F 
2018-04-14 11:29:38.790 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 02 00 00 , callbackid = 0
2018-04-14 11:29:38.791 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:81  ]- Add Node: New node found.
2018-04-14 11:29:38.791 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:38.791 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 02 00 00 , callbackid = 0
2018-04-14 11:29:38.791 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:38.792 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 02 00 00 , callbackid = 0
2018-04-14 11:29:38.792 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99  ]- Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-04-14 11:29:38.792 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveTransactionCompletedEvent
2018-04-14 11:29:38.792 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:29:39.019 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 20 00 4A FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 F9 
2018-04-14 11:29:39.020 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:29:39.021 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:29:39.021 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 20 00 4A FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 F9 
2018-04-14 11:29:39.021 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 20 00 4A FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 F9 
2018-04-14 11:29:39.022 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:29:39.022 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:89  ]- NODE 140: Adding controller.
2018-04-14 11:29:39.022 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 140: Notifying event listeners: ZWaveInclusionEvent
2018-04-14 11:29:39.022 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:29:39.023 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:39.023 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:29:39.023 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:39.024 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 04 8C 19 01 18 01 5E 8F 73 98 86 72 70 85 2D 8E 80 84 5A 59 5B EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:29:39.024 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99  ]- Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-04-14 11:29:39.024 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveTransactionCompletedEvent
2018-04-14 11:29:39.024 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:29:44.768 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 07 00 4A FF 05 8C 00 C4 
2018-04-14 11:29:44.786 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:29:44.786 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:29:44.787 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 07 00 4A FF 05 8C 00 C4 
2018-04-14 11:29:44.788 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 07 00 4A FF 05 8C 00 C4 
2018-04-14 11:29:44.788 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 05 8C 00 , callbackid = 0
2018-04-14 11:29:44.788 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:94  ]- Add Node: Protocol done.
2018-04-14 11:29:44.788 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:44.789 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 05 8C 00 , callbackid = 0
2018-04-14 11:29:44.789 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 81 FF , callbackid = 0
2018-04-14 11:29:44.789 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 05 8C 00 , callbackid = 0
2018-04-14 11:29:44.789 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99  ]- Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-04-14 11:29:44.789 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveTransactionCompletedEvent
2018-04-14 11:29:44.790 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:30:04.323 [DEBUG] [.z.i.config.ZWaveConfiguration:1370]- Ending inclusion mode.
2018-04-14 11:30:04.324 [DEBUG] [.z.i.config.ZWaveConfiguration:1393]- Stopping inclusion timer.
2018-04-14 11:30:04.324 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:60  ]- Ending INCLUSION mode.
2018-04-14 11:30:04.324 [DEBUG] [o.b.z.i.protocol.SerialMessage:115 ]- NODE 255: Creating empty message of class = AddNodeToNetwork (0x4A), type = Request (0x00)
2018-04-14 11:30:04.325 [DEBUG] [b.z.i.protocol.ZWaveController:651 ]- Enqueueing message. Queue length = 1
2018-04-14 11:30:04.325 [INFO ] [b.z.i.protocol.ZWaveController:862 ]- Ending inclusion mode
2018-04-14 11:30:04.325 [DEBUG] [WaveController$ZWaveSendThread:1295]- Took message from queue for sending. Queue length = 0
2018-04-14 11:30:04.325 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 04 00 4A 05 B4 
2018-04-14 11:30:04.325 [DEBUG] [WaveController$ZWaveSendThread:1355]- NODE 255: Sending REQUEST Message = 01 04 00 4A 05 B4 
2018-04-14 11:30:04.518 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 07 00 4A FF 06 8C 00 C7 
2018-04-14 11:30:04.518 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:30:04.518 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:30:04.519 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 07 00 4A FF 06 8C 00 C7 
2018-04-14 11:30:04.519 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 07 00 4A FF 06 8C 00 C7 
2018-04-14 11:30:04.519 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 06 8C 00 , callbackid = 0
2018-04-14 11:30:04.520 [DEBUG] [.b.z.i.p.s.AddNodeMessageClass:97  ]- Add Node: Done.
2018-04-14 11:30:04.520 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 140: Notifying event listeners: ZWaveInclusionEvent
2018-04-14 11:30:04.520 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:30:04.520 [DEBUG] [.z.i.config.ZWaveConfiguration:1393]- Stopping inclusion timer.
2018-04-14 11:30:04.520 [ERROR] [.z.i.config.ZWaveConfiguration:1399]- Neither inclusion nor exclusion was active!
2018-04-14 11:30:04.521 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 05 , callbackid = 0
2018-04-14 11:30:04.521 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 06 8C 00 , callbackid = 0
2018-04-14 11:30:04.521 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 05 , callbackid = 0
2018-04-14 11:30:04.521 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = FF 06 8C 00 , callbackid = 0
2018-04-14 11:30:04.521 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:99  ]- Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-04-14 11:30:04.521 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 255: Notifying event listeners: ZWaveTransactionCompletedEvent
2018-04-14 11:30:04.521 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:30:04.522 [DEBUG] [WaveController$ZWaveSendThread:1430]- NODE 255: Response processed for callback id 0 after 196ms/4920ms.

After trying to inluce the switch there is no new device in the Devices list in Habmin 1.

If I trigger a Node Information Frame from the switch, this is the result in the log:

2018-04-14 11:21:19.028 [DEBUG] [eController$ZWaveReceiveThread:1601]- Receive Message = 01 1E 00 49 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 25 
2018-04-14 11:21:19.037 [DEBUG] [eController$ZWaveReceiveThread:1517]- Receive queue ADD: Length=1
2018-04-14 11:21:19.037 [DEBUG] [b.z.i.protocol.ZWaveController:1244]- Receive queue TAKE: Length=0
2018-04-14 11:21:19.038 [DEBUG] [o.b.z.i.protocol.SerialMessage:255 ]- Assembled message buffer = 01 1E 00 49 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 25 
2018-04-14 11:21:19.039 [DEBUG] [b.z.i.protocol.ZWaveController:1245]- Process Message = 01 1E 00 49 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 25 
2018-04-14 11:21:19.039 [DEBUG] [b.z.i.protocol.ZWaveController:200 ]- Message: class = ApplicationUpdate (0x49), type = Request (0x00), payload = 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:21:19.039 [DEBUG] [.ApplicationUpdateMessageClass:49  ]- NODE 139: Application update request. Node information received.
2018-04-14 11:21:19.040 [DEBUG] [.ApplicationUpdateMessageClass:54  ]- NODE 139: Application update request. Node not known!
2018-04-14 11:21:19.040 [DEBUG] [b.z.i.protocol.ZWaveController:668 ]- NODE 24: Notifying event listeners: ZWaveInclusionEvent
2018-04-14 11:21:19.040 [DEBUG] [.z.internal.ZWaveActiveBinding:455 ]- ZwaveIncomingEvent
2018-04-14 11:21:19.040 [DEBUG] [.z.i.config.ZWaveConfiguration:1393]- Stopping inclusion timer.
2018-04-14 11:21:19.041 [ERROR] [.z.i.config.ZWaveConfiguration:1399]- Neither inclusion nor exclusion was active!
2018-04-14 11:21:19.041 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:83  ]- Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 05 , callbackid = 0
2018-04-14 11:21:19.041 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:84  ]- Recv message Message: class = ApplicationUpdate (0x49), type = Request (0x00), payload = 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:21:19.042 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:85  ]- Checking transaction complete: Sent message Message: class = AddNodeToNetwork (0x4A), type = Request (0x00), payload = 05 , callbackid = 0
2018-04-14 11:21:19.042 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:96  ]- Checking transaction complete: Recv message Message: class = ApplicationUpdate (0x49), type = Request (0x00), payload = 84 8B 18 01 18 01 5E 70 85 2D 8E 80 84 8F 59 5B 73 5A 86 72 EF 20 5B 26 27 2B 60 , callbackid = 0
2018-04-14 11:21:19.042 [DEBUG] [.z.i.p.s.ZWaveCommandProcessor:107 ]- Checking transaction complete: class=ApplicationUpdate, callback id=0, expected=AddNodeToNetwork, cancelled=false      mismatch

I have tried rebooting the server. I have tried factory resetting the wallc-2 switched, but the result is just the same.

I hope someone can help me, thanks in advance!

2

It looks like there’s a missing handler in the code to handle new controllers - I’ll add this today.

3

I’ve added the code to support including controllers (it should be available in the snapshot within an hour or so). However, given that you restarted the binding, I don’t think this will help.

Can you also provide a log of the startup. This will likely be long so please put the complete log somewhere like pastebin (or dropbox etc) so I can download it.

4

Great! Thanks a lot!

Is this some piece of code that has been there in earlier versions? I have included a bunch of units before.

When and how can I get your fix?

Do you have any clue as to why I can’t seem to access the configuration info on some of my units? I have configured them before so I am certain that it has worked (I have changed settings like LED brightness and different other settings and they are still in that mode).

It seems to be some model related info that is missing, because for example all Fibaro Dimmer2 devices works to show and set configuration, but fibaro door magnet FGK101 does no longer show any configuration info. Fibaro FGDW.002 does work. Fibaro double relay FGS222 does not work, and so on…

Any ideas on how I can fix that?

5

No - it is new. It looks like it was just an omission.

As above, if you restart the binding, then it should still initialise the device, so as I said, this probably isn’t the full story and I’ll need to see a logfile.

Maybe the database changed the type/IDs so that your devices are no longer found? I’m not really sure - I’d suggest to check that the database has the type/ids for your devices. I know there was some “rationalisation” of some devices a little while back, so it’s possible things got removed that shouldn’t have been.

Other than that I’m not sure what would cause it without a lot more information…

6

By looking at the Product Explorer in the habmin1 interface, I can see all the I have, the ones that work and the ones that does not work any longer.

Is there any way to “reset” that information in habmin, hopefully without the need to re-include the devices themselves?

7

Please check in the database itself - we need to be sure that the device types of your devices are in the database. You can type the type:id into the search to see what comes up.

8

There seem to be something wrong with the database, i have looked at the different devices I have that won’t show configurations and this is the text that shows when i look them up in the database:

http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/409

Device definition contains errors
Device category is not set.
These errors must be removed before the device can be approved

Overview information is not set
Inclusion information is not set
Exclusion information is not set
Association 1 appears to be a Lifeline group - please use the label "Lifeline".



http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/145

Device definition contains errors
`Type:Id` (0100:0101) is duplicated with another device with overlapping versions. (145, 548)
Device category is not set.
At least one manufacturers product image must be uploaded
These errors must be removed before the device can be approved

Overview information is not set
Inclusion information is not set
Exclusion information is not set
Wakeup information is not set
Parameter 1 description is too long - shorten and use the overview field.
Parameter 2 description is too long - shorten and use the overview field.
Parameter 11 description is too long - shorten and use the overview field.
Parameter 12 description is too long - shorten and use the overview field.
Parameter 13 description is too long - shorten and use the overview field.
Parameter 14 description is too long - shorten and use the overview field.
Parameter 25 description is too long - shorten and use the overview field.



http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/604

Overview information is not set
Inclusion information is not set
Exclusion information is not set



http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/124

Overview information is not set
Inclusion information is not set
Exclusion information is not set
Parameter 6, option 1 label is too long - shorten and use the overview field.
Parameter 6, option 2 label is too long - shorten and use the overview field.
Parameter 7, option 1 label is too long - shorten and use the overview field.
Parameter 7, option 2 label is too long - shorten and use the overview field.
Parameter 15 description is too long - shorten and use the overview field.
Parameter 16, option 0 label is too long - shorten and use the overview field.
Parameter 16, option 1 label is too long - shorten and use the overview field.
Parameter 30, option 1 label is too long - shorten and use the overview field.
Parameter 30, option 2 label is too long - shorten and use the overview field.
Parameter 30, option 3 label is too long - shorten and use the overview field.
Parameter 31, option 1 label is too long - shorten and use the overview field.
Parameter 31, option 2 label is too long - shorten and use the overview field.
Parameter 31, option 3 label is too long - shorten and use the overview field.
Parameter 32, option 1 label is too long - shorten and use the overview field.
Parameter 32, option 2 label is too long - shorten and use the overview field.
Parameter 32, option 3 label is too long - shorten and use the overview field.
Parameter 33, option 1 label is too long - shorten and use the overview field.
Parameter 33, option 2 label is too long - shorten and use the overview field.
Parameter 33, option 3 label is too long - shorten and use the overview field.
Parameter 40, option 1 label is too long - shorten and use the overview field.
Parameter 40, option 2 label is too long - shorten and use the overview field.
Parameter 40, option 3 label is too long - shorten and use the overview field.
Parameter 41, option 1 label is too long - shorten and use the overview field.
Parameter 41, option 2 label is too long - shorten and use the overview field.
Parameter 41, option 3 label is too long - shorten and use the overview field.
Parameter 42, option 1 label is too long - shorten and use the overview field.
Parameter 42, option 2 label is too long - shorten and use the overview field.
Parameter 42, option 3 label is too long - shorten and use the overview field.
Parameter 43, option 1 label is too long - shorten and use the overview field.
Parameter 43, option 2 label is too long - shorten and use the overview field.
Parameter 43, option 3 label is too long - shorten and use the overview field.



http://www.cd-jackson.com/index.php/zwave/zwave-device-database/zwave-device-list/devicesummary/177

Device definition contains errors
Device category is not set.
At least one manufacturers product image must be uploaded
These errors must be removed before the device can be approved

Overview information is not set
Inclusion information is not set
Exclusion information is not set
9

Please feel free to update this device to correct this - it won’t be an issue though as the device is already in the database. I recently upgraded some warnings to errors to try and enforce data entry to improve the database (there was a recent post about this).

This is a problem - so to confirm - your WallC has the 0100:0101 device type?

However, I don’t think either of these are causing the issue where no parameters are shown since the devices are in the database so should be discovered (even if the last one might be incorrect - it still has parameters, so should be discovered).

10

Manufacturer POPP
Product 009303 Wall controller
Manufacturer ID 154
Device ID 101
Device type 100
Version 4

Which is a little strange since it says Z-wave.me ZME_WALLC-S on the sticker.

11

Probably either one of the POPP or Z-wave.me are just rebranded versions that have the same onboard software?

How can the error in the database be fixed, so I can access and configure my device?

12

I’ve removed the conflict in the type/ids. It would be appreciated if you could update any other information required to remove the warnings/error?

13

Now I have upladed an image and added some text into the database for the WallC-S.

Do you think it will fix my problem with not being able to see the configuration? How will that change in information come into my installation? I’m not sure about how it all works.

14

I’m not sure - it’s been a long time since I looked at OH1 and I’m not sure exactly what definitions are there. If it was working in the past, then this probably won’t fix it.

Once I’ve updated the binding (I’ll do this tomorrow) you will need to grab the latest version of the OH1 binding.

15

Where exactly can I grab your latest version?

Is this the place? https://openhab.ci.cloudbees.com/job/openHAB1-Addons/