Battery Powered devices marked as DEAD about zwave2mqtt

[sjorge]

Works fine now!

[jamesarbrown]

I was trying to investigate and i found this
#284 (comment)

It fixed my issue

[sjorge]

I managed to get most things working aside from battery level and the very annoying issues with switches, linking these to homekit using node-red is causing mayham due to the multiple conflicting state changes, I backed this config so I can quickly go back to the state I am at now. But I did revert to OpenHAB for my current flow as now so I have a working setup

Overall zwave2mqtt has a lot of potential but it has a few rought corners, I'm happy to help you get them fixed. If there is any extra info you need, I'll try to provide it.

[robertsLando]

Did you try to set the Assume Awake option enabled? Battery powered devices usually need that to be awaken on init

[robertsLando]

I thank you for your feedbacks and I will try to fix them all but some bugs related with the protocols most times are related to node-openzwave and Openzwave library, maybe you can find your issues there too

[sjorge]

Well thats the thing, the device is not awake at startup because it sleeps for ~20min and then sends an update. (Unless there is movement, then it sends it imediatly)

Wouldn't assume awake make it worse? I think the table should alteast load the type/product info from the zcfg.zml file in that case. I can see this getting very confusing if there are multiple battery devices.

Also the type/product does not get update once the devices checks it, the node state is properly set to 'Sleep' after the first update though.

--- that was a bit confusing, let me try in a few bullets

• Wouldn't setting Assume Awake make it worse? As the battery devices are sleeping.
• It would be nice to load the type/product info form the zcfg.xml if a device is not responding on startup.
• The type/product info does not get update once the device wakes up and sends data
• The state of the node is OK after the first wakeup and set to sleeping.

[robertsLando]

I can try to fetch the type/product from zwcfg_...xml file on init but I don't know how to detect devices as sleeping on start

Try to send testNode on a device, does the state is correctly updated to sleeping then?

If so I could make an automatic function that sends the testNode to each dead device on init

[robertsLando]

Does send a NIF request to the sleeping nodes on init would fix the problem?

[robertsLando]

Try with this fix ed6acb0 and let me know @sjorge

[sjorge]

That didn't help, as the node deos not respond to a NIF command while it is sleeping.

Here is the log from the startup

