Domoticz

Open source Home Automation System
https://forum.domoticz.com/

Zwave Control Panel Now Showing 3 Unknown Devices

https://forum.domoticz.com/viewtopic.php?t=15039

Page 1 of 2

Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Saturday 24 December 2016 11:39
by gcoupe
Woke up this morning to find problems with my Domoticz system. Three devices which were known yesterday (an Aeotec Smart Switch 6 and two Fibaro FGS 212 relay switches) are now showing up in the Openzwave control panel as unknown, and only as listening nodes. Domoticz still has them in its list, but naturally reports errors if I send a command to any of these devices. I've tried a network heal, but can't revive them.

Any suggestions as to how to get them back in operation, or do I have to remove all three nodes from the system and add them back in again? Thanks.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Saturday 24 December 2016 11:47
by Egregius
You could try commands like 'Has node failed' and/or 'Refresh Node Information' of OZWCP.
Give it a little time between different commands.
I asume you already did a shutdown and power up?

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Saturday 24 December 2016 12:20
by gcoupe
Thanks for the suggestions, but I'm afraid nothing has worked.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Saturday 24 December 2016 12:58
by Domosapiens
My suggestion:
Stop Open Zwave (disable the Z-Wave controller)
Remove from your config/zwcfg_0blabla.xml the concerned nodes. (the whole section from "<Node>" up-to "</Node>" )
Start Open Zwave.
Let Open Zwave/Domotics re-discover your faulty nodes.

For the two Fibaro FGS 212:
Add, if needed, a 1 to Group 3 of each node.
Group 3 is the lifeline, so a 1 must be there for the connection with the Z-Wave controller.
Create the connections via Hardware -> Z-Wave controller blue setup button -> Node management -> Groups & Network

For the Aeotec Smart Switch 6:
Without a type number, I can not check the config file. But you can find out yourself.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Saturday 24 December 2016 15:06
by gcoupe
@Domosapiens - thanks, that seems to have done the trick. The switches are now all working, but I notice that the network information table looks odd.
I can't add Group information to any of the three switches (the top three 20, 21 and 22 in the screenshot), and Group information seems to be missing from a lot of the devices. I'm sure it was present a few weeks ago when I last visited this screen.
Domoticz 52.png
Domoticz 52.png (183.64 KiB) Viewed 8299 times

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Monday 26 December 2016 1:00
by Domosapiens
How can you expect help if you don't tell what type of devices it are?
At least post a snapshot of the list of nodes.
Are they discovered by Z-wave according the correct type?
What was in the log file when you included?
What is in the zwcfg_0blabla.xml about these nodes (post in between code brackets)

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Monday 26 December 2016 10:36
by gcoupe
@Domosapiens wrote: "How can you expect help if you don't tell what type of devices it are?"

Look, I'm sorry if I've offended you, but much of the working of Domoticz remains a complete mystery to me, and I often don't know what is useful information to provide to aid in diagnosing issues.

Here's a screenshot of the OZW control panel showing the list of nodes at the time when the last three nodes were not working:
Domoticz 51.png
Domoticz 51.png (102.32 KiB) Viewed 8252 times
After following your suggestion (thank you again), here's the list of nodes as they now stand:
Domoticz 55.png
Domoticz 55.png (99.75 KiB) Viewed 8252 times
It seems to me that things have improved, but I notice that the Product data for these three nodes is still blank. Indeed, I notice that product data from other nodes is missing, and I'm sure that this was all present and correct originally.

If I list the nodes in Domoticz (as they now stand), then it seems to me that product data has been lost from the system somehow. Here's a screenshot of the nodes, with node 2 selected. Notice how the Manufacturer's data is missing, along with the entire Configuration section, and the ID and Type values are both 0x0000 - shouldn't they be 0x1000 and 0x0600?
Domoticz 53.png
Domoticz 53.png (270.88 KiB) Viewed 8252 times
It seems to me that data has been corrupted somewhere along the line, and the question is, is the source of errors the Aeotec USB stick itself, or in the Domoticz database?

