Naming Zwave Device in Habmin

I have about 13 different zwave devices now connected to Aeon Z Stick and setup with Habmin and OpenHab.

But I can never get Habmin to change the name of the device to help remember what Node5, Node6, etc are. For each node, I use the +/- dropdown in Habmin yet attempts to edit the name do nothing. I’ve tried with both Chrome and IE browsers but can never edit that Name field.

Can anyone else edit that field without issue?

Yes, naming is working fine, at least through Firefox.
Just double click the area below the node name …

Thanks.

Does the name ‘stick’ for you though? I’ll set the name for the device and then a few seconds later is goes back to being blank?

Mine did this and then all of a sudden it changed to Chinese symbols, now it won’t change. Other devices have stuck though, so it must have to be supported by the hardware.

It DOES work BUT there is a magic sequence of keystrokes in my experience. You should experiment with variants of:

a. when you enter the data in a field, how do you exit the field ? try — , tab, arrow key, as variant – IT DOES MATTER …
b. when you find the combination which is sticky in habmin UI for you…make sure to click the save icon in toolbar when done.

Just a note on this - the name is saved in the node files - if the device doesn’t initialise, then it won’t get saved (I don’t think thats the issue here, but just mentioning it).

I’m getting the same chinese symbols now after I change a name. I’m still experimenting between web browsers and key combinations but still haven’t got it to stick properly.

I am using the zwave 1.8 binding with habmin 1.7 as well, although not sure if that would make a difference.

Where are the node files stored? Can something be checked and changed manually?

[quote=“ptmuldoon, post:7, topic:6287, full:true”]
Where are the node files stored?[/quote]

/var/lib/openhab/zwave (apt-get install)
/opt/openhab/etc/zwave (manual install)

Still working fine here, OH 1.8.0, z-wave binding 1.8.0, habmin 1.7.0-snapshot

I’ve tried now stopping OpenHab and then manually changing the field in the node xml file. And then when I restarted OpenHab, in habmin and the xml the name changed back to those strange chinese characters.

All very strange as others seem able to actually change the name.

@ptmuldoon, Have you found a fix for the weird Chinese characters? I’m having the same issue. After @chris mentioned the node xml files, I deleted those and restarted OpenHab, still the same issue.

Happens for GE 45609 Switch and GE 45605 Duplex receptacle

OH 1.8.1, Zwave Binding 1.81, habmin 1.7.0-snapshot

@moberlin8 - I have not found a fix and gave up on it for a while. I can retry it later tonight though when back home. I know i tried in multiple browsers as well as changing the xml and couldn’t get anything to show correctly.

I’m slowly getting ready for OH2 as well, thus why haven’t worried as much about it currently.

Can anyone confirm if this still happens in the latest binding. There was a problem with null handling when receiving nose names which should be fixed.

Works fine in 1.8.1 :slightly_smiling:
But: I also had never problems renaming nodes in 1.7.1 and 1.8.0 …

Thanks. It will also depend on your device(s) - if they don’t support the NodeNaming command class, then it wouldn’t be a problem anyway (none of my devices seem to implement it)

I’m back looking at this again and seems I had success in somehow naming the first 3 item in Habmin under OH1. Yet, my remaining switches (same device models) are showing the strange Chinese symbols.

And I think those symbols or lack of any name is causing all sorts of warning and errors in the log of improper names lengths.

I really don’t think this has anything to do with browser versions, but perhaps some weird quick in a possible error somewhere else I could have in OH1 with an items or rules files that then throws a conflict. That’s just me guessing I see some other strange errors that I do not remember seeing in the past as well.

Yes - OH1 still has the bug that I think should be fixed in OH2 now so I will try and port this over in the coming days…

@chris

Thanks Chris. If it helps, here is some of the log. First most of my nodes report an Warning on a Scene being unsupported and then get an error and warning on the name. It also looks like it trys to read/resolve the name 12 times and then moves onto the next node doing the same thing.

There are all primarily Leviton Switch (DZS15-1LZ) and Leviton Dimmer Switches (DZMX-1LZ)

2016-03-24 15:07:44.464 [INFO ] [rialApiGetInitDataMessageClass] - ------------Number of Nodes Found Registered to ZWave Controller------------
2016-03-24 15:07:44.464 [INFO ] [rialApiGetInitDataMessageClass] - # Nodes = 14
2016-03-24 15:07:44.464 [INFO ] [rialApiGetInitDataMessageClass] - ----------------------------------------------------------------------------
2016-03-24 15:07:44.900 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 16: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.911 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 15: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.923 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 12: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.931 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 17: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.943 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 8: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.955 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 11: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.963 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 14: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.982 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 10: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:44.991 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 18: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:45.003 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 9: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:45.048 [WARN ] [.o.b.z.i.p.c.ZWaveCommandClass] - NODE 3: Unsupported command class SCENE_ACTUATOR_CONF
2016-03-24 15:07:45.399 [ERROR] [.c.ZWaveNodeNamingCommandClass] - NODE 16 : Node Name report error in message length
2016-03-24 15:07:45.399 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 16: Node name: null
2016-03-24 15:07:45.399 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No converter found for command class = NODE_NAMING, ignoring event.
2016-03-24 15:07:45.431 [ERROR] [.c.ZWaveNodeNamingCommandClass] - NODE 16 : Node Name report error in message length
2016-03-24 15:07:45.431 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 16: Node location: null
2016-03-24 15:07:45.431 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - No converter found for command class = NODE_NAMING, ignoring event.
2016-03-24 15:07:45.463 [ERROR] [.c.ZWaveNodeNamingCommandClass] - NODE 16 : Node Name report error in message length
2016-03-24 15:07:45.463 [INFO ] [.c.ZWaveNodeNamingCommandClass] - NODE 16: Node name: null

Same problem here. Got to poking around the xml files and noticed that when the odd characters are present that the ‘<’ at the beginning of the

 tag was missing. Stopping OpenHab, manually editing the xml file and starting OpenHab shows the same old weird characters.
        

I also just tried the re-naming of my device and got the following error:

2016-03-29 10:31:53.628 [ERROR] [.z.i.config.ZWaveConfiguration] - NODE 2: Error in doSet - no database found

Which database is meant here?

Thx. J.

I believe this is a bug in the XML library as it should (IMHO!) be capable of reading and writing the same data. However, this is something I’ve been trying to resolve - I pushed a change to the OH2 repo a few days back and will do the same to the OH1 repo today. Hopefully it will help.