2019-03-11T12:33:32.478Z z2m:Store scenes.json not found
2019-03-11T12:33:32.913Z z2m:App Application path:/opt/zwave2mqtt
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 false --ConsoleOutput false --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 15000 --NetworkKey XXXREMOVEDXXX
2019-03-11T12:33:33.030Z z2m:Zwave Connecting to /dev/cua/0
2019-03-11T12:33:33.129Z z2m:App Listening on port 8091
2019-03-11T12:33:33.203Z z2m:Mqtt MQTT client connected
2019-03-11T12:33:33.217Z z2m:Zwave Scanning network with homeid: 0xfc20d090
2019-03-11T12:33:33.218Z z2m:Zwave Node added 1
2019-03-11T12:33:33.220Z z2m:Zwave ValueAdded: 1-32-1-0 Basic
2019-03-11T12:33:33.220Z z2m:Zwave Node added 2
2019-03-11T12:33:33.223Z z2m:Zwave ValueAdded: 2-48-1-0 Sensor
2019-03-11T12:33:33.223Z z2m:Zwave ValueAdded: 2-49-1-1 Temperature
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-3 Luminance
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-5 Relative Humidity
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-49-1-27 Ultraviolet
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-94-1-0 ZWave+ Version
2019-03-11T12:33:33.224Z z2m:Zwave ValueAdded: 2-94-1-1 InstallerIcon
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-94-1-2 UserIcon
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-2 Wake up 10 minutes on Power On
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-3 On time
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-4 Enable Motion Sensor
2019-03-11T12:33:33.225Z z2m:Zwave ValueAdded: 2-112-1-5 Command Options
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-8 Awake timeout
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-9 Current power mode
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-39 Low Battery
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-40 Report Only On Thresholds
2019-03-11T12:33:33.226Z z2m:Zwave ValueAdded: 2-112-1-41 Temperature Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-42 Humidity Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-43 Luminance Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-44 Battery Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-45 UV Reporting Threshold
2019-03-11T12:33:33.227Z z2m:Zwave ValueAdded: 2-112-1-46 Low Temp Alarm
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-48 Enable/disable to send a report on Threshold
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-49 Set the upper limit value of temperature sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-50 Set the lower limit value of temperature sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-51 Set the upper limit value of humidity sensor
2019-03-11T12:33:33.228Z z2m:Zwave ValueAdded: 2-112-1-52 Set the lower limit value of humidity sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-53 Set the upper limit value of Lighting sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-54 Set the lower limit value of Lighting sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-55 Set the upper limit value of ultraviolet sensor
2019-03-11T12:33:33.229Z z2m:Zwave ValueAdded: 2-112-1-56 Set the lower limit value of ultraviolet sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-57 Set the recover limit value of temperature sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-58 Set the recover limit value of humidity sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-59 Set the recover limit value of Lighting sensor
2019-03-11T12:33:33.230Z z2m:Zwave ValueAdded: 2-112-1-60 Set the recover limit value of Ultraviolet sensor
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-61 Get the out-of-limit state of the Sensors
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-64 Temperature scale
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-81 LED blinking report
2019-03-11T12:33:33.231Z z2m:Zwave ValueAdded: 2-112-1-100 Reset Params 101-103 to Default
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-101 Group 1 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-102 Group 2 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-103 Group 3 Reports
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-110 Reset Params 111-113 to Default
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-111 Group 1 Interval
2019-03-11T12:33:33.232Z z2m:Zwave ValueAdded: 2-112-1-112 Group 2 Interval
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-113 Group 3 Interval
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-201 Temperature Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-202 Humidity Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-203 Luminance Calibration
2019-03-11T12:33:33.233Z z2m:Zwave ValueAdded: 2-112-1-204 Ultraviolet Calibration
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-112-1-252 Enable/disable Lock Configuration
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-112-1-255 Reset To Factory Defaults
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-0 Alarm Type
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-1 Alarm Level
2019-03-11T12:33:33.234Z z2m:Zwave ValueAdded: 2-113-1-2 SourceNodeId
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-113-1-10 Burglar
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-0 Powerlevel
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-1 Timeout
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-2 Set Powerlevel
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-3 Test Node
2019-03-11T12:33:33.235Z z2m:Zwave ValueAdded: 2-115-1-4 Test Powerlevel
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-5 Frame Count
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-6 Test
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-7 Report
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-8 Test Status
2019-03-11T12:33:33.236Z z2m:Zwave ValueAdded: 2-115-1-9 Acked Frames
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-128-1-0 Battery Level
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-1 Minimum Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-2 Maximum Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-3 Default Wake-up Interval
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-4 Wake-up Interval Step
2019-03-11T12:33:33.237Z z2m:Zwave ValueAdded: 2-132-1-0 Wake-up Interval
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-0 Library Version
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-1 Protocol Version
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 2-134-1-2 Application Version
2019-03-11T12:33:33.238Z z2m:Zwave Node added 4
2019-03-11T12:33:33.238Z z2m:Zwave ValueAdded: 4-37-1-0 Switch
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-39-1-0 Switch All
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-0 Energy
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-1 Previous Reading
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-2 Interval
2019-03-11T12:33:33.239Z z2m:Zwave ValueAdded: 4-50-1-8 Power
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-16 Voltage
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-20 Current
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-32 Exporting
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-50-1-33 Reset
2019-03-11T12:33:33.240Z z2m:Zwave ValueAdded: 4-94-1-0 ZWave+ Version
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-94-1-1 InstallerIcon
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-94-1-2 UserIcon
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-3 Over current protection
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-4 Over heat protection
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-20 Status re-power on
2019-03-11T12:33:33.241Z z2m:Zwave ValueAdded: 4-112-1-21 WallSwipe IR sensor
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-64 WallSwipe button color
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-65 WallSwipe LED Up gesture action
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-66 WallSwipe LED Down gesture action
2019-03-11T12:33:33.242Z z2m:Zwave ValueAdded: 4-112-1-67 WallSwipe LED Left gesture action
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-68 WallSwipe LED Right gesture action
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-69 WallSwipe Night light
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-71 WallSwipe sensitivity
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-80 Notification report association group 1
2019-03-11T12:33:33.243Z z2m:Zwave ValueAdded: 4-112-1-81 Notification report using the external switch 1
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-82 Notification report using the external switch 2
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-83 LED status
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-84 Time set for Night light mode
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-86 Set the ON time of output load
2019-03-11T12:33:33.244Z z2m:Zwave ValueAdded: 4-112-1-87 Set the OFF time of output load
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-90 Enable/disable the parameter 91 and 92
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-91 Minimum Change to send Report (Watt)
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-92 Minimum Change to send Report (%)
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-100 Default Group Reports
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-101 Report type sent in Reporting Group 1
2019-03-11T12:33:33.245Z z2m:Zwave ValueAdded: 4-112-1-102 Report type sent in Reporting Group 2
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-103 Report type sent in Reporting Group 3
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-110 Set 111-113 to default
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-111 Send Interval for Reporting Group 1
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-112 Send Interval for Reporting Group 2
2019-03-11T12:33:33.246Z z2m:Zwave ValueAdded: 4-112-1-113 Send Interval for Reporting Group 3
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-120 Set the external S1 mode
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-121 Set the external S2 mode
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-122 Control destination for S1
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-123 Control destination for S2
2019-03-11T12:33:33.247Z z2m:Zwave ValueAdded: 4-112-1-144 WallSwipe
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-247 S1/S2 when the Switch mode is 3-way switch
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-248 Function of S1/S2
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-251 Configuration factory reset function
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-252 Configuration Locked
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-112-1-255 Reset To Factory Defaults
2019-03-11T12:33:33.248Z z2m:Zwave ValueAdded: 4-113-1-0 Alarm Type
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-1 Alarm Level
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-2 SourceNodeId
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-7 Heat
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-113-1-11 Power Management
2019-03-11T12:33:33.249Z z2m:Zwave ValueAdded: 4-115-1-0 Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-1 Timeout
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-2 Set Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-3 Test Node
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-4 Test Powerlevel
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-5 Frame Count
2019-03-11T12:33:33.250Z z2m:Zwave ValueAdded: 4-115-1-6 Test
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-7 Report
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-8 Test Status
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-115-1-9 Acked Frames
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-129-1-0 Day
2019-03-11T12:33:33.251Z z2m:Zwave ValueAdded: 4-129-1-1 Hour
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-129-1-2 Minute
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-0 Library Version
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-1 Protocol Version
2019-03-11T12:33:33.252Z z2m:Zwave ValueAdded: 4-134-1-2 Application Version
2019-03-11T12:33:37.379Z z2m:App New connection P95jcp1Jpi1H6IPXAAAA
2019-03-11T12:33:37.630Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:37.658Z z2m:Zwave Notification from node 4: Notification - NoOperation (2)
2019-03-11T12:33:37.658Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:37.665Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-11T12:33:37.777Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-11T12:33:37.777Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:37.789Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-11T12:33:38.078Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-11T12:33:38.082Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-11T12:33:42.536Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:47.154Z z2m:App User disconnected P95jcp1Jpi1H6IPXAAAA
2019-03-11T12:33:47.200Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-11T12:33:47.203Z z2m:Zwave Notification from node 2: Notification - Node Dead (5)
2019-03-11T12:33:47.642Z z2m:Zwave node 4 ready: AEON Labs - ZW116 Nano Switch (On/Off Power Switch)
2019-03-11T12:33:47.644Z z2m:Zwave Network scan complete. Found: 3 nodes
2019-03-11T12:33:47.644Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-11T12:33:47.644Z z2m:Zwave controller command { nodeid: 0, state: 3, errcode: 10, help: 'Error - Failed' }
2019-03-11T12:33:47.977Z z2m:App New connection o6OAxznl529W-8WRAAAB
2019-03-11T12:33:57.868Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:57.869Z z2m:Zwave zwave node 4: changed: 50-1-0:Energy:3.175 -> 3.175
2019-03-11T12:33:57.870Z z2m:Zwave zwave node 4: changed: 50-1-1:Previous Reading:3.175 -> 3.175
2019-03-11T12:33:57.870Z z2m:Zwave zwave node 4: changed: 50-1-2:Interval:4 -> 11
2019-03-11T12:33:57.968Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:57.968Z z2m:Zwave zwave node 4: changed: 50-1-8:Power:6.4 -> 6.404
2019-03-11T12:33:58.068Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:58.069Z z2m:Zwave zwave node 4: changed: 50-1-16:Voltage:227.575 -> 227.341
2019-03-11T12:33:58.167Z z2m:Zwave zwave node 4: changed: 50-1-32:Exporting:false -> false
2019-03-11T12:33:58.168Z z2m:Zwave zwave node 4: changed: 50-1-20:Current:0.087 -> 0.092