I'd post the node information from the zwcfg_ file if I could find that, but the file seems to have completely changed in its structure and content, and nodes (other than the controller) are no longer listed in <Node>...</Node> sections...

If I need to delete the entire Zwave network from both Domoticz and the USB Stick and rebuild it, then so be it. It's a real pain, but it's probably better than trying to patch up the data.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Monday 26 December 2016 11:07
by Domosapiens
Ok. You did not offend me.

This info brings us somewere.

The zwcfg_0blabla.xml file (blabla is your specific Z-Stick number) is a file that is enriched for every node you include and used by Domoticz to store intermediate values.

Did you modify one of the manufaturer specific xml files yourself?
(if so, a xml file error in such file will disturb all successive node inclusions.)

All nodes with ID 0000 are not included correctly.
Because there are so many, my suggestion is:
- open a log window
- stop Z-Wave (disable your stick)
- backup and then remove the zwcfg_0blabla.xml
- enable you Z-stick
- look in the log how the zwcfg_0blabla.xml will be rebuild
- catch the errors, if there are any

Rebuilding the whole network is an ultimate solution, not needed yet.
(but if you do: first exclude the nodes!)

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Monday 26 December 2016 12:21
by gcoupe
@Domosapiens, thanks. I tried following the instructions, but things didn't seem to happen as expected...

1. I opened the log window in Domoticz
2. I disabled the stick - by removing it from the USB connector - is this what you meant?
3. I backed up and removed the zwcfg_0blabla.xml file.
4. I plugged the stick back in.
5. The log showed no messages about rebuilding the zwcfg file.

So I restarted Domoticz completely, and opened a new log window. Here's the content (note there's messages from Wunderground and my Slimme Meter in between the ZWave messages):

Code: Select all

