forum

Hello,

Whats the correct way of getting the device name as it is set in the Webinterface e.g in the Device Status list? Command class NodeNaming doesn't seem to work because

zway.devices[2].instances[0].NodeNaming.data.nodename.value;

for example returns "Cannot read property 'data' of undefined". But

zway.devices[2].instances[0].SwitchBinary.data.level.value

for example works without problems.

For me that call
zway.devices[N].instances[0].NodeNaming.data.nodename.value; (copied this straight from my s/w)
works for the devices that are capable of setting the device name (see under Expert Commands for your devices.
Similarly for location
zway.devices[N].instances[0].NodeNaming.data.location.value;

May be your device does not support NodeNaming CC. Our UI use a Rules.xml file to store names. This will change in the next UI, so please be prepared to this.

@Poltos or Community
I am as well looking for a way to get the NodeNames from ZWay via http. Have you changed Software in the meantime as announced last Year? Any Idea about how Zway does/could propagate NodeNames via http?

We have changed it as promised. The s/w is under development now. There is a way to get widgets name via http (not nodes anymore, since one Z-Wave node can lead to many widgets).

.... and how can I achieve to this? I am currently using the latest development clone of your automation engine.

PoltoS wrote:We have changed it as promised. The s/w is under development now. There is a way to get widgets name via http (not nodes anymore, since one Z-Wave node can lead to many widgets).

Please stick to consistent terminology. Imho mixed use of "widget" and "virtual device" is confusing. If I understand this correctly a real world device (node in your terms) will be seen as 1 or several virtual devices in the new s/w.

It would be good if the core notions of this new global design gets described in the manuals. Has it been documented already somewhere?

A bit on the forum. We have started to redesign one part from scratch again, this caused a new delay. Still we have a hope to end up with something releasable soon...