I tried with both Assume Awake enabled and disabled.

[sjorge]

Node 2 being the battery powered node that is asleep, it also does not respond to test node request.

The node does get the correct state after the first checkin, maybe we can just load the type/product for all nodes if it is in the config? That way I can atleast identify the really dead nodes from the ones that are marked dead but should be battery powered.

Remebering which node id are the battery powered ones is a pain, but the product should make that easier.

[robertsLando]

I could fetch the type/product on init but I would prefer a way to detect battery powered devices, can you find something in openzwave docs about this?

Maybe by sending a wakeup command if your device supports it?

I think that mark a node as dead if it doesn't respond to the initial scan is correct here and If I change this I could create errors in the case the node is really missing in my network. SO I think the best fix to this is to manually weak someway the node on init

[sjorge]

They seem to have the following command class:

                        <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="0" />
                        </CommandClass>

If is this one is present in the cached configuration, one can make a safe assumption that it is a battery powered device?

But is probably better to use the WAKE_UP class to find and keep track internally if a node is overdue (dead?) or still OK.

                     <CommandClass id="132" name="COMMAND_CLASS_WAKE_UP" version="2" request_flags="2" innif="true">
                                <Instance index="1" />
                                <Value type="int" genre="system" instance="1" index="0" label="Wake-up Interval" units="Seconds" read_only="false" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="1200" />
                                <Value type="int" genre="system" instance="1" index="1" label="Minimum Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="240" />
                                <Value type="int" genre="system" instance="1" index="2" label="Maximum Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3600" />
                                <Value type="int" genre="system" instance="1" index="3" label="Default Wake-up Interval" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="3600" />
                                <Value type="int" genre="system" instance="1" index="4" label="Wake-up Interval Step" units="Seconds" read_only="true" write_only="false" verify_changes="false" poll_intensity="0" min="-2147483648" max="2147483647" value="60" />
                        </CommandClass>