2016-12-26 11:40:57.227 Domoticz V3.5877 (c)2012-2016 GizMoCuz
2016-12-26 11:40:57.227 Build Hash: 15b013c, Date: 2016-11-10 16:44:33
2016-12-26 11:40:57.289 Sunrise: 08:42:00 SunSet:16:26:00
2016-12-26 11:40:57.289 EventSystem: reset all events...
2016-12-26 11:40:57.305 Active notification subsystems: pushalot (1/12)
2016-12-26 11:40:57.320 WebServer(HTTP) started on address: :: with port 8080
2016-12-26 11:40:57.524 WebServer(SSL) started on address: :: with port 443
2016-12-26 11:40:57.524 Proxymanager started.
2016-12-26 11:40:57.524 Starting shared server on: :::6144
2016-12-26 11:40:57.524 TCPServer: shared server started...
2016-12-26 11:40:57.524 RxQueue: queue worker started...
2016-12-26 11:40:59.539 Wunderground: Worker started...
2016-12-26 11:40:59.555 Hardware Monitor: Warning, OpenHardware Monitor is not installed on this system. (http://openhardwaremonitor.org)
2016-12-26 11:40:59.555 P1 Smart Meter: Using serial port: COM3
2016-12-26 11:40:59.555 Hardware Monitor: Started
2016-12-26 11:40:59.571 EventSystem: reset all events...
2016-12-26 11:40:59.571 EventSystem: reset all device statuses...
2016-12-26 11:40:59.586 EventSystem: Started
2016-12-26 11:41:00.055 OpenZWave: Starting...
2016-12-26 11:41:00.055 OpenZWave: Version: 1.4.2246.ga583ba8.dirty
2016-12-26 11:41:00.071 OpenZWave: using config in: C:\Program Files (x86)\Domoticz\Config/
2016-12-26 11:41:00.305 OpenZWave: Driver Ready
2016-12-26 11:41:00.336 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.336 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.336 OpenZWave: Value_Added: Node: 6 (0x06), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.336 OpenZWave: Value_Added: Node: 7 (0x07), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.336 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: ALARM, Label: Alarm Type, Instance: 1
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: ALARM, Label: Alarm Level, Instance: 1
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: BATTERY, Label: Battery Level, Instance: 1
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.368 OpenZWave: Value_Added: Node: 12 (0x0c), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.415 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Level, Instance: 1
2016-12-26 11:41:00.430 (Z-Stick USB Gen 5) Lighting Limitless/Applamp (Fibaro RGBW)
2016-12-26 11:41:00.493 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Bright, Instance: 1
2016-12-26 11:41:00.493 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Dim, Instance: 1
2016-12-26 11:41:00.524 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-26 11:41:00.524 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: METER, Label: Energy, Instance: 1
2016-12-26 11:41:00.524 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: COLOR, Label: Color, Instance: 1
2016-12-26 11:41:00.524 (Z-Stick USB Gen 5) Lighting Limitless/Applamp (LEDs woonkamer)
2016-12-26 11:41:00.602 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: COLOR, Label: Color Index, Instance: 1
2016-12-26 11:41:00.618 OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.665 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.665 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-26 11:41:00.680 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-26 11:41:00.727 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.743 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-26 11:41:00.743 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-26 11:41:00.774 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.774 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-26 11:41:00.774 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Energy, Instance: 1
2016-12-26 11:41:00.790 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Power, Instance: 1
2016-12-26 11:41:00.790 OpenZWave: Value_Added: Node: 19 (0x13), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.790 OpenZWave: Value_Added: Node: 20 (0x14), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.790 OpenZWave: Value_Added: Node: 21 (0x15), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:00.790 OpenZWave: Value_Added: Node: 22 (0x16), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-26 11:41:03.055 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:41:03.087 (Smart Meter) P1 Smart Meter (Gas)
2016-12-26 11:41:10.004 (Lichtenvoorde weather) Temp + Humidity + Baro (Weather 1)
2016-12-26 11:41:10.058 (Lichtenvoorde weather) Wind (Wind)
2016-12-26 11:41:10.096 (Lichtenvoorde weather) UV (UV)
2016-12-26 11:41:10.178 (Lichtenvoorde weather) Rain (Unknown)
2016-12-26 11:41:10.270 (Lichtenvoorde weather) General/Visibility (Unknown)
2016-12-26 11:41:13.057 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:41:18.855 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-26 11:41:19.862 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-26 11:41:20.889 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-26 11:41:21.953 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-26 11:41:23.016 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:41:23.069 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:41:24.037 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:41:25.056 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:41:33.073 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:41:36.010 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 15 (0x0f)
2016-12-26 11:41:37.056 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 17 (0x11)
2016-12-26 11:41:38.081 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 17 (0x11)
2016-12-26 11:41:39.106 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 18 (0x12)
2016-12-26 11:41:40.130 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 18 (0x12)
2016-12-26 11:41:41.148 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-26 11:41:42.164 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 4 (0x04)
2016-12-26 11:41:43.065 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:41:43.182 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 6 (0x06)
2016-12-26 11:41:44.651 Incoming connection from: 192.168.178.21
2016-12-26 11:41:53.056 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:03.037 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:13.050 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:13.927 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:13.957 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:13.996 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:14.030 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:16.710 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:16.765 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:17.709 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:17.766 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:20.709 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:20.767 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:21.710 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:42:21.767 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:42:23.048 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:24.024 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:42:24.862 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:42:24.900 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:42:33.071 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:35.278 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-26 11:42:36.314 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-26 11:42:37.347 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-26 11:42:38.363 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 12 (0x0c)
2016-12-26 11:42:39.380 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 12 (0x0c)
2016-12-26 11:42:40.407 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-26 11:42:43.067 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:52.423 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-26 11:42:53.070 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:42:53.439 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-26 11:42:54.455 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-26 11:42:55.492 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-26 11:42:56.523 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:42:57.539 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:43:03.068 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:13.072 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:23.066 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:30.751 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:30.812 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:33.061 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:34.868 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:34.922 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:40.398 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-26 11:43:41.184 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:41.221 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:41.546 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:41.599 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:41.999 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:42.054 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:42.155 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:42.317 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:42.371 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:42.402 OpenZWave: Awake Nodes queried
2016-12-26 11:43:43.086 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:47.854 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:47.917 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:48.870 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:48.917 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:49.870 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:49.901 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:50.855 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:43:50.901 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:43:53.085 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:43:54.716 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:54.753 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:57.716 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:57.752 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:58.715 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:58.753 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:43:59.717 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:43:59.769 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:44:00.716 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:44:00.754 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:44:03.086 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:44:04.871 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:44:04.918 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:44:13.084 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:44:17.867 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:44:17.929 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:44:19.867 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:44:19.899 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:44:20.867 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:44:20.914 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:44:21.868 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-26 11:44:21.931 (Z-Stick USB Gen 5) General/kWh (kWh Meter)
2016-12-26 11:44:23.084 (Smart Meter) P1 Smart Meter (Power)
2016-12-26 11:44:24.716 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:44:24.768 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:44:30.718 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-26 11:44:30.771 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-26 11:44:32.719 (Z-Stick USB Gen 5) Usage (Unknown)
The zwcfg file has been recreated, and here's the OZW log (I've removed blank lines from the log output):

