LinuxMCE Forums
General => Users => Topic started by: CentralMedia on October 22, 2018, 12:28:17 am
-
Sometime back, I had a aeotec labs usb stick and used to include my lights via the built in inclusion remote on it.
I have been inactive for sometime, but re-attempting to add some lights with the new gen 5 stick (Aeotec Z-Stick Gen5), seems I am doing something incorrect , not showing up.
Looking at the following link (http://wiki.linuxmce.org/index.php/ZWave), is it now, you should use an inclusion remote?
Is it, you can't used the built in inclusion remote in the stick (Aeotec Z-Stick Gen5) I am using?
-
Hello
I have the same Z-wave stick.
From trial and error and off the top of my head, the way i include devices is take the stick out of the host computer, go to the device one wishes to include, press the button on the stick until it flashes indicating inclusion mode, put the light or other device into inclusion mode. Once the devices are included the usb stick should flash more rapidly telling that the inclusion was successful.
If this is a light, some lights do not have an inclusion button. With this all I did was fit the light but before turning it on, bring the usb stick to the light you want to include, put the stick into include mode then turn the light on. This should include the device.
Sometimes I have had trouble including devices or things get messed up. if you have problems, try excluding all the devices first, by this i mean put the controller and device into exclusion mode, this is a long press and hold on the remote and it should flash differently, the same process above for inclusion but excluding the device and start over again including them. Most devices are different on how they are included/excluded so check the manual of each device for more details. My last light didn't come with any so I had to figure it out..
A last resort is resetting the controller from the "Soft reset controller" in the Advanced ZWave page of the lmce admin. then deleting the ZWave devices. Note that this doesn't automatically exclude the devices, lights, sensors that have been included so those devices need to be excluded even after a reset of the controller
So if you have any problems I would try excluding the devices first and starting over. If the device has been used with a previous controller, try excluding it with that first and including with the new one.
I have reset the controller before this will remove all the devices the stick remembers, but the devices seem to remember and you also have to exclude them first. Remember to quick reload router.. Sometimes you will need to reboot if there is a problem and ZWave gets stuck.
Sure someone with better knowledge will chime in :)
HTH
Gav
EDIT: I knew I had something wrong. The part about Soft reset isn't right, I had to enter a specially crafted command to send to the device which did a hard reset but I cannot remember that off hand. Still the exclusion or reset of other devices needs to be done.
-
Thanks
I had followed the procedure to include devices, only did one so far, out of four I have, a new GE switch.
Will try your suggestion on excluding and re-including, as had already rebooted the core, when I saw nothing come up to add the light, after including the light and plugging it back into the USB port on the core. That time, it only detected the controller again. On the reboot, it brought up the setup wizard, but no lights were added.
-
Quick Verification
I am seeing tree (3) devices added for my zwave controller, see below. Should there be a Device for "ZWave Embedded Light Interfa"?
Device 45 -> Device Template #: 1754 Seems default device
Device 46 -> Device Template #: 1820 (ZWave Embedded Climate Interfa)
Device 47 -> Device Template #: 1922 (ZWave Embedded Security Interf)
-
That's it!
I have the same, the lights are controlled by the parent ZWave device here.
Here is a paste of one of my lights in Wizard > Devices > Lights
(some dimmer)
Device #: 170
Device Template #: 38
Controlled by: ZWave
In the LMCE web admin and the top menu Automation > Advanced ZWave will show more info.
Sometimes in the past I have had to delete all those devices you pasted after messing around to force re-reading, then remove the usb stick and rebooted. you will have to add everything again but if things go crazy that is a sure fire way to start over after resetting all the devices but only do that as a last resort. Things work for me here now so I haven't done that for a while, sometimes it takes some time for Zwave settings to stick I think I just had to keep trying until I got it working.
Edit: if you want lots of info you can also do this
tail -f /var/log/pluto/${your_parent_ZWave_device_number}_ZWave.log
Or connect to the screen session that is running for the device; screen -ls
that can be of great help in finding problems.
-
In the LMCE web admin and the top menu Automation > Advanced ZWave, use the button Add device. That how i always have done with great success.
BR Daniel
-
I tried the automation -> zwave, what I am seeing is attached, just telling me message.
When I plug in the device, I do get the wizard, but it keeps saying the device times out. Before I restarted, was getting message timeouts in the zwave log
Timeouts Before Restart
with device <0xb4fffb40>
05 10/28/18 12:39:11.156 ZWInterface::OnNotification() : Type_ControllerCommand: State Command has completed succe
ssfully <0xb4fffb40>
05 10/28/18 12:40:32.818 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:41:33.845 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
01 10/28/18 12:42:06.000 AlarmCallback(): trying to revive node 2 for the 1 time <0xb6d77b40>
05 10/28/18 12:42:07.024 ZWInterface::OnNotification() : Message timed out, node 2 <0xb4fffb40>
01 10/28/18 12:42:10.000 AlarmCallback(): trying to revive node 5 for the 1 time <0xb6d77b40>
05 10/28/18 12:42:11.000 ZWInterface::OnNotification() : Message timed out, node 5 <0xb4fffb40>
05 10/28/18 12:42:34.886 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:43:35.913 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:44:36.967 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:45:37.990 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:46:39.017 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:47:40.259 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:48:41.404 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:49:42.436 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:50:43.491 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:51:44.532 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:52:45.604 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:53:46.644 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:54:47.692 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:55:48.752 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:56:49.807 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:57:50.888 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:58:51.922 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 12:59:52.952 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 13:00:53.996 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
What I see after restart
05 10/28/18 12:59:52.952 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
05 10/28/18 13:00:53.996 ZWInterface::OnNotification() : Message timed out, node 4 <0xb4fffb40>
== ATTEMPT FRESH START ==
1 10/28/18 13:02:44 /usr/pluto/bin/Spawn_Device.sh 42 (spawning-device) 18535 Dev: 42; Already Running list: 15,16,17,18,27,37,
== FRESH START ==
1 10/28/18 13:02:44 /usr/pluto/bin/Spawn_Device.sh 42 (spawning-device) device: 42 ip: localhost cmd_line: ZWave
0 10/28/18 13:02:44 42 (spawning-device) Entering 42
========== NEW LOG SECTION ==========
1 10/28/18 13:02:44 42 (spawning-device) Starting... 1
1 10/28/18 13:02:44 42 (spawning-device) Found /usr/pluto/bin/ZWave
05 10/28/18 13:02:44.210 Creating child 43 <0xb6d5a700>
05 10/28/18 13:02:44.210 Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire event
s. <0xb6d5a700>
05 10/28/18 13:02:44.210 Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0
xb6d5a700>
05 10/28/18 13:02:44.210 Creating child 44 <0xb6d5a700>
05 10/28/18 13:02:44.210 Note: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire event
s. <0xb6d5a700>
05 10/28/18 13:02:44.210 Note: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR. <0
xb6d5a700>
2018-10-28 13:02:44.248 Info, Reading /etc/openzwave/options.xml for Options
2018-10-28 13:02:44.248 Info, Reading /etc/openzwave/options.xml for Options
Tried adding a light manually a few days back, no luck either, possible got it incorrect.
-
If it stuck on Info, Reading /etc/openzwave/options.xml for Options, try a killall ZWave. That usually gets things going.
-
Killed it, restarted the machine, no luck, then restarted again, did an update.
Got attached
-
Well it looks like the controller is working and the devices are there but the red don't look good.
Shouldn't need to reboot if you killall ZWave, think I tried something like that before but ZWave died so rebooted to make sure, maybe I sent it the wrong signal. thanks for the tip pointman87.
-
I rebooted, but no devices were added.
Tried it again, no luck. Office work to do, will try later
-
So the AV wizard pop up, so went through it. In tailing the 42_Z.. log, I am seeing the following. The avwizard had not errored out this time though, still no lights added. Rebooting again, as I head out.
I only have two devices added to the controller
10/30/18 19:18:05.445 ZWInterface::OnNotification() : Node 5 presumed dead! <0xb4fffb40>
01 10/30/18 19:18:05.449 ZWave::OnNotification() : Node presumed dead, node id = 5 <0xb4fffb40>
05 10/30/18 19:18:05.973 ZWInterface::OnNotification() : Type_EssentialNodeQueriesComplete nodeId = 4 <0xb4fffb40>
05 10/30/18 19:18:06.505 ZWInterface::OnNotification() : Type_ControllerCommand: State Starting <0xb4fffb40>
05 10/30/18 19:18:06.520 ZWInterface::OnNotification() : Type_ControllerCommand: State Controller is communicating with device <0xb4fffb40>
05 10/30/18 19:18:06.719 ZWInterface::OnNotification() : Type_ControllerCommand: State Command has completed successfully <0xb4fffb40>
05 10/30/18 19:18:06.719 ZWInterface::OnNotification() : Type_ControllerCommand: State Starting <0xb4fffb40>
05 10/30/18 19:18:06.730 ZWInterface::OnNotification() : Type_ControllerCommand: State Controller is communicating with device <0xb4fffb40>
05 10/30/18 19:18:07.329 ZWInterface::OnNotification() : Type_ControllerCommand: State Command has completed successfully <0xb4fffb40>
05 10/30/18 19:18:50.987 Got a reload command from 0 <0xb59ffb40>
01 10/30/18 19:21:00.000 AlarmCallback(): trying to revive node 2 for the 1 time <0xb6d57b40>
01 10/30/18 19:21:00.205 ZWInterface::OnNotification() : Node 2 presumed dead! <0xb4fffb40>
01 10/30/18 19:21:00.209 ZWave::OnNotification() : Node presumed dead, node id = 2 <0xb4fffb40>
01 10/30/18 19:21:05.000 AlarmCallback(): trying to revive node 5 for the 1 time <0xb6d57b40>
01 10/30/18 19:21:09.158 ZWInterface::OnNotification() : Node 5 presumed dead! <0xb4fffb40>
01 10/30/18 19:21:09.161 ZWave::OnNotification() : Node presumed dead, node id = 5 <0xb4fffb40>
-
With one of the devices, I believed I know why it fails. My house has a lot of concrete and steel, downstairs, seem the signal not reaching as the core, is two walls away (loading block, with steel inside, that are filled with concrete, they are load bearing walls) away from the node 5 switch. Previously with the older gen stick, before moving, I used to used a USB extension cable, seems it either dead or not functioning with this one.
Any recommendation on a USB extension cable?
If I move the zwave stick, to a raspberry pi MD(not built yet), that is in the same room with the two switches. Technically should be no issues, but any draw back, would have like to keep it on core?
-
I have run my Aeotec zwave (usb with inclusion) on an MD for some time without issues. I went this route after having issues with the configuration being pulled through from the zwave adapter to my LinuxmceVM as well as signal strength with it in the core sitting downstairs in a rack. The MD was not an RPI one, it is an PXE booted traditional MD so not certain that your RPI option will definately work, but I can't see why it wouldn't. Only draw back was the slight delay for the MD to boot and initialise the zwave adapter during any reboots etc. when the MD was not active. I run all my MDs 24/7 otherwise though.
Of note, I also have a Aeotec mini-mote as inclusion as I didn't always have devices within range of the usb adapter and it made it easier than using webadmin. Remember though the more devices (hard wired I find work best) you have, the better the zwavenetwork performance will be.
Hope thats useful.
Cheers
Garath
-
Working today, to get my Raspberry 2, working as an MD.
Three failures thus far, first just giving me a Rainbow Screen, 2nd and 3rd attempted, failed for dpkg errors. Went and got a new SD card as it's a disked MD, on the 4th attempt.
-
Got the Pi 2, built as an MD.
Deleted the interface on the core, then reload, followed by rebooting the core itself
Then added the zwave stick to the MD,within the space and closer to the two lights. Now I get no node drops, but no luck adding stuff, restarted everything twice already
Zwave log, device 83
1 11/04/18 18:06:39 83 (spawning-device) Found /usr/pluto/bin/ZWave
05 11/04/18 18:06:39.528 Creating child 84 <0x76fa5000>
05 11/04/18 18:06:39.536 Note: Device manager has attached a device of type 1820 that this has no custom event handler for. It will not fire events. <0x76fa5000>
05 11/04/18 18:06:39.536 Note: Device manager has attached a device of type 1820 that this has no custom handler for. This is normal for IR. <0x76fa5000>
05 11/04/18 18:06:39.537 Creating child 85 <0x76fa5000>
05 11/04/18 18:06:39.537 Note: Device manager has attached a device of type 1922 that this has no custom event handler for. It will not fire events. <0x76fa5000>
05 11/04/18 18:06:39.537 Note: Device manager has attached a device of type 1922 that this has no custom handler for. This is normal for IR. <0x76fa5000>
01 11/04/18 18:06:39.755 TranslateSerialUSB platform/soc/3f980000.+1.3 result <0x76fa5000>
2018-11-04 18:06:39.775 Info, Reading /etc/openzwave/options.xml for Options
2018-11-04 18:06:39.776 Info, Reading /etc/openzwave/options.xml for Options
Running Zwave Processes
root@moon71:/var/log/pluto# ps -ef|grep ZWave
root 5095 1 0 18:06 ? 00:00:00 /usr/bin/SCREEN -d -m -S ZWave83 /usr/pluto/bin/Spawn_Device.sh 83 192.168.80.1 ZWave
root 5098 5095 0 18:06 pts/9 00:00:00 /bin/bash /usr/pluto/bin/Spawn_Device.sh 83 192.168.80.1 ZWave
root 5327 5098 0 18:06 pts/9 00:00:00 /usr/pluto/bin/ZWave -d 83 -r 192.168.80.1 -l /var/log/pluto/83_ZWave.log
root 22182 18013 0 18:32 pts/14 00:00:00 grep ZWave
Automated View attached
Is it possible, either command line or through web site, to add the light switches manually?
-
Tried adding the lights manually and setting the port from what I saw.
The port 2, seems to be the controller, as it had the brand name.
Tried 4 and 5, but no luck in controlling the light.
Also, I am running a disked MD, but the light log goes to
/usr/pluto/diskless/71/var/log/pluto/89_Light_Switchonoff.log
I don't have a directory /usr/pluto/diskless
The DCrouter log, has the following
08 11/04/18 20:23:00.975 Received Message from 0 (unknown / ) to 89 (Light Switch (on/off) / Living Room/Family Room), type 1 id 193 Command:Off, retry none, parameters: <0x5cffeb40>
05 11/04/18 20:23:00.975 The target device 89 (routed to 83) has not registered. <0xb60e8b40>
05 11/04/18 20:23:01.024 Socket::ReceiveData 0xb3084a10 failed, bytes left 0 start: 2207059 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 135 Incoming_Conn Socket 135 ::ffff:127.0.0.1 <0x5cffeb40>
05 11/04/18 20:23:01.025 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 135 ::ffff:127.0.0.1 <0x5cffeb40>
05 11/04/18 20:23:01.025 TCPIP: Closing connection to -1003 (Router Dev #0) 0xb3084a10 m_Socket: -1 <0x5cffeb40>
05 11/04/18 20:23:01.025 Router::RemoveAndDeleteSocket 0xb3084a10 -1003 <0x5cffeb40>
-
That log is the path to it on the core. You can check var/log/pluto/89_Light_Switchonoff.log on the MD or the initial location on the core for that log.
-
I got it to work.
After lucking out with the MD (raspberry 2), not even getting a view under Automation -> zwave, I moved my core from inside "hide away location" so I don't get the dropping issue, in light of my minimal switches.
Deleted the existing zwave device, then added back the zwave device to the core, no luck either.
Thus I took the stick out, excluded the switches, reset the stick and deleted the zwave interface from the core. Restarted the core, then plugged in the stick, followed the prompts and was able to see it in Automation -> Zwave as node 1. Then included the lights switches, grand total of two, plugged it back into the core, followed the prompt, nothing. I also was not seeing anything in automation -> zwave.
I then restarted the core, the wizard came up again, followed through the prompts. When I checked automation -> zwave, saw the nodes, node 1 being the stick, node 2, one switch and node 3 another. When i checked the status, for the nodes, both node 2 and 3, showed they are lnuxmce devices and the template number, so that was new and hopeful. Checked under lights and they were listed there, great. Added them to the rooms, reload and regen and it worked
Have attached some pics on ow it looks. Something to note, I have a GE and an Inovelli switch. Both work, but when you click on the node icon, the GE values especially for label switch, says true, the Inovelli that value is false. Listing also attached.
Thanks guys
-
GE Values
-
Inovelli Values
-
I'm glad you have managed to get things working. I did start an upgrade to the zwave system some time ago but didn't complete it. Once that is done the openzwave interface should have better knowledge of a lot more devices.
J.
-
Understanding Zwave is a mesh network.
Is multiple controller sticks supported, let's say one on a ground floor the other on a second floor, and for the controlled by, you tell which switches is on which controller?
Not sure if this is still valid, but say it on argo control.
Would this (RaZberry Pi Z-Wave module) be supported in a Raspberry MD or at all?
-
I don't see why multiple zwave networks wouldn't work. You would only include certain devices into each network and adjust the controlled by, as you say. I've not known anyone to do this but it could work.
I think the raspberry pi zwave module is supported by openzwave, but it would not be auto detected by LMCE at this point as no one has attempted to use one that I know of.
J.
-
Good you got it working.
Would like to add to what Garbui mentioned, the first time I added a zwave plus device a while back, a hardwired plug, I was amazed to see how it fixed the connection issues with other devices because it acts as a repeater. I've added a few more devices since then and the network seems fine so wholeheartedly agree adding more devices are better, even one if it can act as a repeater in the mesh.
USB cable are a lot cheaper though, it's good to see how issues like this can be tackled in multiple ways, didn't know having a second controller was at all possible.
Cheers.
-
Any one has experience with the zwave locks?
Also
Aeotec Multisensor 6, Z-Wave Plus 6-in1 motion, temperature, humidity, light, UV, vibration sensor
-
I have a lock but haven't successfully paired it with the open zwave library we have. I'm going to update that but it's a matter of time available. There 6 in 1 causes me problems where it floods the zwave network after LMCE requests confirmations. Temp is reported alternately in F and C causing it to report different values everything failing the confirmation.
J.
Sent from my Pixel using Tapatalk
-
Any Experience with the following?
GoControl WA00Z-1 Z-Wave Scene-Controller Wall Switch
I bought one, but the openzwave driver is only saying probe when I click the status, not seeing an id like the other devices, maybe that is expected. No device added also, see attached
I am okay adding it manually and trying to create an event do so specific stuff when the buttons pressed.
Am also interested in the following which I have not bought yet
Aeotec WallMote, Z-Wave Plus wireless wall switch, 2 button, 8 scene remote control
-
Try to add it. I've been slowly working to update our openzwave so we have support for lots more devices and better security support. Our version is before they released the protocol spec. I've got it in the build just haven't had a chance to test it before deploying...
Sent from my Pixel using Tapatalk
-
Open to suggestions/guidance
Tried light and security sensor, currently at security sensor but can't seem to capture an event value or maybe reading it wrong, generic sercurity sensor
What I was looking for, is when you press one of the buttons on the device, let's say it sends a value, so I can capture that turn off the TV, any lights and if possible set the house mode to arm
See what I am getting
zwave log
ZWave::OnNotification() : Type_NodeQueriesComplete nodeId = 7 <0xb4fffb40>
05 01/16/19 20:13:27.625 Device mapping: <0xb4fffb40>
05 01/16/19 20:13:27.629 GetDeviceTemplate() manufacturer = 014f, prodType = 5343, prodId = 3132 <0xb4fffb40>
01 01/16/19 20:13:27.633 -> No device template for node with generic 24, specific 1, label <none> <0xb4fffb40>
05 01/16/19 20:13:27.637 * Device id = 7, dt = 0 (<unknown>), main label = <none>, pk_parent = 0 <0xb4fffb40>
05 01/16/19 20:13:27.641 -> Already mapped to device, PK_Device=130 <0xb4fffb40>
DCErouter
07 01/16/19 20:17:45.934 Event #100 has no handlers <0xaf403b40>
07 01/16/19 20:17:45.934 Received Message from 130 (goControlScene / ) to -1001 (unknown / ), type 2 id 100 Event:Battery Level Changed, ret ry none, parameters: <0xaf403b40>
07 01/16/19 20:17:45.934 Parameter 30(Value): 85 <0xaf403b40>
08 01/16/19 20:17:45.974 Received Message from 96 (ZWave / Closet/Storage Space) to 4 (General Info Plug-in / Closet/Storage Space), type 1 id 246 Command:Set Device Data, retry none, parameters: <0xaf403b40>
08 01/16/19 20:17:45.981 Parameter 2(PK_Device): 130 <0xaf403b40>
08 01/16/19 20:17:45.985 Parameter 5(Value To Assign): 85 <0xaf403b40>
08 01/16/19 20:17:45.989 Parameter 52(PK_DeviceData): 293 <0xaf403b40>
07 01/16/19 20:17:46.342 Event #100 has no handlers <0xaf403b40>
07 01/16/19 20:17:46.342 Received Message from 130 (goControlScene / ) to -1001 (unknown / ), type 2 id 100 Event:Battery Level Changed, ret ry none, parameters: <0xaf403b40>
07 01/16/19 20:17:46.342 Parameter 30(Value): 88 <0xaf403b40>
08 01/16/19 20:17:46.352 Received Message from 96 (ZWave / Closet/Storage Space) to 4 (General Info Plug-in / Closet/Storage Space), type 1 id 246 Command:Set Device Data, retry none, parameters: <0xaf403b40>
08 01/16/19 20:17:46.352 Parameter 2(PK_Device): 130 <0xaf403b40>
08 01/16/19 20:17:46.352 Parameter 5(Value To Assign): 88 <0xaf403b40>
08 01/16/19 20:17:46.352 Parameter 52(PK_DeviceData): 293 <0xaf403b40>
-
What version of LMCE are you running? 32 bit or 64 bit, 1404? If you want to test a newer openzwave I can send you the packages...
J
Sent from my Pixel using Tapatalk
-
See results of uname and lsb.. Running 32 bit version
dcerouter_1551:/var/log/pluto# uname -a
Linux dcerouter 4.4.0-141-generic #167~14.04.1-Ubuntu SMP Mon Dec 10 13:22:45 UTC 2018 i686 i686 i686 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Created a light, getting the following. At a specific time it crashed the zwave network :)
DCErouter
07 01/17/19 19:36:52.091 Event #100 has no handlers <0x67bbcb40>
07 01/17/19 19:36:52.091 Received Message from 133 (Light Switch Scene / ) to -1001 (unknown / ), type 2 id 100 Event:Battery Level Changed, retry none, parameters: <0x67bbcb40>
07 01/17/19 19:36:52.091 Parameter 30(Value): 82 <0x67bbcb40>
08 01/17/19 19:36:52.130 Received Message from 96 (ZWave / Closet/Storage Space) to 4 (General Info Plug-in / Closet/Storage Space), type 1 id 246 Command:Set Device Data, retry none, parameters: <0x67bbcb40>
08 01/17/19 19:36:52.130 Parameter 2(PK_Device): 133 <0x67bbcb40>
08 01/17/19 19:36:52.130 Parameter 5(Value To Assign): 82 <0x67bbcb40>
08 01/17/19 19:36:52.130 Parameter 52(PK_DeviceData): 293 <0x67bbcb40>
Zwave log
5 01/17/19 19:41:58.761 ZWave::OnNotification() : Type_NodeQueriesComplete nodeId = 7 <0xb4fffb40>
05 01/17/19 19:41:58.766 Device mapping: <0xb4fffb40>
05 01/17/19 19:41:58.769 GetDeviceTemplate() manufacturer = 014f, prodType = 5343, prodId = 3132 <0xb4fffb40>
01 01/17/19 19:41:58.773 -> No device template for node with generic 24, specific 1, label <none> <0xb4fffb40>
05 01/17/19 19:41:58.778 * Device id = 7, dt = 0 (<unknown>), main label = <none>, pk_parent = 0 <0xb4fffb40>
05 01/17/19 19:41:58.781 -> Already mapped to device, PK_Device=133 <0xb4fffb40>