So this node checks in once every 1200 seconds, and sleeps in between. These appear to be standard command classes, so I think it is safe to assume if we have a WAKE_UP class we can mark it as 'Asleep' until the interval ~10% margin has passed and then mark it dead. Or reset the counter if it has checked in?

I think the WAKE_UP class is probably better than the battery class as there might be devices that have a battery but are always on? Both devices I had for testing were the same product so there config is the same.

Edit: From observation this also seems to be more or less what OpenHAB did. The device was Awake or Asleep until I removed the batteries and it missed a check in.

[robertsLando]

So in brief: I should check if a 'dead' device has COMMAND_CLASS_WAKE_UP after scan is done, set it to asleep, wait for Wake-up Interval seconds to check if it checks in than assume it 'dead' ?

Are you sure there is no way that openzwave can send a request to this node to manually trigger that 'check in' ? I think this would be lot easier and more correct

[robertsLando]

I have found this issue: OpenZWave/node-openzwave-shared#249 check it

[sjorge]

So in brief: I should check if a 'dead' device has COMMAND_CLASS_WAKE_UP after scan is done, set it to asleep, wait for Wake-up Interval seconds to check if it checks in than assume it 'dead' ?

Sounds about right

Are you sure there is no way that openzwave can send a request to this node to manually trigger that 'check in' ? I think this would be lot easier and more correct