Code: Select all

Logging started 2016-12-26 11:41:00.086 
2016-12-26 11:41:00.102 Always, OpenZwave Version 1.4.2246 Starting Up
2016-12-26 11:41:18.855 Error, Node019, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:18.855 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:19.855 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:19.855 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:20.870 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:20.870 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:21.895 Error, Node022, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:21.895 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:22.961 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:22.961 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:24.022 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:24.022 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:25.040 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:25.040 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:25.895 Error, Node014, ERROR: Dropping command, expected response not received after 6 attempt(s)
Dumping queued log messages
2016-12-26 11:41:25.895 4740 ERROR: Dropping command, expected response not received after 6 attempt(s)
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
2016-12-26 11:41:35.983 Error, Node015, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:35.983 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:37.025 Error, Node017, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:37.025 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:38.059 Error, Node017, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:38.059 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:39.085 Error, Node018, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:39.085 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:40.115 Error, Node018, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:40.115 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:41.132 Error, Node002, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:41.132 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:42.148 Error, Node004, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:42.148 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:41:43.166 Error, Node006, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:41:43.166 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:13.896 Error, Node007, ERROR: Dropping command, expected response not received after 6 attempt(s)
Dumping queued log messages
2016-12-26 11:42:13.896 4740 ERROR: Dropping command, expected response not received after 6 attempt(s)
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
2016-12-26 11:42:14.009 Error, Node013, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:42:14.009 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:42:24.008 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:24.008 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:35.256 Error, Node019, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:35.256 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:36.293 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:36.293 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:37.331 Error, Node011, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:37.331 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:38.347 Error, Node012, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:38.347 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:39.365 Error, Node012, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:39.365 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:40.383 Error, Node020, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:40.383 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:42.335 Error, Node020, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:42:42.335 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:42:42.350 Error, Node020, ERROR: Dropping command, expected response not received after 6 attempt(s)
Dumping queued log messages
2016-12-26 11:42:42.350 4740 ERROR: Dropping command, expected response not received after 6 attempt(s)
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
2016-12-26 11:42:42.397 Error, Node021, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:42:42.397 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:42:52.408 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:52.408 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:53.423 Error, Node021, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:53.423 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:54.439 Error, Node022, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:54.439 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:55.470 Error, Node022, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:55.470 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:56.507 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:56.507 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:42:57.524 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:42:57.524 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
2016-12-26 11:43:30.266 Error, Node013, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:43:30.266 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:43:30.304 Error, Node013, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:43:30.304 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:43:30.319 Error, Node013, ERROR: Dropping command, expected response not received after 6 attempt(s)
Dumping queued log messages
2016-12-26 11:43:30.319 4740 ERROR: Dropping command, expected response not received after 6 attempt(s)
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
Dumping queued log messages
End of queued log message dump
2016-12-26 11:43:30.366 Error, Node013, ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
Dumping queued log messages
2016-12-26 11:43:30.366 4740 ERROR: ZW_SEND_DATA could not be delivered to Z-Wave stack
End of queued log message dump
2016-12-26 11:43:40.379 Error, Node013, ERROR: Dropping command, expected response not received after 1 attempt(s)
Dumping queued log messages
2016-12-26 11:43:40.379 4740 ERROR: Dropping command, expected response not received after 1 attempt(s)
End of queued log message dump
The end result is that the node information is the same as shown in my previous message - the errors have not been caught and corrected.

