openzwave / zwave2mqtt Goto Github PK
View Code? Open in Web Editor NEWFully configurable Zwave to MQTT gateway and Control Panel using NodeJS and Vue
License: MIT License
zwave2mqtt's People
Contributors
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
Stargazers
Watchers
Forkers
jlrgraham gaybro8777 dannynicolas iceglow nexiles react9 jshridha papertigers alphatangoalpha silfa718 mattgruter thundergreen arjenhiemstra ilharts dchesterton colinharrington wilmardo wwebers bjornreppen ksuclipse masiorski sfstar iblis82 docbobo riemers jabastien chickenandpork derrohrbach dinth drkduncan daevaorn alex-savin pilot-sys hyperbolic2346 nervetattoo ovenystas chilicheech nicoxygen potterdoug jyvern mshiznitzh adrum jonasped hvxl llunved kuhlivisj edwork matt-pmct idyedov tomasz69 greifi fabio-torchetti jasonsinclair5 kuanyuchen dearthymcstain mrwho j9brown renos31 ptzimotou pdbogen samiahmedshaik niemyjski drjjr2 sirpeanut jacksun101 markferry p4p3r jarobabs dbaker-rh peter-vanpoucke squiddity darkbasic homected ahochsteger sieukrem varet80 bmight swipswaps go4ble frago711 kipe sgc1990 vsqla blaunicorn arvind-india docdocker devsider ddai00bit ivantq numbnet moayyaed jonatanolofsson fabio-radin bayaabidzwave2mqtt's Issues
Rows per page uses node ID instead of counting items causing items to be hidden
I have been fighting to get a simple setup with an Aeotec stick and two sirens to work.
I moved them over from a Home Assistant installation and it used to be a larger installation
I tried to import the config and it was reported successful but I assumed it did not work because I could not see my 2 sirens.
So I removed them and added them and they are in the config. But no sign of them in the user interface - in the table of nodes. Until I by accident touch the header and the table sorted descending. Then I tried to click to see ALL instead of rows per page 10. Then all 3 nodes are visible
So the table of nodes and the feature of showing 10 at a time uses the node number. That is wrong. An Aeotec stick will keep on assigning higher numbers even when you remove older nodes. In my case my first node was in the upper 20s. And after having added and removed they became 30 and 31. I then tried to factory reset the stick and start all over. Then the nodes are 1,2,3 and shows normally. You should change the table showing feature so it shows the 10 first, Then the next 10, and next 10. Not by node ID buy by counting. People will have holdes in their node intervals so the tables will be strange with less than 10 in them otherwise and worst case people like me will not see any nodes
Web page connection - 302 error code
After the success install, I'm connect on the web service : http://myLocalIP:8091
But, my client notify me than the page is not redirected correctly.
In the backend, I have this message :
z2m:Store settings.json not found +0ms
z2m:Store scenes.json not found +109ms
z2m:App Application path:/usr/src/app +0ms
z2m:Gateway Gateway needs both MQTT and Zwave Configuration to work +0ms
z2m:App Listening on port 8091 +0ms
z2m:App Error: Not Found
z2m:App at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
z2m:App at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
z2m:App at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
z2m:App at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
z2m:App at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
z2m:App at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
z2m:App at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +9s
GET / 302 163.416 ms - 46
z2m:App Error: Not Found
z2m:App at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
...
...
...
z2m:App Error: Not Found
z2m:App at /snapshot/Zwave2Mqtt/app.js:0:0
z2m:App at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12)
z2m:App at next (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:275:10)
z2m:App at cors (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:188:7)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:224:17
z2m:App at originCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:214:15)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:219:13
z2m:App at optionsCallback (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:199:9)
z2m:App at corsMiddleware (/snapshot/Zwave2Mqtt/node_modules/cors/lib/index.js:204:7)
z2m:App at Layer.handle [as handle_request] (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/layer.js:95:5)
z2m:App at trim_prefix (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:317:13)
z2m:App at /snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:284:7
z2m:App at Function.process_params (/snapshot/Zwave2Mqtt/node_modules/express/lib/router/index.js:335:12) +64ms
GET / 302 39.646 ms - 46
To inform, I use one Raspberry pi 0w with raspbian-strech. I have try your dockers images, the classic install and build my own docker image (with arm32v6/alpine).
Thanks a lot for your help !
How to remove a failed node completely?
Is there a way to remove a failed node?
I've tried modifying the xml file both while the server is up and down but doesn't make a difference. Can't see an option for it unless I'm missing something.
Thanks
[Feature] Home Assistant integration
I see in your todo list that integration (discovery I assume) with home assistant is planned.
Can you tell me when you think to build this functionality?
I am already using zigbee2mqtt, so a big fan of mqtt and would be very happy if full integration with the device registry of home assistant is implemented for z-wave!
Door locks?
Hi,
Sorry not an issue, but don't see a forum to post questions on - has anyone used zwave2mqtt with doorlocks - specifically the Yale Conexis L1? Thinking about getting one, but don't know if it will work.
Also what USB sticks do you folks use? Will https://www.amazon.co.uk/gp/product/B00YETCNOE/ref=ox_sc_act_title_1?smid=A3P5ROKL5A1OLE&psc=1 work?
Device DB not working
I’d love to move over to this, but if I start afresh, it doesn’t pull any device information (docker). I’ve tried pulling over the folder structure of the device db and pointing at that, but everything is unrecognised.
If I feed it an existing zwcfg from hass, it works.
Am I doing something wrong?
Question: Launching at Boot
Sorry for a possible Linux noob question. How would I automatically launch Zwave2Mqtt at boot? I'm trying to create a systemd service, but issues with references to file dependencies, etc.
Cannot rebuild [email protected]
I have issues installing the npm packages with OpenZwave2Mqtt version 1.1.3.
root@83e2f7f43730:/opt$ npm install [email protected]
> [email protected] preinstall /opt/node_modules/openzwave-shared
> node lib/install-ozw.js
> [email protected] install /opt/node_modules/openzwave-shared
> node-gyp rebuild
Illegal option -p
nm: 'a.out': No such file
gyp: Call to 'ldconfig -p | grep 'libopenzwave.so ' | awk '{print $4}' | xargs nm -g --demangle |grep OpenZWave::Value::GetTypeNameFromEnum | wc -l' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:345:16)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.9.125-linuxkit
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/node_modules/openzwave-shared
gyp ERR! node -v v10.16.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
npm WARN [email protected] No repository field.
npm WARN [email protected] No license field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-07-03T09_31_19_381Z-debug.log
I have uploaded the logfile to my gist: https://gist.github.com/rgruyters/28825da79ee6ad479f134e9b14f71015
I don't have any issues when I install version 1.4.8 of openzwave-shared.
Is this a known issue?
Run on an embedded GL-MT300N-V2
I have some GL-MT300N-V2 laying around, small embedded devices that originally run openWRT - this units are fully flashable and should be fully capable as running as a server for zwave2mqtt with a flash image.
Anyone had any luck flashing a openWRT / GL-MT300N-V2 device with a basic linux imsage and run zwave2mqtt on it?
Would be an easy way to put a small factor zwave bridge in the house that is not a RPI
Reopening of serialport fails on settings save
2019-03-13T21:51:51.136Z z2m:Mqtt Error while publishing a value client disconnecting
2019-03-13T21:51:51.136Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-13T21:51:51.137Z z2m:Mqtt Error while publishing a value client disconnecting
2019-03-13T21:51:51.137Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-13T21:51:51.137Z z2m:Mqtt Error while publishing a value client disconnecting
2019-03-13T21:51:51.137Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-13T21:51:51.137Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
/opt/zwave2mqtt/node_modules/nedb/lib/datastore.js:77
if (err) { throw err; }
^
Error: ENOENT: no such file or directory, open '/opt/zwave2mqtt/store/mqtt/incoming~'
I restarted with the switch value with poll disabled under the gateway settings, I got this error.
Not all configuration is exposed (for mutliple nodes the same type of config is missing)
I have a ZW116 Nano Switch (AEON Labs)
It has a button under node -> values -> configuration with label SET 111-113 TO DEFAULT which are the reporting intervals for group 1, 2 and 3.
But there is no way (that I found) to change the values to something different. e.g. I want 111 to be set too 300 as I want updates every 5 minutes.
3-Speed fan lists "Dim" and "Bright" rather than something more applicable
When controlling a 3-speed fan (I'm using the GE one for instance) the buttons that show up are for "Bright" and "Dim". It probably makes sense to change these to "Faster" and "Slower" for fans.
Does not reattach to controller after softreset
After sending a softreset command the USB device gets briefly detached and reattached.
This results in zwave2mqtt talking to a no longer valid fd? for the serial device. Restart zwave2mqtt fixes this.
Reopening the device after sending a softreset should have the same effect.
UI Toggle buttons (for Switches) does a weird state dance when toggled
I have a outlet device that has an on/off switch exposed in the user settings.
Changing the stay from On -> Off (or Off -> On) will make the toggle switch position, but immediately go back to the previous position. (It also sends the zwave command to the device). The device them responds with the new state making the toggle go to the correct state.
It would be nice that the button stays at the new position and maybe is disabled for a second (or until a new update is received - which ever comes first I guess).
Correctly displays multiple group associations and suggestion for removing association for a dead child node
I've a device with a few associations. I got two problems with it:
- The interface does not display the entity names correctly because of the limited interface space. Now I can only see all the associations to open the zWave Log and look at the 'getAssociations' resultset
- Another problem is that the parent device has some associations with some dead child nodes and I can't remove that. I can only delete an association when that child node is in the node list, otherwise I can't choose it and got no option 'Remove'.
May be it's an option to display an dropdown with all the associations and when selection is made, display the option 'Remove'.
In the screenshot below, the Node 15 and 16 are dead. The other 4 associations are not displayed because of the limited space.
Zwcfg config file problems
Thanks for this great add-on. Very nice to see all the cool add-ons you created.
I tried to migrate from HA with Zwave with an Aeon Labs USB stick to this component. After configuring the basics I got the first nodes available in Zwave2Mqtt, but all the Zwave node information etc is empty because the add-on starts with a empty OpenZwave config.
I found the option to import an Zwave config file, so I uploaded my Zwcfg config file from the HA root directory but it looks that won't work. I don't see any difference.
After a few minutes a few of the 50 nodes I got have some Zwave node information. I give the Add-on a restart and after that all the node information was gone again.
So a few problems / suggestions for the manual:
- Why the Zwcfg file import doesn't work. I don't see any error or something. Maybe because of the 1.4 <---> 1.6 difference?
- Where in the add-on container is the local Zwcfg file located? I tried to find it but I can only find the /opt directory with the web application files but without the Zwcfg file.
- Make the Zwcfg persistent so after a restart not all the node information is gone
- An option to link an config file or something from outside the container inside would be great. So the config file could be on an central place instead of inside an add-on container.
[Question] Properties polling
Telling the truth I do not completele understand how properties polling is implemented in openzwave right now, but it will be very good to have different settings per property for polling.
Two types of devices at my setup are: danfoss thermostat and MCO CO2 sensor.
First devices is almost always in sleep mode, second one is always on. Danfoss thermostat wakes up from time to time and pushes current temp settings. CO2 sensor automatically pushes sensor value change is more then 50ppm....
But it's not good. For CO2 device is would be much better to have possibility to poll it's value periodically (i.e. get value each 10 seconds) and for danfoss thermostat it would be very good to have possibility to adjust it's clock - this is more complicated. You should listen on 'wake up' event, imediatelly poll for clock values and send new time in case there is a big difference - this steps should be done before device will go to sleep again.
Crash after a few seconds on SmartOS/illumos
I found this project while googling for an issue building a node-red-ui-dashboard voor de openzwave stuff (which is a pain). This looked very promising and I got it installed OK.
After going through all the configuration steps and hitting save I had a hard crash. This happens again when restarting after a few seconds.
[root@amethyst /opt/Zwave2Mqtt]# npm start
> [email protected] start /opt/Zwave2Mqtt
> node bin/www
z2m:Store scenes.json not found +0ms
z2m:App Application path:/opt/Zwave2Mqtt +0ms
Initialising OpenZWave 1.4.3365 binary addon for Node.JS.
OpenZWave Security API is ENABLED
ZWave device db : /opt/local/etc/openzwave
User settings path : /opt/Zwave2Mqtt
Option Overrides : --Logging true --ConsoleOutput true --QueueLogLevel 8 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 60000 --NetworkKey 0x58,0x50,0x3A,0x1C,0x0A,0xD7,0x66,0x6D,0x27,0x78,0x67,0x4C,0x1E,0xCB,0xC4,0x61
z2m:Zwave Connecting to /dev/cua/0 +0ms
2019-03-03 13:22:11.659 Always, OpenZwave Version 1.4.3365 Starting Up
2019-03-03 13:22:11.660 Info, Setting Up Provided Network Key for Secure Communications
2019-03-03 13:22:11.660 Info, mgr, Added driver for controller /dev/cua/0
2019-03-03 13:22:11.660 Info, Opening controller /dev/cua/0
2019-03-03 13:22:11.660 Info, Trying to open serial port /dev/cua/0 (attempt 1)
2019-03-03 13:22:11.662 Info, Serial port /dev/cua/0 opened (attempt 1)
2019-03-03 13:22:11.662 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-03-03 13:22:11.662 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-03-03 13:22:11.662 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-03-03 13:22:11.662 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-03-03 13:22:11.662 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-03-03 13:22:11.662 Detail,
2019-03-03 13:22:11.662 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x15) - FUNC_ID_ZW_GET_VERSION: 0x01, 0x03, 0x00, 0x15, 0xe9
2019-03-03 13:22:11.665 Detail, contrlr, Received: 0x01, 0x10, 0x01, 0x15, 0x5a, 0x2d, 0x57, 0x61, 0x76, 0x65, 0x20, 0x36, 0x2e, 0x30, 0x32, 0x00, 0x01, 0x92
2019-03-03 13:22:11.665 Detail,
2019-03-03 13:22:11.665 Info, contrlr, Received reply to FUNC_ID_ZW_GET_VERSION:
2019-03-03 13:22:11.665 Info, contrlr, Static Controller library, version Z-Wave 6.02
2019-03-03 13:22:11.665 Detail, Node045, Expected reply was received
2019-03-03 13:22:11.665 Detail, Node045, Message transaction complete
2019-03-03 13:22:11.665 Detail,
2019-03-03 13:22:11.665 Detail, contrlr, Removing current message
2019-03-03 13:22:11.665 Detail,
2019-03-03 13:22:11.665 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x20) - FUNC_ID_ZW_MEMORY_GET_ID: 0x01, 0x03, 0x00, 0x20, 0xdc
2019-03-03 13:22:11.668 Detail, contrlr, Received: 0x01, 0x08, 0x01, 0x20, 0xfc, 0x20, 0xd0, 0x90, 0x01, 0x4b
2019-03-03 13:22:11.668 Detail,
2019-03-03 13:22:11.668 Info, contrlr, Received reply to FUNC_ID_ZW_MEMORY_GET_ID. Home ID = 0xfc20d090. Our node ID = 1
2019-03-03 13:22:11.668 Detail, Node032, Expected reply was received
2019-03-03 13:22:11.668 Detail, Node032, Message transaction complete
2019-03-03 13:22:11.668 Detail,
2019-03-03 13:22:11.668 Detail, contrlr, Removing current message
2019-03-03 13:22:11.668 Detail,
2019-03-03 13:22:11.668 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x05) - FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES: 0x01, 0x03, 0x00, 0x05, 0xf9
2019-03-03 13:22:11.670 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x05, 0x1c, 0xe3
2019-03-03 13:22:11.670 Detail,
2019-03-03 13:22:11.670 Info, contrlr, Received reply to FUNC_ID_ZW_GET_CONTROLLER_CAPABILITIES:
2019-03-03 13:22:11.670 Info, contrlr, There is a SUC ID Server (SIS) in this network.
2019-03-03 13:22:11.670 Info, contrlr, The PC controller is an inclusion static update controller (SUC) and was the original primary before the SIS was added.
2019-03-03 13:22:11.670 Detail, Node227, Expected reply was received
2019-03-03 13:22:11.670 Detail, Node227, Message transaction complete
2019-03-03 13:22:11.670 Detail,
2019-03-03 13:22:11.670 Detail, contrlr, Removing current message
2019-03-03 13:22:11.670 Detail,
2019-03-03 13:22:11.670 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x07) - FUNC_ID_SERIAL_API_GET_CAPABILITIES: 0x01, 0x03, 0x00, 0x07, 0xfb
2019-03-03 13:22:11.674 Detail, contrlr, Received: 0x01, 0x2b, 0x01, 0x07, 0x05, 0x24, 0x01, 0x15, 0x04, 0x00, 0x00, 0x01, 0xfe, 0x87, 0x7f, 0x88, 0xcf, 0x3f, 0xc0, 0x47, 0xfb, 0xdf, 0xfd, 0xe0, 0x67, 0x00, 0x80, 0x80, 0x00, 0x80, 0x86, 0x00, 0x00, 0x00, 0xe8, 0x73, 0x00, 0x80, 0x0f, 0x00, 0x00, 0x60, 0x5a, 0x00, 0x6d
2019-03-03 13:22:11.674 Detail,
2019-03-03 13:22:11.674 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES
2019-03-03 13:22:11.674 Info, contrlr, Serial API Version: 5.36
2019-03-03 13:22:11.674 Info, contrlr, Manufacturer ID: 0x0115
2019-03-03 13:22:11.674 Info, contrlr, Product Type: 0x0400
2019-03-03 13:22:11.674 Info, contrlr, Product ID: 0x0001
2019-03-03 13:22:11.674 Detail, contrlr, Queuing (Command) FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2019-03-03 13:22:11.674 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
2019-03-03 13:22:11.674 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
2019-03-03 13:22:11.674 Detail, contrlr, Queuing (Command) FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2019-03-03 13:22:11.674 Detail, Node036, Expected reply was received
2019-03-03 13:22:11.674 Detail, Node036, Message transaction complete
2019-03-03 13:22:11.674 Detail,
2019-03-03 13:22:11.674 Detail, contrlr, Removing current message
2019-03-03 13:22:11.674 Detail,
2019-03-03 13:22:11.674 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x56) - FUNC_ID_ZW_GET_SUC_NODE_ID: 0x01, 0x03, 0x00, 0x56, 0xaa
2019-03-03 13:22:11.676 Detail, contrlr, Received: 0x01, 0x04, 0x01, 0x56, 0x01, 0xad
2019-03-03 13:22:11.676 Detail,
2019-03-03 13:22:11.676 Info, contrlr, Received reply to GET_SUC_NODE_ID. Node ID = 1
2019-03-03 13:22:11.676 Detail, Node173, Expected reply was received
2019-03-03 13:22:11.676 Detail, Node173, Message transaction complete
2019-03-03 13:22:11.676 Detail,
2019-03-03 13:22:11.676 Detail, contrlr, Removing current message
2019-03-03 13:22:11.676 Detail,
2019-03-03 13:22:11.677 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x1c) - FUNC_ID_ZW_GET_RANDOM: 0x01, 0x04, 0x00, 0x1c, 0x20, 0xc7
2019-03-03 13:22:11.734 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x1c, 0x01, 0x20, 0x3d, 0x8c, 0x40, 0x51, 0x7b, 0x16, 0xaf, 0xf7, 0xe1, 0x16, 0xa5, 0x6b, 0x92, 0xc2, 0x32, 0x48, 0xdb, 0x7d, 0x27, 0x92, 0xc2, 0xc0, 0x14, 0x4e, 0xd6, 0x83, 0xab, 0x26, 0xb1, 0xcf, 0xc1, 0x26, 0x6a
2019-03-03 13:22:11.734 Detail,
2019-03-03 13:22:11.734 Info, contrlr, Received reply to FUNC_ID_ZW_GET_RANDOM: true
2019-03-03 13:22:11.734 Detail, Node032, Expected reply was received
2019-03-03 13:22:11.734 Detail, Node032, Message transaction complete
2019-03-03 13:22:11.734 Detail,
2019-03-03 13:22:11.734 Detail, contrlr, Removing current message
2019-03-03 13:22:11.734 Detail,
2019-03-03 13:22:11.734 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x02) - FUNC_ID_SERIAL_API_GET_INIT_DATA: 0x01, 0x03, 0x00, 0x02, 0xfe
z2m:App Listening on port 8091 +0ms
z2m:Mqtt MQTT client offline +0ms
z2m:Mqtt MQTT client closed +1ms
2019-03-03 13:22:11.832 Detail, contrlr, Received: 0x01, 0x25, 0x01, 0x02, 0x06, 0x08, 0x1d, 0x0b, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x05, 0x00, 0xc4
2019-03-03 13:22:11.832 Detail,
2019-03-03 13:22:11.832 Info, mgr, Driver with Home ID of 0xfc20d090 is now ready.
2019-03-03 13:22:11.832 Info,
2019-03-03 13:22:11.832 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_GET_INIT_DATA:
2019-03-03 13:22:11.832 Info, contrlr, Node 001 - New
2019-03-03 13:22:11.832 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2019-03-03 13:22:11.832 Detail, Node001, QueryStage_ProtocolInfo
2019-03-03 13:22:11.832 Detail, Node001, Queuing (Query) Get Node Protocol Info (Node=1): 0x01, 0x04, 0x00, 0x41, 0x01, 0xbb
2019-03-03 13:22:11.832 Detail, Node001, Queuing (Query) Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:11.832 Info, Node001, Initializing Node. New Node: false (false)
2019-03-03 13:22:11.832 Info, contrlr, Node 002 - New
2019-03-03 13:22:11.833 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2019-03-03 13:22:11.833 Detail, Node002, QueryStage_ProtocolInfo
2019-03-03 13:22:11.833 Detail, Node002, Queuing (Query) Get Node Protocol Info (Node=2): 0x01, 0x04, 0x00, 0x41, 0x02, 0xb8
2019-03-03 13:22:11.833 Detail, Node002, Queuing (Query) Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:11.833 Info, Node002, Initializing Node. New Node: false (false)
2019-03-03 13:22:11.833 Info, contrlr, Node 004 - New
2019-03-03 13:22:11.833 Detail, Node004, AdvanceQueries queryPending=0 queryRetries=0 queryStage=None live=1
2019-03-03 13:22:11.833 Detail, Node004, QueryStage_ProtocolInfo
2019-03-03 13:22:11.833 Detail, Node004, Queuing (Query) Get Node Protocol Info (Node=4): 0x01, 0x04, 0x00, 0x41, 0x04, 0xbe
2019-03-03 13:22:11.833 Detail, Node004, Queuing (Query) Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:11.833 Info, Node004, Initializing Node. New Node: false (false)
2019-03-03 13:22:11.833 Detail, Node008, Expected reply was received
2019-03-03 13:22:11.833 Detail, Node008, Message transaction complete
2019-03-03 13:22:11.833 Detail,
2019-03-03 13:22:11.833 Detail, contrlr, Removing current message
2019-03-03 13:22:11.833 Detail, Node001, Notification: DriverReady
2019-03-03 13:22:11.833 Detail, Node001, Notification: NodeNew
2019-03-03 13:22:11.833 Detail, Node001, Notification: NodeAdded
z2m:Zwave Scanning network with homeid: 0xfc20d090 +176ms
2019-03-03 13:22:11.834 Detail, Node002, Notification: NodeNew
2019-03-03 13:22:11.834 Detail, Node002, Notification: NodeAdded
2019-03-03 13:22:11.834 Detail, Node004, Notification: NodeNew
2019-03-03 13:22:11.834 Detail, Node004, Notification: NodeAdded
2019-03-03 13:22:11.834 Detail,
2019-03-03 13:22:11.834 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x06) - FUNC_ID_SERIAL_API_SET_TIMEOUTS: 0x01, 0x05, 0x00, 0x06, 0x64, 0x0f, 0x97
z2m:Zwave Node added 1 +1ms
z2m:Zwave Node added 2 +0ms
z2m:Zwave Node added 4 +0ms
2019-03-03 13:22:11.836 Detail, contrlr, Received: 0x01, 0x05, 0x01, 0x06, 0x64, 0x0f, 0x96
2019-03-03 13:22:11.836 Detail,
2019-03-03 13:22:11.836 Info, contrlr, Received reply to FUNC_ID_SERIAL_API_SET_TIMEOUTS
2019-03-03 13:22:11.836 Detail, Node015, Expected reply was received
2019-03-03 13:22:11.836 Detail, Node015, Message transaction complete
2019-03-03 13:22:11.836 Detail,
2019-03-03 13:22:11.836 Detail, contrlr, Removing current message
2019-03-03 13:22:11.836 Detail,
2019-03-03 13:22:11.836 Info, contrlr, Sending (Command) message (Callback ID=0x00, Expected Reply=0x00) - FUNC_ID_SERIAL_API_APPL_NODE_INFORMATION: 0x01, 0x07, 0x00, 0x03, 0x01, 0x02, 0x01, 0x00, 0xf9
2019-03-03 13:22:11.837 Detail, contrlr, Removing current message
2019-03-03 13:22:11.837 Detail,
2019-03-03 13:22:11.837 Info, Node001, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=1): 0x01, 0x04, 0x00, 0x41, 0x01, 0xbb
2019-03-03 13:22:11.845 Detail, Node001, Received: 0x01, 0x09, 0x01, 0x41, 0xd3, 0x16, 0x01, 0x02, 0x02, 0x01, 0x73
2019-03-03 13:22:11.845 Detail,
2019-03-03 13:22:11.845 Info, Node001, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2019-03-03 13:22:11.845 Info, Node001, Protocol Info for Node 1:
2019-03-03 13:22:11.845 Info, Node001, Listening = true
2019-03-03 13:22:11.845 Info, Node001, Beaming = true
2019-03-03 13:22:11.845 Info, Node001, Routing = true
2019-03-03 13:22:11.845 Info, Node001, Max Baud Rate = 40000
2019-03-03 13:22:11.845 Info, Node001, Version = 4
2019-03-03 13:22:11.845 Info, Node001, Security = false
2019-03-03 13:22:11.849 Info, Node001, Basic device class (0x02) - Static Controller
2019-03-03 13:22:11.849 Info, Node001, Generic device Class (0x02) - Static Controller
2019-03-03 13:22:11.849 Info, Node001, Specific device class (0x01) - Static PC Controller
2019-03-03 13:22:11.849 Info, Node001, COMMAND_CLASS_BASIC is not mapped
2019-03-03 13:22:11.849 Info, Node001, Mandatory Command Classes for Node 1:
2019-03-03 13:22:11.849 Info, Node001, None
2019-03-03 13:22:11.850 Info, Node001, Mandatory Command Classes controlled by Node 1:
2019-03-03 13:22:11.850 Info, Node001, COMMAND_CLASS_BASIC
2019-03-03 13:22:11.850 Detail, Node022, Expected reply was received
2019-03-03 13:22:11.850 Detail, Node022, Message transaction complete
2019-03-03 13:22:11.850 Detail,
2019-03-03 13:22:11.850 Detail, Node001, Removing current message
2019-03-03 13:22:11.850 Detail, Node001, Notification: NodeProtocolInfo
2019-03-03 13:22:11.850 Detail, Node001, Notification: ValueAdded
2019-03-03 13:22:11.850 Detail, Node001, Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:11.850 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2019-03-03 13:22:11.850 Detail, Node001, QueryStage_Probe
2019-03-03 13:22:11.851 Detail, Node001, QueryStage_WakeUp
2019-03-03 13:22:11.851 Detail, Node001, QueryStage_ManufacturerSpecific1
2019-03-03 13:22:11.851 Detail, Node001, Load Controller Manufacturer Specific Config
z2m:Zwave ValueAdded: 1-32-1-0 Basic +17ms
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_NodePlusInfo
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_SecurityReport
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_ManufacturerSpecific2
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_Versions
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_Instances
2019-03-03 13:22:11.867 Info, Node001, Essential node queries are complete
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_Static
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_Associations
2019-03-03 13:22:11.867 Detail, Node001, QueryStage_Neighbors
2019-03-03 13:22:11.867 Detail, Requesting routing info (neighbor list) for Node 1
2019-03-03 13:22:11.867 Detail, Node001, Queuing (Command) Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2019-03-03 13:22:11.867 Detail, Node001, Queuing (Query) Query Stage Complete (Neighbors)
2019-03-03 13:22:11.867 Detail, Node001, Notification: EssentialNodeQueriesComplete
2019-03-03 13:22:11.867 Detail,
2019-03-03 13:22:11.867 Info, Node001, Sending (Command) message (Callback ID=0x00, Expected Reply=0x80) - Get Routing Info (Node=1): 0x01, 0x07, 0x00, 0x80, 0x01, 0x00, 0x00, 0x03, 0x7a
2019-03-03 13:22:11.871 Detail, Node001, Received: 0x01, 0x20, 0x01, 0x80, 0x08, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x56
2019-03-03 13:22:11.871 Detail,
2019-03-03 13:22:11.871 Info, Node001, Received reply to FUNC_ID_ZW_GET_ROUTING_INFO
2019-03-03 13:22:11.872 Info, Node001, Neighbors of this node are:
2019-03-03 13:22:11.872 Info, Node001, Node 4
2019-03-03 13:22:11.872 Detail, Expected reply was received
2019-03-03 13:22:11.872 Detail, Message transaction complete
2019-03-03 13:22:11.872 Detail,
2019-03-03 13:22:11.872 Detail, Node001, Removing current message
2019-03-03 13:22:11.872 Detail,
2019-03-03 13:22:11.872 Info, Node002, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=2): 0x01, 0x04, 0x00, 0x41, 0x02, 0xb8
2019-03-03 13:22:11.875 Detail, Node002, Received: 0x01, 0x09, 0x01, 0x41, 0xd3, 0x9c, 0x01, 0x04, 0x21, 0x01, 0xdc
2019-03-03 13:22:11.875 Detail,
2019-03-03 13:22:11.875 Info, Node002, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2019-03-03 13:22:11.875 Info, Node002, Protocol Info for Node 2:
2019-03-03 13:22:11.875 Info, Node002, Listening = true
2019-03-03 13:22:11.875 Info, Node002, Beaming = true
2019-03-03 13:22:11.875 Info, Node002, Routing = true
2019-03-03 13:22:11.875 Info, Node002, Max Baud Rate = 40000
2019-03-03 13:22:11.875 Info, Node002, Version = 4
2019-03-03 13:22:11.875 Info, Node002, Security = false
2019-03-03 13:22:11.875 Info, Node002, Basic device class (0x04) - Routing Slave
2019-03-03 13:22:11.875 Info, Node002, Generic device Class (0x21) - Multilevel Sensor
2019-03-03 13:22:11.875 Info, Node002, Specific device class (0x01) - Routing Multilevel Sensor
2019-03-03 13:22:11.875 Info, Node002, COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_SENSOR_MULTILEVEL
2019-03-03 13:22:11.875 Info, Node002, Mandatory Command Classes for Node 2:
2019-03-03 13:22:11.875 Info, Node002, COMMAND_CLASS_SENSOR_MULTILEVEL
2019-03-03 13:22:11.875 Info, Node002, Mandatory Command Classes controlled by Node 2:
2019-03-03 13:22:11.875 Info, Node002, COMMAND_CLASS_BASIC
2019-03-03 13:22:11.875 Detail, Node156, Expected reply was received
2019-03-03 13:22:11.875 Detail, Node156, Message transaction complete
2019-03-03 13:22:11.875 Detail,
2019-03-03 13:22:11.875 Detail, Node002, Removing current message
2019-03-03 13:22:11.875 Detail, Node002, Notification: NodeProtocolInfo
2019-03-03 13:22:11.875 Detail, Node002, Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:11.875 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2019-03-03 13:22:11.875 Detail, Node002, QueryStage_Probe
2019-03-03 13:22:11.875 Info, Node002, NoOperation::Set - Routing=true
2019-03-03 13:22:11.875 Detail, Node002, Queuing (NoOp) NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xca
2019-03-03 13:22:11.875 Detail, Node002, Queuing (Query) Query Stage Complete (Probe)
2019-03-03 13:22:11.875 Detail,
2019-03-03 13:22:11.875 Info, Node002, Sending (NoOp) message (Callback ID=0x0a, Expected Reply=0x13) - NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x0a, 0xca
2019-03-03 13:22:11.883 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-03-03 13:22:11.883 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
z2m:App New connection LvkjHajX3keecGb7AAAA +2s
z2m:Mqtt MQTT client reconnecting +1s
z2m:Mqtt MQTT client closed +3ms
z2m:Mqtt MQTT client reconnecting +2s
z2m:Mqtt MQTT client closed +1ms
z2m:Mqtt MQTT client reconnecting +2s
z2m:Mqtt MQTT client closed +1ms
2019-03-03 13:22:17.580 Detail, Node002, Received: 0x01, 0x18, 0x00, 0x13, 0x0a, 0x01, 0x02, 0x3a, 0x00, 0x7f, 0x7f, 0x7f, 0x7f, 0x7f, 0x01, 0x01, 0x07, 0x00, 0x00, 0x00, 0x00, 0x02, 0x0b, 0x04, 0x02, 0xb0
2019-03-03 13:22:17.580 Detail, Node002, ZW_SEND_DATA Request with callback ID 0x0a received (expected 0x0a)
2019-03-03 13:22:17.580 Info, Node002, WARNING: ZW_SEND_DATA failed. No ACK received - device may be asleep.
2019-03-03 13:22:17.580 Warning, Node002, WARNING: Device is not a sleeping node.
2019-03-03 13:22:17.580 Info, Node002, QueryStageRetry stage Probe requested stage Probe max 3 retries 0 pending 1
2019-03-03 13:22:17.580 Detail, Node001, Expected callbackId was received
2019-03-03 13:22:17.580 Detail, Node001, Expected reply was received
2019-03-03 13:22:17.580 Detail, Node001, Message transaction complete
2019-03-03 13:22:17.580 Detail,
2019-03-03 13:22:17.580 Detail, Node002, Removing current message
2019-03-03 13:22:17.580 Detail, Node002, Notification: Notification - NoOperation
2019-03-03 13:22:17.581 Detail,
2019-03-03 13:22:17.581 Info, Node004, Sending (Query) message (Callback ID=0x00, Expected Reply=0x41) - Get Node Protocol Info (Node=4): 0x01, 0x04, 0x00, 0x41, 0x04, 0xbe
z2m:Zwave Notification from node 2: Notification - NoOperation (2) +6s
2019-03-03 13:22:17.583 Detail, Node004, Received: 0x01, 0x09, 0x01, 0x41, 0xd3, 0x9c, 0x01, 0x04, 0x10, 0x01, 0xed
2019-03-03 13:22:17.583 Detail,
2019-03-03 13:22:17.583 Info, Node004, Received reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO
2019-03-03 13:22:17.583 Info, Node004, Protocol Info for Node 4:
2019-03-03 13:22:17.583 Info, Node004, Listening = true
2019-03-03 13:22:17.583 Info, Node004, Beaming = true
2019-03-03 13:22:17.583 Info, Node004, Routing = true
2019-03-03 13:22:17.583 Info, Node004, Max Baud Rate = 40000
2019-03-03 13:22:17.583 Info, Node004, Version = 4
2019-03-03 13:22:17.583 Info, Node004, Security = false
2019-03-03 13:22:17.583 Info, Node004, Basic device class (0x04) - Routing Slave
2019-03-03 13:22:17.583 Info, Node004, Generic device Class (0x10) - Binary Switch
2019-03-03 13:22:17.583 Info, Node004, Specific device class (0x01) - Binary Power Switch
2019-03-03 13:22:17.584 Info, Node004, COMMAND_CLASS_BASIC will be mapped to COMMAND_CLASS_SWITCH_BINARY
2019-03-03 13:22:17.584 Info, Node004, Mandatory Command Classes for Node 4:
2019-03-03 13:22:17.584 Info, Node004, COMMAND_CLASS_BASIC
2019-03-03 13:22:17.584 Info, Node004, COMMAND_CLASS_SWITCH_BINARY
2019-03-03 13:22:17.584 Info, Node004, COMMAND_CLASS_SWITCH_ALL
2019-03-03 13:22:17.584 Info, Node004, Mandatory Command Classes controlled by Node 4:
2019-03-03 13:22:17.584 Info, Node004, None
2019-03-03 13:22:17.584 Detail, Node156, Expected reply was received
2019-03-03 13:22:17.584 Detail, Node156, Message transaction complete
2019-03-03 13:22:17.584 Detail,
2019-03-03 13:22:17.584 Detail, Node004, Removing current message
2019-03-03 13:22:17.584 Detail, Node004, Notification: NodeProtocolInfo
2019-03-03 13:22:17.584 Detail, Node004, Notification: ValueAdded
2019-03-03 13:22:17.584 Detail, Node004, Notification: ValueAdded
2019-03-03 13:22:17.584 Detail, Node004, Query Stage Complete (ProtocolInfo)
2019-03-03 13:22:17.584 Detail, Node004, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Probe live=1
2019-03-03 13:22:17.584 Detail, Node004, QueryStage_Probe
2019-03-03 13:22:17.584 Info, Node004, NoOperation::Set - Routing=true
2019-03-03 13:22:17.584 Detail, Node004, Queuing (NoOp) NoOperation_Set (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xcd
2019-03-03 13:22:17.584 Detail, Node004, Queuing (Query) Query Stage Complete (Probe)
2019-03-03 13:22:17.584 Detail,
2019-03-03 13:22:17.584 Info, Node004, Sending (NoOp) message (Callback ID=0x0b, Expected Reply=0x13) - NoOperation_Set (Node=4): 0x01, 0x09, 0x00, 0x13, 0x04, 0x02, 0x00, 0x00, 0x25, 0x0b, 0xcd
z2m:Zwave ValueAdded: 4-37-1-0 Switch +3ms
z2m:Zwave ValueAdded: 4-39-1-0 Switch All +0ms
2019-03-03 13:22:17.592 Detail, Node004, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-03-03 13:22:17.592 Detail, Node004, ZW_SEND_DATA delivered to Z-Wave stack
2019-03-03 13:22:17.616 Detail, Node004, Received: 0x01, 0x18, 0x00, 0x13, 0x0b, 0x00, 0x00, 0x02, 0x00, 0xb0, 0x7f, 0x7f, 0x7f, 0x7f, 0x01, 0x01, 0x03, 0x00, 0x00, 0x00, 0x00, 0x02, 0x01, 0x00, 0x00, 0x4d
2019-03-03 13:22:17.616 Detail, Node004, ZW_SEND_DATA Request with callback ID 0x0b received (expected 0x0b)
2019-03-03 13:22:17.616 Info, Node004, Request RTT 32 Average Request RTT 32
2019-03-03 13:22:17.616 Detail, Expected callbackId was received
2019-03-03 13:22:17.616 Detail, Expected reply was received
2019-03-03 13:22:17.617 Detail, Message transaction complete
2019-03-03 13:22:17.617 Detail,
2019-03-03 13:22:17.617 Detail, Node004, Removing current message
2019-03-03 13:22:17.617 Detail, Node004, Notification: Notification - NoOperation
2019-03-03 13:22:17.617 Detail, Node001, Query Stage Complete (Neighbors)
2019-03-03 13:22:17.617 Detail, Node001, AdvanceQueries queryPending=0 queryRetries=0 queryStage=Session live=1
2019-03-03 13:22:17.617 Detail, Node001, QueryStage_Session
2019-03-03 13:22:17.617 Detail, Node001, QueryStage_Dynamic
2019-03-03 13:22:17.617 Detail, Node001, QueryStage_Configuration
2019-03-03 13:22:17.617 Detail, Node001, QueryStage_Complete
2019-03-03 13:22:17.617 Warning, CheckCompletedNodeQueries m_allNodesQueried=0 m_awakeNodesQueried=0
2019-03-03 13:22:17.617 Warning, CheckCompletedNodeQueries all=0, deadFound=0 sleepingOnly=0
2019-03-03 13:22:17.617 Detail, Node001, Notification: NodeQueriesComplete
2019-03-03 13:22:17.617 Detail, Node002, Query Stage Complete (Probe)
2019-03-03 13:22:17.617 Detail, Node002, AdvanceQueries queryPending=0 queryRetries=1 queryStage=Probe live=1
2019-03-03 13:22:17.617 Detail, Node002, QueryStage_Probe
2019-03-03 13:22:17.617 Info, Node002, NoOperation::Set - Routing=true
2019-03-03 13:22:17.617 Detail, Node002, Queuing (NoOp) NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x0c, 0xcc
2019-03-03 13:22:17.617 Detail, Node002, Queuing (Query) Query Stage Complete (Probe)
2019-03-03 13:22:17.617 Detail,
2019-03-03 13:22:17.617 Info, Node002, Sending (NoOp) message (Callback ID=0x0c, Expected Reply=0x13) - NoOperation_Set (Node=2): 0x01, 0x09, 0x00, 0x13, 0x02, 0x02, 0x00, 0x00, 0x25, 0x0c, 0xcc
z2m:Zwave Notification from node 4: Notification - NoOperation (2) +32ms
/opt/Zwave2Mqtt/lib/Gateway.js:76
var values = this.config.values.filter(v => v.device == node.device_id);
^
TypeError: Cannot read property 'filter' of undefined
at Gateway.onValueChanged (/opt/Zwave2Mqtt/lib/Gateway.js:76:35)
at emitThree (events.js:136:13)
at ZwaveClient.emit (events.js:217:7)
at ZwaveClient.nodeReady (/opt/Zwave2Mqtt/lib/ZwaveClient.js:305:14)
at emitTwo (events.js:126:13)
at OZW.emit (events.js:214:7)
2019-03-03 13:22:17.624 Detail, Node002, Received: 0x01, 0x04, 0x01, 0x13, 0x01, 0xe8
2019-03-03 13:22:17.624 Detail, Node002, ZW_SEND_DATA delivered to Z-Wave stack
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `node bin/www`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-03-03T13_22_17_805Z-debug.log
[root@amethyst /opt/Zwave2Mqtt]# cat /root/.npm/_logs/2019-03-03T13_22_17_805Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/opt/local/bin/node', '/opt/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle [email protected]~prestart: [email protected]
6 info lifecycle [email protected]~start: [email protected]
7 verbose lifecycle [email protected]~start: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~start: PATH: /opt/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/opt/Zwave2Mqtt/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/opt/local/sbin:/opt/local/bin:/usr/sbin:/usr/bin:/sbin
9 verbose lifecycle [email protected]~start: CWD: /opt/Zwave2Mqtt
10 silly lifecycle [email protected]~start: Args: [ '-c', 'node bin/www' ]
11 silly lifecycle [email protected]~start: Returned: code: 1 signal: null
12 info lifecycle [email protected]~start: Failed to exec start script
13 verbose stack Error: [email protected] start: `node bin/www`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/opt/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (/opt/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid [email protected]
15 verbose cwd /opt/Zwave2Mqtt
16 verbose SunOS 5.11
17 verbose argv "/opt/local/bin/node" "/opt/local/bin/npm" "start"
18 verbose node v8.12.0
19 verbose npm v6.8.0
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] start: `node bin/www`
22 error Exit status 1
23 error Failed at the [email protected] start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Menu always expands on click
You can collapse the menu by clicking on the little 3 strip icon in the header.
This is great if the screen space available is small (say a small tablet), tapping a menu icon will expand the menu again.
Ideally it should remain collapsed until the header is clicked again.
Settings does not load settings after a restart (on SmartOS/FreeBSD)
Error while retriving configuration, check console
Is displayed for a few seconds on the popup at the bottom.
z2m:App Error: spawn udevadm ENOENT
z2m:App at Process.ChildProcess._handle.onexit (internal/child_process.js:190:19)
z2m:App at onErrorNT (internal/child_process.js:362:16)
z2m:App at _combinedTickCallback (internal/process/next_tick.js:139:11)
z2m:App at process._tickCallback (internal/process/next_tick.js:181:9) +215ms
That might be to blame.
No device options visibleon USB Dongle (ZWave Plus USB Dongle)
Hi there, great work! I've checked the git version yesterday with a ZWave Plus USB Dongle.
The device is recognized & after about 15 minutes all known ZWave devices appear in the webinterface.
When I select the USB Dongle there a no options under user, config, etc. So I'm not able to add devices, remove devices, etc
Label also has value for node name and location
Seems a bit silly to repeat the value twice
State change not being published
Hey,
I've got a door lock that reports it's battery state. I'm finding that while the zwave2mqtt Web interface is showing an updated battery state (93%), the mqtt topic it reports on is still showing the retained message of 100%, so it appears this change isn't being pushed to mqtt.
Any recommendations on what I could try to fix this?
Thanks, love this programme!
docker
Hi
when I run docker run --rm -it -p 8091:8091 --device=/dev/ttyACM1 --mount source=zwave2mqtt,target=/usr/src/app/store robertslando/zwave2mqtt:latest
the I can't reach the mqtt server running on same server at docker.. just get timeout connectig
Remove failed node
I have read #4 but I don't think it's enough to just have a replace function.
I think there really needs to be something to remove a failed node... Like this feature in Home Assistant which does it too: https://community.home-assistant.io/t/z-wave-help-dead-nodes/41673/21
What do you think?
Gateway configured manually does not show all devices - at least not if same type
I am trying to setup Gateway configured manually
I have one Aeotec stick and two identical sirens.
When I want to setup the topics manually for the sirens I can only see one.
I see the stick and one siren. So I cannot use the feature at all
[Statement] MQTT auto discovery in HA
Hey,
So I have set up my lights how I like them now, I luckily don't have many so easy to manually setup the HA discovery in MQTT.
I wanted to share my findings so far, incase this sparks something, or (with a bit more time & learning) I might complete a pull request to get this automated.
So I have only looked at lights & switches, and for lights only the brightness of them.
For switches its pretty easy to setup with a template such as :
Saved to : homeassistant/switch/dining_room/config
{ "name": "In_wall_dining_room_switch", "state_topic": "zwave/Dining_Room/19/37/1/0", "command_topic": "zwave/_CLIENTS/ZWAVE_GATEWAY-Mos_mqtt/api/setValue/set", "availability_topic": "zwave/Dining_Room/19/status", "payload_on": "{ \"args\":[19,37,1,0,true]}", "payload_off": "{ \"args\":[19,37,1,0,false]}", "state_on": "true", "state_off": "false", "qos": 2, "retain": false, "payload_available": "true", "payload_not_available": "false", "unique_id": "dining_room_switch_111", "device": { "identifiers": "diningroomswitch111", "name": "in_wall_dining_room_switch", "sw_version": "1", "model": "Zwave", "manufacturer": "" } }
Lights get a little tricker, as annoyingly the payload on & payload off are supposed to match the state, which because I am using the API it does not...
{ "name": "In_wall_study_switch", "state_topic": "zwave/Study/21/37/1/0", "command_topic": "zwave/_CLIENTS/ZWAVE_GATEWAY-Mos_mqtt/api/setValue/set", "availability_topic": "zwave/Study/21/status", "brightness_command_topic": "zwave/Study/21/38/1/0/set", "brightness_state_topic": "zwave/Study/21/38/1/0", "payload_on": "{ \"args\":[21,37,1,0,true]}", "payload_off": "{ \"args\":[21,37,1,0,false]}", "state_value_template": "{% if value_json.value == true %}{ \"args\":[21,37,1,0,true]}{% else %}{ \"args\":[21,37,1,0,false]} {% endif %}", "brightness_scale": 99, "qos": 2, "retain": false, "payload_available": "true", "payload_not_available": "false", "unique_id": "study_switch_111", "on_command_type": "first", "device": { "identifiers": "inwallstudyswitch111", "name": "in_wall_study_switch", "sw_version": "1", "model": "Zwave", "manufacturer": "" } }
A couple of things to note:
HA throws no error if you miss the device, but you can't set an area for an entity without a device block.. so I added it.
the brightness scale depends on the switch, my nano dimmers accept 1 to 99, where as HA can provide any value to 255 I believe, so that limits that
On_command_type is set to first, as I was finding that for my dimmer if I sent the on / off and then the brightness something was happening where it would not changed, first made the brightness go first.
Anyways this is how I have manually set them up so that HA can be left running and I don't have to play around with the config & keep rebooting..
Switch returns multiple conflicting changes
2019-03-09T14:04:28.547Z z2m:App Zwave api call: setValue [ 4, 37, 1, 0, false ]
2019-03-09T14:04:28.547Z z2m:Zwave Success zwave api call setValue
2019-03-09T14:04:28.702Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:true -> false
2019-03-09T14:04:28.724Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:30.424Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:35.068Z z2m:App Zwave api call: setValue [ 4, 37, 1, 0, true ]
2019-03-09T14:04:35.068Z z2m:Zwave Success zwave api call setValue
2019-03-09T14:04:35.131Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:35.204Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:35.274Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:39.431Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> true
2019-03-09T14:04:47.767Z z2m:App Zwave api call: setValue [ 4, 37, 1, 0, false ]
2019-03-09T14:04:47.768Z z2m:Zwave Success zwave api call setValue
2019-03-09T14:04:47.962Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:true -> false
2019-03-09T14:04:52.424Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> false
2019-03-09T14:04:59.582Z z2m:App Zwave api call: setValue [ 4, 37, 1, 0, true ]
2019-03-09T14:04:59.583Z z2m:Zwave Success zwave api call setValue
2019-03-09T14:04:59.692Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:false -> true
2019-03-09T14:05:04.472Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:true -> true
2019-03-09T14:05:04.514Z z2m:Zwave zwave node 4: changed: 37-1-0:Switch:true -> true
When using the toggle button on the UI it detects multie state changes. This is very hard to filter out on some MQTT clients as they also gets multiple changes.
Usually the first one is the correct one, but not always.
Question: Get current state from a node_id
Hi there.
I'm struggling with the api. I have set everything up and I can get all subscriptions on a topic. But when I start my own application I want to get the current value/state for a node.
I have tried to publish to this topic:
<prefix>/<?Location>/<node_name>/status or <prefix>/<?Location>/<node_name>/status/set
Where my prefix are set in my settings, and location is set to Kontor.
What am I missing here?
I'm kinda lost, so hope somebody could help me out :)
If this is the wrong place to publish questions I'm sorry.
Best Regards
Kjetil
Protocol support in host url
Maybe I am missing something but passing in the host and port to the mqtt options.servers array inside lib/MqttClient.js doesn't seem to allow me to connect to a tls secured mosquitto broker.
If I manually change the code to be var client = mqtt.connect('tls://mqtt.example.com', options) then everything works as expected and a connection to the mqtt broker is established.
I have tried messing around with putting the url in the "Host url" section of the web UI and that results in connection failures that look like:
1556827963: New connection from 10.8.8.98 on port 8883.
1556827963: OpenSSL Error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
1556827963: Socket error on client <unknown>, disconnecting.
[feature] parse alarm command class
It would be nice that the alarm command clase would be translated to a descriptive string for the value. (Or maybe make it configurable)
https://github.com/OpenZWave/open-zwave/wiki/Alarm-Command-Class
Question: No message when switch changed physically
I'm not receiving messages when my Leviton Dimmer Switch is changed physically. If it's changed via the API I receive the appropriate messages. Is this by design?
Using openzwave 1.6 git build breaks nodes that are sleeping on startup
At startup they show as DEAD again.
After the first checkin they show up correctly,... but the location and name get cleared. Node now shows as SLEEPING
The received data from the node gets send to mqtt without the name/location so node-red (in my case) does no longer matches on the mqtt messages.
If I try to set the name and location again, the node ends up in the REMVOED state. (It does not show up again after another checkin, restarting zwave2mqtt brings it back)
enablePoll / disablePoll does not update the is_polled flag of full zwave payload
While trying to solve #12 I was playing with enablePoll/disablePoll.
- start zwave2mqtt with poll disabled for the value
- send
{"args":[{"node_id":4,"class_id":37,"instance":1,"index":0}]}tozwave/_CLIENTS/ZWAVE_GATEWAY-mosca/api/enablePoll/set - we now get the value every few seconds (frequency has no effect :()
For the message received now this is the payload
{"value_id":"4-37-1-0","node_id":4,"class_id":37,"type":"bool","genre":"user","instance":1,"index":0,"label":"Switch","units":"","help":"","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"value":true}
- (optionally disable poll again) send
{"args":[{"node_id":4,"class_id":37,"instance":1,"index":0}]}tozwave/_CLIENTS/ZWAVE_GATEWAY-mosca/api/disablePoll/set
As you can see the polled message have is_polled set to false!
[Question] fgk-101 as doorbell not populating correctly
Hi,
I have recently moved over from HA zwave as I found that the constant reboots were messing up the network, one thing that I am missing however the ability to trip a fgk-101 device with a doorbell (found an article online) under HA it would change the status of the device from on to off and back again (about 10 times in a row), which I could then attach automation to trigger alerts etc..
Under zwave2mqtt I see that it nothing changes on the MQTT or zwave (webpage), however if I debug I see :
z2m:Zwave node event 15 0 +315ms
OpenZWave Detail, Node015, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0f, 0x03, 0x20, 0x01, 0x00, 0xdf
OpenZWave Detail,
OpenZWave Info, Node015, Received Basic set from node 15: level=0. Sending event notification.
OpenZWave Detail, Node015, Notification: NodeEvent
z2m:Zwave node event 15 255 +179ms
OpenZWave Detail, Node015, Received: 0x01, 0x09, 0x00, 0x04, 0x00, 0x0f, 0x03, 0x20, 0x01, 0xff, 0x20
OpenZWave Detail,
OpenZWave Info, Node015, Received Basic set from node 15: level=255. Sending event notification.
OpenZWave Detail, Node015, Notification: NodeEvent
So the zwave info it being sent and the level set from off to on when the doorbell goes.
My question is: what is the easiest / best way (might be two different options) to map this change either into MQTT or as a websocket / command to node-red?
Cheers
[feat] Publish scene event to MQTT
I'm trying to react to different button-presses on the NodOn Octan Remote.
When set to "Scene activation" it publishes scene events. OpenZWave correctly receives them and I was able to access these events within NodeRed (and the Open-Z-Wave-components).
I also see the events in the Zwave2Mqtt-log:
My request is that you publish those events to MQTT. I suggest a topic parallel to the status, like <prefix>/<nodeid>/scene
Constant MQTT disconnect/reconnect.
I'm seeing a constant disconnect/reconnecting of the MQTT client. I'm running a mosquitto client on the same Raspberry pi that zwave2mqtt and HA are running on. My zwave2mqtt logs are filled with this:
2019-06-28T04:42:10.379Z z2m:Mqtt MQTT client reconnecting
2019-06-28T04:42:10.384Z z2m:Mqtt MQTT client closed
2019-06-28T04:42:15.389Z z2m:Mqtt MQTT client reconnecting
2019-06-28T04:42:15.393Z z2m:Mqtt MQTT client closed
2019-06-28T04:42:20.395Z z2m:Mqtt MQTT client reconnecting
2019-06-28T04:42:20.400Z z2m:Mqtt MQTT client closed
I'm fairly certain that the gateway isn't talking to the MQTT broker at all either. My zwave devices don't respond to injected messages, and the gateway doesn't seem to send out any messages when I trigger the devices. Is this a misconfiguration on my end, or a problem with the code? The auth details are correct, as are the URL and Port.
Support user defined aliases instead of numeric IDs in ValueId gateway type
I see the argument against using names for the value classes (localisation, subject to change, etc.). However, it would be great if nodes could still be named. Those arguments do not apply to node names as they are specified manually in the UI.
This would help tremendously with moving/replacing z-wave devices.
Currently the options are /33/112/1/90, requiring downstream consumers to keep track of Node IDs, or /door5/sensor_binary/sensor, where sensor_binary and sensor are not guaranteed to be stable since they come from an external library. If we had a hybrid option like /door5/112/1/90, then consumers do not need to know which node ID to use, but they can still use constant IDs for the value.
[QUESTION] Copy HA xml file(s)?
Is it possible to copy (from HA installation) the two zwave configuration files to a fresh install on a rpi3b and not have to set everything up again?
Battery Powered devices marked as DEAD
Some battery powered devices like ZW100 MultiSensor 6 (AEON Labs) are detected as DEAD after stratup and do not have the type/product fields loaded. (zwcfg has the device with all the info)
Under settings -> zwave I have Assume Awake toggled disabled.
The only way for the device to show online is by manually waking it (physically) and sending a NIF request to the device. After that it will be correctly marked as sleeping
Enabeling/disabling zwave logging does not take effect on save.
When enabling or disabling the logging toggle and hitting safe, logging is not enabled|disabled.
Neither software not documentation contains any default values or explanations
I am trying to - still not successful - setup this project.
I have the software compiled and running - but setting it up is almost impossible
Many of the settings are just blank fields.
What is the format of the network ID?
What poll interval should I use? I know little about z-wave - I have no idea if this should be 1 ms, or 10 ms, or 10000 ms. What is a good common sense default value? What is the minimum that will not make a zwave network collape?
What does the "Assume Awake" mean?
mqtt
What is a sensible reconnect interval?
What is the clean flag? What is recommended? Put a default and not a blank here
You can get this fixed easily in minutes by at least editing the documentation. And do not ask me to do it because I do not know the answers. I am totally confused
Set row number per page
Is it possible to change the default rows per page to something else?
The default appears to be 10, however i prefer 50 or All (50 does not exist), so wondered if there was a config setting to change the default or some JS that can force it to change?
[bug] Empty node type and product after adding new device
Version
Got this bug in version in the latest stable and the current head.
Steps:~
-add a new node
-Choosing in the UI the controller option "Add node", cancel the secure option
-Including the node by pressing the including option on the node
-The node is added successful
The new node is displayed in the list but with an empty type and product. It looks like there's no refresh or something.
When I look at the log I see all the information. In the UI all the entities and config option are available in the UI. Renaming the node in the UI are not displayed in the interface.
When I restart the application of docker container the type, product and new node name is displayed correctly.
How to access second channel on multi-zoned thermostat?
Hi,
I have a "SSR 302 2-zone Thermostat Receiver (Horstmann (Secure Meters))" (https://www.vesternet.com/mwdownloads/download/link/id/517/) which exposes two channels to switch on either the central heating or the hot water cylinder.
If I switch the "Mode" of value 3-64-2-0 using the web UI of Zwave2Mqtt, I see the following on the MQTT bus:
zwave/utility/heating/thermostat_mode/mode {"value_id":"3-64-2-0","node_id":3,"class_id":64,"type":"list","genre":"user","instance":2,"index":0,"label":"Mode","units":"","help":"","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"values":["Off","Heat"],"value":"Heat"}
And the 2nd channel of the thermostat activates as expected.
How can I use the gateway to toggle this? I have tried:
mosquitto_pub -t zwave/utility/heating/thermostat_mode/mode/set -m '{"value_id":"3-64-2-0","node_id":3,"class_id":64,"type":"list","genre":"user","instance":2,"index":0,"label":"Mode","units":"","help":"","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"values":["Off","Heat"],"value":"Heat"}'
But for some reason - that actually toggles channel 1 and not channel 2, resulting in the following output on the MQTT bus:
zwave/utility/heating/thermostat_mode/mode/set {"value_id":"3-64-2-0","node_id":3,"class_id":64,"type":"list","genre":"user","instance":2,"index":0,"label":"Mode","units":"","help":"","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"values":["Off","Heat"],"value":"Heat"}
zwave/utility/heating/thermostat_mode/mode {"value_id":"3-64-1-0","node_id":3,"class_id":64,"type":"list","genre":"user","instance":1,"index":0,"label":"Mode","units":"","help":"","read_only":false,"write_only":false,"min":0,"max":0,"is_polled":false,"values":["Off","Heat"],"value":"Heat"}
Note above, the value_id being set is 3-64-2-0 but the value being altered is 3-64-1-0 (i.e. the other channel).
Am I sending the wrong command to the MQTT gateway here?
Battery Level reported incorrectly in UI and MQTT messages
<CommandClass id="128" name="COMMAND_CLASS_BATTERY" version="1" request_flags="4" innif="true">
<Instance index="1" />
<Value type="byte" genre="user" instance="1" index="0" label="Battery Level" units="%" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="0" max="255" value="100" />
</CommandClass>One of my devices is battery powered and is zwave2mqtt is getting an incorrect Battery Level reading from COMMAND_CLASS_BATTERY.
On OpenHAB the device reads 100% with 2 fresh batteries and 50% with just one battery plugged in.
For zwave2mqtt the value is displayed as '0' in the interface and on the MQTT messages. When checking zwcfg.xml (because it also saves current values) it properly has the value set 100.
Invalid Network Key. Does not contain 16 Bytes - Contains 1
Hi,
First of all kudos on the software!
I've run into a snag whilst getting this up and running, working without a security key is fine however when trying to add one openzwave fails. What format should the key be in? I have tried the following in the text box yet each one fails:
0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA
"0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA"
[0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA]
{0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA}
'0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA'
0xE1 0x40 0xE5 0x36 0x2E 0xD2 0xC6 0x42 0x28 0xB1 0x07 0xBF 0x9B 0x81 0x4A 0xDA
It seems to only capture the last byte and not the other 15. Error message:
zwave2mqtt | Initialising OpenZWave 1.4.3335 binary addon for Node.JS. zwave2mqtt | OpenZWave Security API is ENABLED zwave2mqtt | ZWave device db : /usr/local/etc/openzwave zwave2mqtt | User settings path : /opt/zwave2mqtt/source zwave2mqtt | Option Overrides : --Logging true --ConsoleOutput true --QueueLogLevel 8 --DriverMaxAttempts 3 --NetworkKey {0xE1, 0x40, 0xE5, 0x36, 0x2E, 0xD2, 0xC6, 0x42, 0x28, 0xB1, 0x07, 0xBF, 0x9B, 0x81, 0x4A, 0xDA} --SaveConfiguration true zwave2mqtt | 2019-02-05T09:07:48.338Z z2m:Zwave Connecting to /dev/ttyACM0 zwave2mqtt | 2019-02-05 09:07:48.342 Always, OpenZwave Version 1.4.3335 Starting Up zwave2mqtt | 2019-02-05 09:07:48.344 Info, Setting Up Provided Network Key for Secure Communications zwave2mqtt | 2019-02-05 09:07:48.345 Warning, Invalid Network Key. Does not contain 16 Bytes - Contains 1 zwave2mqtt | 2019-02-05 09:07:48.346 Warning, Raw Key: 0xDA} zwave2mqtt | 2019-02-05 09:07:48.347 Warning, Parsed Key: zwave2mqtt | 2019-02-05 09:07:48.348 Warning, 1) - 0xDA} zwave2mqtt | 2019-02-05 09:07:48.349 Error, Exception: Driver.cpp:6772 - 103 - Failed to Read Network Key
Thanks
Start inclusion in secure mode
It doesn't look posible to start a secure inclusion via the control panel, it should be the same as regular inclusion but passing 'true' as the first argument.
Container won't start for the second time
When I run sudo docker run --rm -it -p 8091:8091 --device=/dev/ttyAMA0 -v /var/lib/zwave2mqtt:/usr/src/app/store robertslando/zwave2mqtt:latest, configure everything and press CTRL-C.
It won't start the second time with this error message:
fs.js:1061
return binding.unlink(pathModule._makeLong(path));
^
Error: ENOENT: no such file or directory, unlink 'zwcfg_0xf5a134ce.xml'
at Object.fs.unlinkSync (fs.js:1061:18)
at fs.readdir.files.forEach.file (/snapshot/Zwave2Mqtt/lib/ZwaveClient.js:0:0)
at Array.forEach (<anonymous>)
at fs.readdir (/snapshot/Zwave2Mqtt/lib/ZwaveClient.js:0:0)
at FSReqWrap.oncomplete (fs.js:135:15)
pi@zigzag:~ $ sudo docker run --rm -it -p 8091:8091 --device=/dev/ttyAMA0 -v /var/lib/zwave2mqtt:/usr/src/app/store robertslando/zwave2mqtt:latest
Any idea?
Request - Node Location
Hi,
Wondering whether a button to disable showing node_location in the topic even when present?
I like the node_location feature however if zwave2mqtt restarts then it needs to wait until the devices have woken up and synced it's status before it picks up the location again. Or maybe I'm missing something?
I have this running in docker so maybe there are persistent files I need to look out for.
Thanks
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.