Not on the once I have atleast, testNode, Send NIF, all the commands just fail.
The only way to force and early checkin is getting on a ladder and opening the battery compartment to push the little wake up switch needed for inclusion.

I have found this issue: OpenZWave/node-openzwave-shared#249 check it

Sounds different, after the first wake up of the node the table gets type/product update and all values start to come through.

[robertsLando]

@sjorge try this commit, I have added an event nodeAvailable that should be triggered before nodeReady and maybe it is what we are looking for, maybe battery power devices trigger the nodeAvailable event and not the nodeReady and I can get all info there. I have just placed a debug there so you can check in console output what happens.

Wait for your feedback

[sjorge]

2019-03-12T12:28:07.523Z z2m:Store scenes.json not found
2019-03-12T12:28:07.970Z z2m:App Application path:/opt/zwave2mqtt
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 false --ConsoleOutput false --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 15000 --NetworkKey XXX
2019-03-12T12:28:08.095Z z2m:Zwave Connecting to /dev/cua/0
2019-03-12T12:28:08.192Z z2m:App Listening on port 8091
2019-03-12T12:28:08.264Z z2m:Mqtt MQTT client connected
2019-03-12T12:28:08.279Z z2m:Zwave Scanning network with homeid: 0xfc20d090
2019-03-12T12:28:08.280Z z2m:Zwave Node added 1
2019-03-12T12:28:08.281Z z2m:Zwave Node ID 1 is available { manufacturer: 'Z-Wave.Me',
  manufacturerid: '0x0115',
  product: 'ZME_UZB1 USB Stick',
  producttype: '0x0400',
  productid: '0x0001',
  type: 'Static PC Controller',
  name: 'controller',
  loc: 'serverroom' }
2019-03-12T12:28:08.289Z z2m:Zwave ValueAdded: 1-32-1-0 Basic
2019-03-12T12:28:08.289Z z2m:Zwave Node added 2
2019-03-12T12:28:08.291Z z2m:Zwave Node ID 2 is available { manufacturer: 'AEON Labs',
  manufacturerid: '0x0086',
  product: 'ZW100 MultiSensor 6',
  producttype: '0x0002',
  productid: '0x0064',
  type: 'Home Security Sensor',
  name: 'multisensor',
  loc: 'bedroom' }