You asked if I have modified one of the manufacturer-specific xml files myself. I did - over a year ago - and added information about a Z-Wave.me outdoor switch. But that modified file hasn't been in my Domoticz setup for months now, since it is now included in the OpenZwave library.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Monday 26 December 2016 20:22
by Domosapiens
Complicated ...
2) Removing the USB stick is not correct!
Disable the stick on the hardware page: click on the Z-sitck Gen5 line. Uncheck the box and push update.

Did you delete the home-made Z-Wave.Me ZME_064381 Switch xml file? No leftover in the folder?

About all those timeouts ...
Is your Z-stick hidden behind your computer, or can it transmit in free space.
Use a short USB extension cable to bring it to free space.

For test purposes also disable Wunderground and my Slimme Meter (minimal disturbance during the Z-Wave discovery phase)
Then, publish a picture like Domoticz 53.png
All nodes need to be recognized with the correct ID, before we can go on.

- open a log window
- stop Z-Wave (disable your stick)
- backup and then remove the zwcfg_0blabla.xml
- enable you Z-stick
- look in the log how the zwcfg_0blabla.xml will be rebuild
- catch the errors, if there are any

The message: All nodes queried is the moment that the zwcfg_0blabla.xml is rebuild again

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Tuesday 27 December 2016 10:02
by gcoupe
Ah - sorry for my misunderstanding about "disable", here's the result of following your instructions properly...

The homemade ZME_064381 xml file has long since been deleted. The current entry is from the OpenZWave library (it was added a year ago).

