Cool - thanks Kai 
Can you try to reinitialise the device - in the thing configuration in HABmin, click on the tools menu and select ‘show advanced settings’. Then you should see an option to reinitialise
I first added node 5 as an item, then I reinitialized, but got a red Error sign up in the corner saying “Error sending action”.
And, no - nothing in the log, like I never did the reinit. I have debug on for zwave, the rest is at its default.
I then restarted oh, but now node 5 comes up with the red cross - offline. In the zwave log, it looks alright though. Off line, it seams that I cannot select reinit anymore.
I have seen offline before, for other nodes, and then it has helped to restart, but not now. Maybe it is because it is a battery device, and I haven’t waited long enough, or maybe it is also related to the same problem as the xml issue.
I’ll let it over night, and check before going to work tomorrow, if it has come fully online.
Thanks for all help, and for adding the unknowns - they show up nicely!
How can I actually start an exclusion on on the controller / gateway?
(my UZB Stick has no button)
and could I include … make some settings via habmin … exclude … and all the settings are still on it?
thanks
Good question. I think at the moment there is no way to do this. I’ll add an option into the tools menu of the controller.
I don’t think so - I think with all devices, once you exclude it from the network it gets reset to the factory defaults.
Mhh didnt know that. Once there is the exclusion Option I gonna test that.
I have a number of items that aren’t in the db. I posted the XML of 2 of them above but think they may have gotten lost in the mix of other messages. What’s the best way to have them added to the db?
GE Dimmer Switch (model 12724)
GE Switch (12722)
GE Outlet (12721)
Aeon Gen5 Hidden Door Sensor
Nexia Doorbell Sensor (not installed yet, but soon)
Sorry for missing that - it’s been a busy few days 
The best thing is to register on the database and I’ll give you access to load xml and edit the definitions.
Have those items up. Looks like the previous versions where there and it just updated them with the appropriate data.
The Aeotec Hidden Door sensor didn’t generate an xml file (but it works), so is the best way to handle that to just create a manual entry?
Thanks!
I just fixed the database entry for this device yesterday. It should be working now with the latest zwave binding. If you want to see it fully online, hold the button in with a paperclip for 5 seconds, this causes it to initialize. Don’t hold for 20 though, that is a factory reset Else, you can wait for it to check in, of course.
I just noticed it after I posted my reply. I had looked yesterday and not seen it. One my other items are officially added I’ll have to try out the new binding again (using the 1.9 snapshot in the meantime).
Hey chris, in zwave1 we used to flag a temperature or setpoint with “setpoint_scale=1” to use Fahrenheit over Celsius. I see there is a channel that is commented out in the xml that references this. Is this supported yet in zwave2? I noticed it was a little warm this morning and saw might thermostats were set to 99F !
Channel configuration had some issues in ESH and it wasn’t fully supported when I added the configuration to HABmin a few weeks back so I commented this out. I need to go back and revisit this - I’ll try and look at it tonight or tomorrow.
Thanks, but don’t rush on account of me! Also if there’s anything like this you want to delegate to try and get some more people comfortable with the new code, count me in.
Hi @chris
No, node number 5, the zwave.me wall controller, does not come online. However, it looks fine in the logs afaict (it wakes up and talks to oh periodically, and when I press a button on it).
I guess this might somehow related to the “problem”.
So the reinit route seams to be a dead end.
What if I delete the xml, or start fresh with a new installation of oh/binding?
Edit: LOL! Just after I wrote this, I tried once more to reinit, even though off line, and this time it did something! Log is coming!
For info, the reinitilisation option in the tools menu does the same thing as deleting the XML (well, it does delete the XML, and then it re-initialises as though you’d restarted the binding for that one device).
Great - thanks.
for the AEON Multisensor 6 (ZW100 MultiSensor 6)
the current situation is:
- calibration settings for temp are not reflected
- when the Sensor sends “Alarm” also all values (temp, lux, etc.) go to 255
- when the Alarm is reset all values go to 0
- next interval the normal values come back (however temp calibration seems never to work)
Ok - I’ll need a log of the alarm coming in I suspect…
here we go 
18:16:24.733 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 09 00 04 00 09 03 20 01 FF 26
18:16:24.736 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_152faff77f7_serial_sof changed from 163 to 164
18:16:24.742 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:16:24.744 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 04 00 09 03 20 01 FF 26
18:16:24.745 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 04 00 09 03 20 01 FF 26
18:16:24.746 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 09 03 20 01 FF
18:16:24.747 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DONE)
18:16:24.748 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class BASIC
18:16:24.748 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 9: Received Basic Request
18:16:24.749 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 9: Basic Set sent to the controller will be processed as Basic Report
18:16:24.750 [DEBUG] [.commandclass.ZWaveBasicCommandClass] - NODE 9: Basic report, value = 0xFF
18:16:24.750 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveCommandClassValueEvent
18:16:24.751 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
18:16:24.752 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
18:16:24.756 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
18:16:24.757 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = BASIC, value = 255
18:16:24.761 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw100_00_000_152faff77f7_node9_sensor_relhumidity changed from 43 to 255
18:16:24.763 [DEBUG] [ssage.ApplicationCommandMessageClass] - Transaction not completed: node address inconsistent.
18:16:24.768 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw100_00_000_152faff77f7_node9_sensor_ultraviolet changed from 0 to 255
18:16:24.772 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw100_00_000_152faff77f7_node9_sensor_temperature changed from 22.9 to 255
18:16:24.777 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_aeon_zw100_00_000_152faff77f7_node9_sensor_luminance changed from 0 to 255
18:16:25.055 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C
18:16:25.058 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
18:16:25.059 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C
18:16:25.060 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 09 0A 71 05 00 00 00 FF 07 08 00 00 6C
18:16:25.061 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class = ApplicationCommandHandler (0x04), type = Request (0x00), payload = 00 09 0A 71 05 00 00 00 FF 07 08 00 00
18:16:25.062 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_serial_zstick_152faff77f7_serial_sof changed from 164 to 165
18:16:25.064 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Application Command Request (ALIVE:DONE)
18:16:25.066 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 9: Incoming command class ALARM
18:16:25.068 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Received Alarm Request
18:16:25.069 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Process Alarm Report, V3, length 13
18:16:25.071 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm report - 0 = 0, source=0, event=8, status=255
18:16:25.072 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 9: Alarm Type = General (0)
18:16:25.073 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
18:16:25.074 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveAlarmValueEvent
18:16:25.075 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
18:16:25.078 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got an event from Z-Wave network: ZWaveAlarmValueEvent
18:16:25.080 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 9: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
Looks like an error in the export of the database since all channels are getting the BASIC tag… (@xsnrg I have a feeling this might also relate to your CT100 issue with the data flicking back and forward).
I’ll look into what’s happening with the database and will regenerate the files tonight…
Actually, this was just an error in the database for the ZW100 - the MULTILEVEL_SENSOR class had the ‘treat as basic’ box ticked…