2019-03-12T12:28:08.291Z z2m:Zwave ValueAdded: 2-48-1-0 Sensor
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-1 Temperature
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-3 Luminance
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-5 Relative Humidity
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-49-1-27 Ultraviolet
2019-03-12T12:28:08.292Z z2m:Zwave ValueAdded: 2-94-1-0 ZWave+ Version
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-94-1-1 InstallerIcon
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-94-1-2 UserIcon
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-2 Wake up 10 minutes on Power On
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-3 On time
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-4 Enable Motion Sensor
2019-03-12T12:28:08.293Z z2m:Zwave ValueAdded: 2-112-1-5 Command Options
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-7 Parameter #7
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-8 Awake timeout
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-9 Current power mode
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-39 Low Battery
2019-03-12T12:28:08.294Z z2m:Zwave ValueAdded: 2-112-1-40 Report Only On Thresholds
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-41 Temperature Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-42 Humidity Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-43 Luminance Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-44 Battery Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-45 UV Reporting Threshold
2019-03-12T12:28:08.295Z z2m:Zwave ValueAdded: 2-112-1-46 Low Temp Alarm
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-48 Enable/disable to send a report on Threshold
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-49 Set the upper limit value of temperature sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-50 Set the lower limit value of temperature sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-51 Set the upper limit value of humidity sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-52 Set the lower limit value of humidity sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-53 Set the upper limit value of Lighting sensor
2019-03-12T12:28:08.296Z z2m:Zwave ValueAdded: 2-112-1-54 Set the lower limit value of Lighting sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-55 Set the upper limit value of ultraviolet sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-56 Set the lower limit value of ultraviolet sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-57 Set the recover limit value of temperature sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-58 Set the recover limit value of humidity sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-59 Set the recover limit value of Lighting sensor
2019-03-12T12:28:08.297Z z2m:Zwave ValueAdded: 2-112-1-60 Set the recover limit value of Ultraviolet sensor
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-61 Get the out-of-limit state of the Sensors
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-64 Temperature scale
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-81 LED blinking report
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-100 Reset Params 101-103 to Default
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-101 Group 1 Reports
2019-03-12T12:28:08.298Z z2m:Zwave ValueAdded: 2-112-1-102 Group 2 Reports
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-103 Group 3 Reports
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-110 Reset Params 111-113 to Default
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-111 Group 1 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-112 Group 2 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-113 Group 3 Interval
2019-03-12T12:28:08.299Z z2m:Zwave ValueAdded: 2-112-1-201 Temperature Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-202 Humidity Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-203 Luminance Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-204 Ultraviolet Calibration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-252 Enable/disable Lock Configuration
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-112-1-255 Reset To Factory Defaults
2019-03-12T12:28:08.300Z z2m:Zwave ValueAdded: 2-113-1-0 Alarm Type
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-1 Alarm Level
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-2 SourceNodeId
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-113-1-10 Burglar
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-0 Powerlevel
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-1 Timeout
2019-03-12T12:28:08.301Z z2m:Zwave ValueAdded: 2-115-1-2 Set Powerlevel
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-3 Test Node
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-4 Test Powerlevel
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-5 Frame Count
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-6 Test
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-7 Report
2019-03-12T12:28:08.302Z z2m:Zwave ValueAdded: 2-115-1-8 Test Status
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-115-1-9 Acked Frames
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-128-1-0 Battery Level
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-1 Minimum Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-2 Maximum Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-3 Default Wake-up Interval
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-4 Wake-up Interval Step
2019-03-12T12:28:08.303Z z2m:Zwave ValueAdded: 2-132-1-0 Wake-up Interval
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-0 Library Version
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-1 Protocol Version
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 2-134-1-2 Application Version
2019-03-12T12:28:08.304Z z2m:Zwave Node added 4
2019-03-12T12:28:08.304Z z2m:Zwave Node ID 4 is available { manufacturer: 'AEON Labs',
  manufacturerid: '0x0086',
  product: 'ZW116 Nano Switch',
  producttype: '0x0003',
  productid: '0x0074',
  type: 'On/Off Power Switch',
  name: 'socket_desk',
  loc: 'bedroom' }