The stick is sitting on a windowsill (plugged into a USB holder so that the stick is vertically oriented. The USB extension cable between the holder and the computer is about 1.5 meters long.

Here's the log file during the regeneration phase:

Code: Select all

2016-12-27 09:44:30.199 OpenZWave: Closed
2016-12-27 09:44:31.337 (Smart Meter) P1 Smart Meter (Power)
2016-12-27 09:44:40.639 P1 Smart Meter: Serial Worker stopped...
2016-12-27 09:44:48.323 Wunderground: Worker stopped...
2016-12-27 09:45:50.926 OpenZWave: Starting...
2016-12-27 09:45:50.926 OpenZWave: Version: 1.4.2246.ga583ba8.dirty
2016-12-27 09:45:50.926 OpenZWave: using config in: C:\Program Files (x86)\Domoticz\Config/
2016-12-27 09:45:51.135 OpenZWave: Driver Ready
2016-12-27 09:45:51.135 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 1 (0x01)
2016-12-27 09:45:51.135 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:45:51.135 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 4 (0x04)
2016-12-27 09:45:51.136 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 6 (0x06)
2016-12-27 09:45:51.136 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 7 (0x07)
2016-12-27 09:45:51.136 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 9 (0x09)
2016-12-27 09:45:51.136 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 10 (0x0a)
2016-12-27 09:45:51.136 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 12 (0x0c)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 14 (0x0e)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 15 (0x0f)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 17 (0x11)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 18 (0x12)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-27 09:45:51.137 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-27 09:45:51.138 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-27 09:45:51.138 OpenZWave: New Node added. HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-27 09:45:51.196 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:51.223 OpenZWave: Value_Added: Node: 4 (0x04), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:51.251 OpenZWave: Value_Added: Node: 6 (0x06), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:51.316 OpenZWave: Value_Added: Node: 7 (0x07), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:51.343 OpenZWave: Value_Added: Node: 9 (0x09), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:51.392 OpenZWave: Value_Added: Node: 10 (0x0a), CommandClass: SENSOR BINARY, Label: Sensor, Instance: 0
2016-12-27 09:45:57.010 OpenZWave: Value_Added: Node: 11 (0x0b), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.039 OpenZWave: Value_Added: Node: 12 (0x0c), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.066 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Level, Instance: 1
2016-12-27 09:45:57.067 (Z-Stick USB Gen 5) Lighting Limitless/Applamp (Fibaro RGBW)
2016-12-27 09:45:57.147 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Bright, Instance: 1
2016-12-27 09:45:57.147 OpenZWave: Value_Added: Node: 13 (0x0d), CommandClass: SWITCH MULTILEVEL, Label: Dim, Instance: 1
2016-12-27 09:45:57.174 OpenZWave: Value_Added: Node: 14 (0x0e), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.202 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.266 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.296 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:45:57.322 OpenZWave: Value_Added: Node: 19 (0x13), CommandClass: SWITCH BINARY, Label: Switch, Instance: 1
2016-12-27 09:46:07.338 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-27 09:46:08.353 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-27 09:46:09.367 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-27 09:46:10.391 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-27 09:46:11.404 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-27 09:46:12.421 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-27 09:46:13.438 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-27 09:46:24.461 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 4 (0x04)
2016-12-27 09:46:25.478 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 4 (0x04)
2016-12-27 09:46:26.497 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 6 (0x06)
2016-12-27 09:46:27.540 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 6 (0x06)
2016-12-27 09:46:28.556 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 7 (0x07)
2016-12-27 09:46:29.574 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 7 (0x07)
2016-12-27 09:46:30.594 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 9 (0x09)
2016-12-27 09:46:31.611 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 9 (0x09)
2016-12-27 09:46:32.628 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-27 09:47:02.436 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-27 09:47:12.352 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-27 09:47:12.521 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-27 09:47:12.631 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-27 09:47:12.673 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Unknown, Instance: 1
2016-12-27 09:47:22.690 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-27 09:47:23.708 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-27 09:47:24.727 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-27 09:47:25.750 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 20 (0x14)
2016-12-27 09:47:26.767 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-27 09:47:27.788 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 21 (0x15)
2016-12-27 09:47:28.813 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 22 (0x16)
2016-12-27 09:47:39.872 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 6 (0x06)
2016-12-27 09:47:40.894 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 7 (0x07)
2016-12-27 09:47:41.913 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 9 (0x09)
2016-12-27 09:47:42.931 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:47:43.953 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:47:44.974 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:28.806 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 19 (0x13)
2016-12-27 09:48:29.828 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-27 09:48:30.849 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 11 (0x0b)
2016-12-27 09:48:31.868 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 12 (0x0c)
2016-12-27 09:48:32.887 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 12 (0x0c)
2016-12-27 09:48:33.907 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 13 (0x0d)
2016-12-27 09:48:48.206 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:49.224 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:50.251 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:51.271 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:52.297 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 2 (0x02)
2016-12-27 09:48:53.320 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 14 (0x0e)
2016-12-27 09:49:33.879 OpenZWave: Received timeout notification from HomeID: 3550212702, NodeID: 15 (0x0f)
2016-12-27 09:49:36.723 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: METER, Label: Power, Instance: 1
2016-12-27 09:49:37.800 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: METER, Label: Power, Instance: 1
2016-12-27 09:49:39.683 OpenZWave: Value_Added: Node: 2 (0x02), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-27 09:49:39.684 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:39.721 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:40.107 (Z-Stick USB Gen 5) Light/Switch (Bijgebouw Heater)
2016-12-27 09:49:40.279 OpenZWave: Value_Added: Node: 15 (0x0f), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-27 09:49:40.280 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:40.339 OpenZWave: Value_Added: Node: 17 (0x11), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-27 09:49:40.315 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:40.350 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:40.387 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:40.610 (Z-Stick USB Gen 5) Light/Switch (Degas & Network)
2016-12-27 09:49:40.673 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:40.710 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:40.743 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:40.777 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:40.836 OpenZWave: Value_Added: Node: 18 (0x12), CommandClass: SENSOR MULTILEVEL, Label: Power, Instance: 4
2016-12-27 09:49:40.810 (Z-Stick USB Gen 5) Light/Switch (CV)
2016-12-27 09:49:40.865 (Z-Stick USB Gen 5) Usage (CV Usage)
2016-12-27 09:49:40.899 (Z-Stick USB Gen 5) Usage (CV Power Meter)
2016-12-27 09:49:40.941 (Z-Stick USB Gen 5) Usage (Unknown)
2016-12-27 09:49:40.975 (Z-Stick USB Gen 5) Usage (Power Meter)
2016-12-27 09:49:41.030 OpenZWave: Awake Nodes queried
And here's the result - still having the problem that devices aren't being recognised properly. Could this be caused by the timeout errors?
Domoticz 56.png
Domoticz 56.png (325.73 KiB) Viewed 8187 times

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Tuesday 27 December 2016 12:43
by Domosapiens
gcoupe ... complicated ..
- those timeouts are not correct
- the nodes with ID 0000 are not correct
The USB extension cable between the holder and the computer is about 1.5 meters long
Just a guess: cable too long? Quality insufficient?
The stick is sitting on a windowsill
Just a guess: try another position. Could it be reflection and wave interference from the window ?(isolated glass has a metal raster inside!)


The registration of a node is a multi-step query process, explained here:
http://www.domoticz.com/forum/viewtopic ... 271#p40847

Can you post the first line of node 4 (as example) from the the zwcfg_xxxx.xml
It will look something like this

Code: Select all

   <Node id="18" name="Unknown" location="" basic="4" generic="17" specific="6" type="Motor Control Class B" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="SecurityReport">
to see in what stage the hick-up is.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Tuesday 27 December 2016 16:02
by gcoupe
Here's the listing for Node 4:

Code: Select all

<Node id="4" name="" location="" basic="4" generic="16" specific="0" type="Binary Switch" listening="true" frequentListening="false" beaming="true" routing="true" max_baud_rate="40000" version="4" query_stage="Complete">
        <Manufacturer id="0" name="">
            <Product type="0" id="0" name="" />
        </Manufacturer>
        <CommandClasses>
            <CommandClass id="32" name="COMMAND_CLASS_BASIC" version="1" mapping="37">
                <Instance index="1" />
            </CommandClass>
            <CommandClass id="37" name="COMMAND_CLASS_SWITCH_BINARY" version="1">
                <Instance index="1" />
                <Value type="bool" genre="user" instance="1" index="0" label="Switch" units="" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="0" value="False" />
            </CommandClass>
        </CommandClasses>
    </Node>
I'll try different cables and positions to see if that affects the timeouts. Thanks.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Tuesday 27 December 2016 20:09
by Domosapiens
Thanks.
It shows
query_stage="Complete"
That is OK
<Manufacturer id="0" name="">
<Product type="0" id="0" name="" />
That is wrong!

Remove this zwcfg_xxxx.xml before you start experimenting with Z-Wave stick USB cable and position:
- disable your Z-Wave stick
- remove zwcfg_xxxx.xml
- enable your Z-Wave stick
- let the zwcfg_xxxx.xml be rebuild upto "all nodes are queried"
- check for Manufacturer and Product id's

Another option is to Exclude one of the faulty nodes and Include it again, to see if anything is corrupt on your Z-Wave stick.

You could try using the Zensys tool, to see if there are irregularities
https://aeotec.freshdesk.com/support/so ... ensys-tool

Keep trying!
You have enough nodes to build a rock solid meshed Z-Wave network (unless you live in a castle ;)

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Wednesday 28 December 2016 9:04
by gcoupe
Still battling Z-Wave here. Each time I try different cables or positions and recreate the zwcfg file, I'm getting timeout errors - and more and more of my devices are now being marked as dead. Is there no easy way to unmark them? Or must I go through the process of excluding the node and then re-including it? Then it will have a new nodeid, so presumably all my Blockly scripts need to be reworked.

My network has been working without issue for almost two years. It's only in the last month that I've added three new nodes: an Aeotec Smart Switch 6 and two Fibaro FGS212 relay switches. It doesn't fill me with confidence if the act of adding these devices has somehow destabilised the entire network.

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Wednesday 28 December 2016 10:36
by mark.sellwood
I see your on version V3.5877, did these problems start after upgrading?

My system was working fine on V3.4843, I upgraded to V3.5877 & it worked for a couple of weeks until I added some GreenWave PowerNode 1 port sockets then I started to see the same as you.
After a reboot previous working devices became dead with ID & Type codes showing 0x0000, nothing I did recovered it so I reverted back to V3,4843 & all came good.
Fortunately when I do an upgrade I build a new SD card following the wiki http://www.domoticz.com/wiki/Installing ... spberry_PI then I import the database from the old card.
To revert back all I need to do is put the old SD card back in & I'm good.

I think there is some issue with OZW & V3.5877 but I don't have the skills to find out what.

I know this doesn't help you but maybe someone can help.
I'm sure there are other reports of this issue.
http://www.domoticz.com/forum/viewtopic ... 24&t=14755
http://www.domoticz.com/forum/viewtopic.php?f=6&t=14136

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Wednesday 28 December 2016 11:05
by gcoupe
Hmm. Thanks for your message. Well, indeed the problems did start after I upgraded to the latest stable version, so it's possible that there is a connection. I'm starting to get worried...

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Thursday 29 December 2016 8:40
by gcoupe
So, I've almost got a fully-working system again (thanks to Domosapiens), but there's one problem that still remains at the moment.

I've had to exclude and then re-include all the nodes that were marked as dead - but one node (node ID 025, previously 014) refuses to come alive. It's been excluded and then included, but the Aeotec USB stick is still reporting it as dead. This is despite the fact that the exclusion/inclusion process clearly worked. It's also not because the node is out-of-range in the network - in fact it's the node physically closest to the stick (3 meters away).

How can I make the USB stick see the node as working?
Domoticz 57.png
Domoticz 57.png (253.14 KiB) Viewed 8073 times

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Thursday 29 December 2016 20:53
by Domosapiens
Nice to see that you have progress.
What did the trick ? Moving away from the window?

Now for node 025:
- disable your Z-Wave stick
- backup zwcfg_xxxx.xml
- edit zwcfg_xxxx.xml:
- delete the part: <Node id="25" ....upto .... </Node>
- make sure you do not corrupt the xml structure! (using a xml editor with syntax check make life safer!)
- safe the zwcfg_xxxx.xml
- enable your Z-Wave stick
Check node 25 as soon as "all nodes are queried" is in the log

Re: Zwave Control Panel Now Showing 3 Unknown Devices

Posted: Friday 30 December 2016 9:36
by gcoupe
@Domosapiens, thanks for the suggestions.

I'm still getting some timeouts, but they are from nodes out in the garden and outbuildings. I'll keep experimenting with different cables and positions. I see that the Aeotec Zstick has a setting to enable a nightly Heal Network at 04:00. Is it worth turning this on, to keep the network in shape?

Node 25 was still being reported with no manufacturer name, and with 0 for the ID and Type numbers, so I ended up removing node 25 and adding it in as a new node. That seems to have worked and I now have the network back to normal. Thanks again for your help.
All times are UTC+02:00
Page 1 of 2

Powered by phpBB® Forum Software © phpBB Limited