2019-03-12T12:28:08.304Z z2m:Zwave ValueAdded: 4-37-1-0 Switch
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-39-1-0 Switch All
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-0 Energy
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-1 Previous Reading
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-2 Interval
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-8 Power
2019-03-12T12:28:08.305Z z2m:Zwave ValueAdded: 4-50-1-16 Voltage
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-20 Current
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-32 Exporting
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-50-1-33 Reset
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-0 ZWave+ Version
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-1 InstallerIcon
2019-03-12T12:28:08.306Z z2m:Zwave ValueAdded: 4-94-1-2 UserIcon
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-3 Over current protection
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-4 Over heat protection
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-20 Status re-power on
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-21 WallSwipe IR sensor
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-64 WallSwipe button color
2019-03-12T12:28:08.307Z z2m:Zwave ValueAdded: 4-112-1-65 WallSwipe LED Up gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-66 WallSwipe LED Down gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-67 WallSwipe LED Left gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-68 WallSwipe LED Right gesture action
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-69 WallSwipe Night light
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-71 WallSwipe sensitivity
2019-03-12T12:28:08.308Z z2m:Zwave ValueAdded: 4-112-1-80 Notification report association group 1
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-81 Notification report using the external switch 1
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-82 Notification report using the external switch 2
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-83 LED status
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-84 Time set for Night light mode
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-86 Set the ON time of output load
2019-03-12T12:28:08.309Z z2m:Zwave ValueAdded: 4-112-1-87 Set the OFF time of output load
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-90 Enable/disable the parameter 91 and 92
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-91 Minimum Change to send Report (Watt)
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-92 Minimum Change to send Report (%)
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-100 Default Group Reports
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-101 Report type sent in Reporting Group 1
2019-03-12T12:28:08.310Z z2m:Zwave ValueAdded: 4-112-1-102 Report type sent in Reporting Group 2
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-103 Report type sent in Reporting Group 3
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-110 Set 111-113 to default
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-111 Send Interval for Reporting Group 1
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-112 Send Interval for Reporting Group 2
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-113 Send Interval for Reporting Group 3
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-120 Set the external S1 mode
2019-03-12T12:28:08.311Z z2m:Zwave ValueAdded: 4-112-1-121 Set the external S2 mode
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-122 Control destination for S1
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-123 Control destination for S2
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-144 WallSwipe
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-247 S1/S2 when the Switch mode is 3-way switch
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-248 Function of S1/S2
2019-03-12T12:28:08.312Z z2m:Zwave ValueAdded: 4-112-1-251 Configuration factory reset function
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-112-1-252 Configuration Locked
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-112-1-255 Reset To Factory Defaults
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-0 Alarm Type
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-1 Alarm Level
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-2 SourceNodeId
2019-03-12T12:28:08.313Z z2m:Zwave ValueAdded: 4-113-1-7 Heat
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-113-1-11 Power Management
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-0 Powerlevel
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-1 Timeout
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-2 Set Powerlevel
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-3 Test Node
2019-03-12T12:28:08.314Z z2m:Zwave ValueAdded: 4-115-1-4 Test Powerlevel
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-5 Frame Count
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-6 Test
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-7 Report
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-8 Test Status
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-115-1-9 Acked Frames
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-129-1-0 Day
2019-03-12T12:28:08.315Z z2m:Zwave ValueAdded: 4-129-1-1 Hour
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-129-1-2 Minute
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-0 Library Version
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-1 Protocol Version
2019-03-12T12:28:08.316Z z2m:Zwave ValueAdded: 4-134-1-2 Application Version
2019-03-12T12:28:12.909Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:12.936Z z2m:Zwave Notification from node 4: Notification - NoOperation (2)
2019-03-12T12:28:12.937Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-12T12:28:12.943Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-12T12:28:13.073Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-12T12:28:13.073Z z2m:Zwave controller command { nodeid: 0, state: 1, errcode: 0, help: 'Starting' }
2019-03-12T12:28:13.086Z z2m:Zwave controller command { nodeid: 0, state: 6, errcode: 0, help: 'InProgress' }
2019-03-12T12:28:13.426Z z2m:Zwave controller command { nodeid: 0, state: 7, errcode: 0, help: 'Completed' }
2019-03-12T12:28:13.432Z z2m:Zwave node 1 ready: Z-Wave.Me - ZME_UZB1 USB Stick (Static PC Controller)
2019-03-12T12:28:18.037Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:22.676Z z2m:Zwave Notification from node 2: Notification - NoOperation (2)
2019-03-12T12:28:22.687Z z2m:Zwave Notification from node 2: Notification - Node Dead (5)
2019-03-12T12:28:23.116Z z2m:Zwave node 4 ready: AEON Labs - ZW116 Nano Switch (On/Off Power Switch)
2019-03-12T12:28:23.117Z z2m:Zwave Network scan complete. Found: 3 nodes

2019-03-12T12:28:08.291Z z2m:Zwave Node ID 2 is available { manufacturer: 'AEON Labs',
  manufacturerid: '0x0086',
  product: 'ZW100 MultiSensor 6',
  producttype: '0x0002',
  productid: '0x0064',
  type: 'Home Security Sensor',
  name: 'multisensor',
  loc: 'bedroom' }

There is a trigger fro the ndoe that is sleeping.

[robertsLando]

@sjorge Check my last commit and tell me if everything works now

[robertsLando]

Let me know if you find other bugs. Thank you @sjorge

[jamesarbrown]

Hi @robertsLando is there any chance of getting the docker image pushed up to 3.03 that includes this. Have same issue. I can only see ARM3.03 in there. I am very new to zwave2mqtt so apologies if i have missed something

[robertsLando]

@jamesarbrown I don't understand what you mean

[jamesarbrown]

At the time the docker did not seem to have 3.03 x64, so i cleaned and docker pull again and now its running on 3.03

But, it did not fix this issue for me on a Trisensor zwa005. My device still says dead immediately after restarting zwave2mqtt and even after waiting 2 days

https://github.com/OpenZWave/open-zwave/blob/master/config/aeotec/zwa005.xml

In the device table earlier today, also confirmed comms were active, by having an last active time of 5 hours ago.

Then I looked at the logs by creating a motion event and I can see the controller communicating with it... but still shows dead

2020-04-27 19:59:55.946 Detail, Node012, Decrypted Packet: 0x00, 0x30, 0x03, 0x00, 0x0c 2020-04-27 19:59:55.947 Detail, 2020-04-27 19:59:55.947 Info, Node012, ApplicationCommandHandler - Unhandled Command Class 0x30

Are there any logs / tests I can provide?

The only way I can get it to fix is to press the internal button for 5 sec until the little red LED comes, at which point the tables update and I get a "Sleep" status.

[jamesarbrown]

@robertsLando would it be possible to re-open this issue? or do you think its something different and I can open a new issue?

[robertsLando]

@jamesarbrown If you have refreshNodeInfo option enabled in Zwave settings please disable it

[jamesarbrown]

I have tried the refreshnodeinfo and still the device is marked as dead after some days. I am not sure about the operating details of zwave what it needs to get out of a dead state, but as you can see from this screenshot it has woken up in the past hours and connected in.

Is there anything that can be done to force a full wake up on check in, whilst the device has its zwave radio active?

[robertsLando]

@jamesarbrown Did you try to enable the option in zwave settings called assume awake?

Also let's see what @Fishwaldo says about this. Please @jamesarbrown add your OZW log file here

[jamesarbrown]

Assume Awake was off.... as I thought it should assume they are asleep

Then I turned it on and currently see no difference.

OZWLogStartup.txt
settings.zip

Will try to remember to do another log post after a considerable uptime

[jamesarbrown]

Node 16 seems to be busy but still flagged as dead

1526 Log
1526 Node 16 Logs.txt

Full Log
OZW_Log.txt

[robertsLando]

@Fishwaldo COuld you check the logs please?

[jamesarbrown]

@robertsLando @Fishwaldo
I set the wakeup time as low as possible and then waited on the logs

So, please find attached a node that is "DEAD" and wakes up, but sadly remains dead. Ozw2mqtt 3.2.1

deadnodewakeup.log

[onedr0p]

Looks like that option was removed #603

I wonder what the fix is now to make battery devices alive again after reboot without setting the physical to inclusion.

Am I missing something? I've read thru this issue and others but there doesn't seem to be a solid conclusion...

[robertsLando]

@onedr0p Just send refreshNodeInfo command as broadcast :) To send it as broadcast select that from controller actions and press ok on the popup

[jamesarbrown]

@robertsLando so by default refreshnodeinfo is OFF and does not occur on start?
@onedr0p as far as I was concerned the refreshnodeinfo was a startup thing and was breaking system due to sleeping devices. Looks to me like it's gone altogether which would have suggested it should just work as is?

[robertsLando]

so by default refreshnodeinfo is OFF and does not occur on start?

Yes. It was making too much confusion and there was peoples that was leaving that option on and that is not good.

[onedr0p]

I tried running all the commands last night and it would not come back alive. Now I woke up and I see it's working. Time heals all wounds 😅

[robertsLando]

@onedr0p Patience is the key 😆

[onedr0p]

I just restarted zwave2mqtt again and the device is dead. I am trying to run refreshnodeinfo but the device does not wake up. I know in time it will heal itself somehow but it's not ideal to wait :/

[robertsLando]

Unfortunately I have no idea how to help you with this, sorry

…

--- Daniel

On 14 Jul 2020, at 21:49, Devin Buhl ***@***.***> wrote:  I just restarted zwave2mqtt again and the device is dead. I am trying to run refreshnodeinfo but the device does not wake up. I know in time it will heal itself somehow but it's not ideal to wait :/ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[onedr0p]

No worries, here are the logs and if anyone is curious the device that is problematic is the Ecolink Zwave Plus Door & Window Sensor (DWZWAVE2.5-ECO)

The device is Node008.

OZW.log