Problem/Motivation

Looking for a health check so an external monitor can tell if the driver is up

Expected behavior

port 8091 isnt exposed so I cant use the official one

Actual behavior

n/a

Steps to reproduce

n/a

Proposed changes

I think just exposing port 8091 may allow me to use the curl check

curl http://192.168.100.16:8091/health/zwave -H "Accept: text/plain"

Problem/Motivation

After a couple of months of a happy working with no issues Z-Wave JS to MQTT install I have my devices listed as Unknown manufacturer/product. All except my Z‐Stick Gen5 USB Controller.
All happen after a rather long and unusual power outage (5 hours).
When power was restored I could not get my devices back.
After two days only a few devices (the ones without battery - directly connected to power) had reapered.
I was forced to wake up all my other devices forcing a connect. Unfortunately I had to rename all the reconnected devices in the end.
The devices are Alive and the Interview column shows as Completed. Some entities are on and others are offline. For example the battery values are available for most of the devices but the other device entities are not available.

Expected behavior

I was expecting that my raspberry pi 4 Home Assistant install and my Zwave devices database could survive a power outage.
I never had this behavior before moving to Zwave JS. I had the same setup running without this issue on older Zwave and Openzwave integrations and never loosed the devices.

Actual behavior

After coming up all devices were marked as "Unknown manufacturer/product".

Steps to reproduce

I decided to simulate a new power outage to see if I could reproduce the problem.
I removed the power from my pi 4 and was able to reproduce the problem after removing the power cable and reconnecting it after a couple of minutes.

Proposed changes

I don't have any suggestion. I can provide additional information and maybe this troubleshooting helps others or helps improving the integration.

Problem/Motivation

(Why the issue was filed)

Battery sensors show in HA as 100.0% seems a little excessive just 100% etc would be sufficient and keep with other battery values shown in HA

Expected behavior

(What you expected to happen)

dont need the one decimal point of battery

Actual behavior

(What actually happened)

always showing battery with a decimal point

Steps to reproduce

(How can someone else make/see it happen)

just add supervisior addon and pair device with battery then add to HA with official integration

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Remove the .0 on battery values HA on every other integration only shows battery values to the nearest 1 not .0

Problem/Motivation

When trying to open any file (such as nodes.json) from ZWaveJS2MQTT control panel > Store I receive the following error message: Request failed with status code 404

ZwaveJS2mqtt addon shows the following message in the logs:

2021-01-29 11:37:01.456 INFO APP: GET /api/store//data/store/settings.json 404 1.298 ms - 136 Error: Not Found at /opt/app.js:443:15 at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13) at /opt/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12) at next (/opt/node_modules/express/lib/router/index.js:275:10) at cors (/opt/node_modules/cors/lib/index.js:188:7) at /opt/node_modules/cors/lib/index.js:224:17 at originCallback (/opt/node_modules/cors/lib/index.js:214:15) at /opt/node_modules/cors/lib/index.js:219:13 at optionsCallback (/opt/node_modules/cors/lib/index.js:199:9) at corsMiddleware (/opt/node_modules/cors/lib/index.js:204:7) at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13) at /opt/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12)

Using Z-Wave JS to MQTT addon version 0.2.0 on core-2021.2.0b0 supervisor-2021.01.8.

This error was not received when using portainer and https://hub.docker.com/r/zwavejs/zwavejs2mqtt.

Expected behavior

Files should open without any errors.

Problem/Motivation

ZWave JS Integration doesn't start correctly

Expected behavior

ZWave JS to load.

Actual behavior

Log error:

Logger: homeassistant.components.zwave_js
Source: components/zwave_js/__init__.py:208
Integration: Z-Wave JS (documentation, issues)
First occurred: 6:11:19 PM (12 occurrences)
Last logged: 6:22:35 PM

Failed to connect: Z-Wave JS Server needs to be at least version 1.0.0. Found 1.0.0-beta.8
Failed to connect: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.1', 3000)]

Steps to reproduce

Try to load zwave_js with this addon in core-2021.3.0b0.

Proposed changes

Upgrade server to 1.0.0

I suspect that this is an issue with the core zwave_js integration, and I've filed a report, but I wanted to put an issue here as an FYI.

There is a bug in zwave js that fixes an issue with some inovelli light switches. Can this be pulled into this plugin also? zwave-js/node-zwave-js#2167

Problem/Motivation

(Why the issue was filed)

From the addon documentation I should be able to set the log level:

Option: log_level
The log_level option controls the level of log output by the addon and can be changed to be more or less verbose, which might be useful when you are dealing with an unknown issue. Possible values are:

However there is no where to insert this as the addon doesn't have a section that is editable.

Expected behavior

(What you expected to happen)

I expect to be able to type in the yaml config option

Actual behavior

(What actually happened)

These is no where to type in the yaml config option

Steps to reproduce

(How can someone else make/see it happen)

Install the zwavejs2mqtt add on and try to configure log level.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Missing the option to see removed devices after last update(could be the one before sins I did a 2 version update)

Expected behavior

to be able to filter them

Actual behavior

Missing option

Steps to reproduce

Proposed changes

make it possible to see removed devices and off course be able to reenable them by replacing node

Problem/Motivation

Fibaro Smoke Sensor not recognised after inclusion. Node is added but no information can be obtained.

(Why the issue was filed)
Not able to use Fibaro smoke sensor. Have tried both normal inclusion and secure inclusion.

Expected behavior

Node recognized as Fibaro smoke sensor.

(What you expected to happen)
Retrieve information of node

Actual behavior

Node added. No device info, manufacturer info and so on

(What actually happened)
Only Status is resolved. Status = asleep

Steps to reproduce

Open Control Panel.
Click on Add/Remove Device
Choose Secure Inclusion
Triple click on Fibaro Smoke Sensor
Node added but no info from device

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I'm using Aeotec Doorbell 6 (ZW164) and couldn't trigger the sound from Home assistant.

Expected behavior

I found an issue about ZW164 on Zwave2mqtt, ( cgarwood/homeassistant-zwave_mqtt#45 )
and it looks possible to make the sound by publishing a mqtt command.

Actual behavior

But mqtt topics of zwavejs2mqtt is little bit different with zwave2mqtt.

'homeassistant/nodeID_9/121/2/toneId' is the topic shows change when the doorbell make the sound by tampering.
and following is the value.
{
"id": "9-121-2-toneId",
"nodeId": 9,
"commandClass": 121,
"commandClassName": "Sound Switch",
"endpoint": 2,
"property": "toneId",
"propertyName": "toneId",
"type": "number",
"readable": true,
"writeable": true,
"label": "Play Tone",
"stateless": false,
"min": 0,
"max": 30,
"list": true,
"states": [
{
"text": "off",
"value": 0
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (5 sec)",
"value": 1
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (9 sec)",
"value": 2
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (11 sec)",
"value": 3
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (2 sec)",
"value": 4
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (13 sec)",
"value": 5
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (7 sec)",
"value": 6
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (31 sec)",
"value": 7
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (6 sec)",
"value": 8
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (11 sec)",
"value": 9
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (6 sec)",
"value": 10
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (35 sec)",
"value": 11
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (5 sec)",
"value": 12
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (38 sec)",
"value": 13
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (41 sec)",
"value": 14
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (37 sec)",
"value": 15
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (46 sec)",
"value": 16
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (35 sec)",
"value": 17
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (62 sec)",
"value": 18
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (15 sec)",
"value": 19
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (7 sec)",
"value": 20
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (8 sec)",
"value": 21
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (64 sec)",
"value": 22
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (4 sec)",
"value": 23
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (10 sec)",
"value": 24
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (4 sec)",
"value": 25
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (12 sec)",
"value": 26
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (1 sec)",
"value": 27
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (5 sec)",
"value": 28
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (2 sec)",
"value": 29
},
{
"text": "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000 (27 sec)",
"value": 30
},
{
"text": "default",
"value": 255
}
],
"value": 0,
"lastUpdate": 1614861583195,
"nodeName": "",
"nodeLocation": ""
}

I have completely no idea I have to publish what command to which topic to trigger the sound.

And I can trigger the sound from Zwavejs control panel below, but don't know how to use it in the automation.

Any advice would be appreciated

Proposed changes

I hope there are an entity to trigger the sound.

Problem/Motivation

(Why the issue was filed)

From the addon documentation I should be able to set the log level:

Option: log_level
The log_level option controls the level of log output by the addon and can be changed to be more or less verbose, which might be useful when you are dealing with an unknown issue. Possible values are:

However there is no where to insert this as the addon doesn't have a section that is editable.

Expected behavior

(What you expected to happen)

I expect to be able to type in the yaml config option

Actual behavior

(What actually happened)

These is no where to type in the yaml config option

Steps to reproduce

(How can someone else make/see it happen)

Install the zwavejs2mqtt add on and try to configure log level.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

When adjusting the the distance in the network graph the up button is inactive. Seems to affect Node size and Font size

Expected behavior

Up arrow to work

Actual behavior

Nothing happens

Steps to reproduce

Pull up the Network Graph

Problem/Motivation

The files that are showed in the store page of the UI cannot be showed. Clicking a file gives a "status request failed with status code 404" banner in the window below:

Expected behavior

If I selected a file, the contents is shown in the colomn on the right.

Actual behavior

Clicking a file gives a "status request failed with status code 404" banner in the window below.
Also downloading the files does not work properly.

In the log I see:
2021-02-06 13:35:09.948 INFO APP: GET /api/store//data/store/settings.json 404 3.092 ms - 1364 Error: Not Found at /opt/app.js:452:15 at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13) at /opt/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12) at next (/opt/node_modules/express/lib/router/index.js:275:10) at cors (/opt/node_modules/cors/lib/index.js:188:7) at /opt/node_modules/cors/lib/index.js:224:17 at originCallback (/opt/node_modules/cors/lib/index.js:214:15) at /opt/node_modules/cors/lib/index.js:219:13 at optionsCallback (/opt/node_modules/cors/lib/index.js:199:9) at corsMiddleware (/opt/node_modules/cors/lib/index.js:204:7) at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5) at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13) at /opt/node_modules/express/lib/router/index.js:284:7 at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12)

Steps to reproduce

Click a file in the store.

Proposed changes

Problem/Motivation

The UI of zwavejs2mqtt doesn't properly load

Expected behavior

The UI of zwavejs2mqtt should load

Actual behavior

After restarting the addon, clicking on "Open web UI" button or trying to launch the UI from the sidebar will not display the zwavejs2mqtt UI properly. Please check the attached screenshot.
Addon version: 0.2.3
No errors are shown in the log window.

Steps to reproduce

• Install addon-zwavejs2mqtt;
• Click the start button;
• Wait a few minutes for the addon to start.
• Open UI. Everything works properly;
• Click "Restart" button to restart the addon;
• Open UI. The UI won't load properly (see attached screenshot).

Proposed changes

I was not able to find any work-around.

My log shows MQTT is disabled. According to config docs, if MQTT add-on is installed, it should auto configure with it. How do I enable MQTT?

Problem/Motivation

The motion sensor of AEON Labs ZW074 MultiSensor Gen5 doesn´t return from "7 - Motion Detected" after first trigger.
When I re-interview the node I get no motion on the sensor but when motion is first detected then it never resets again until I re-Interview again. Refresh values etc. does not fix this.

The sensor was working fine until some weeks ago after an update and I haven't update or changed any configuration on the sensor.

Expected behavior

The motion sensor should reset after 240 secs of no motion.

Actual behavior

The motion sensor never resets.

After a re-interview the motion is not triggered until a "real" motion so the sensor is working correctly. The sensor is powered by mains and has a good link to the controller, all other values (temp, lux, humidity) are updating just fine.

node_43.json.txt

When I change a MQTT topic value, just as dimming speed on my light switch, it does NOT affect the diming speed.

When I change the value through the add-on; and I see the same MQTT topic change, it does affect the dimming speed.

Is there something Im doing wrong? I've tried setting values through node red or directly though MQTT explorer. The change looks to be the exact same as when I change it through the add-on, but it doesnt have an effect.

Problem/Motivation

According to ZWavejs2mqtt page I first had to file the issue here.

I migrated from OZW 1.6 to Zwave JS. I am running this addon, but I do not use MQTT. The home assistant integration connects to the websocket.

Two of the sensors I use is a Fibaro FGMS001 motion sensor. When running OZW, no issues.

When the sensor detects motion, it flashes and a motion report is received by Zwavejs. The sensor only flashes again after it stopped seeing motion for the setup duration amount of time and afterwards it sees motion again.
If I keep moving in front of the sensor, it flashes and reports motion. For some reason, after exactly 5min (almost to the ms accurate) I see in the logging that the motion value goes from detected to not detect. Weird thing is that this happens while I keep moving in front of the sensor. When it happens, the sensor does not flash again so it never stopped seeing motion. When I then stop moving, I see again in the logging the motion value changed from no motion to no motion. When I then move again, sensor flashes and in logging I see the motion detected.

Logging (I filtered on the sensor node):

Line 119: 2021-03-30 20:07:19.642 INFO ZWAVE: Node 22: value updated: 113-0-Home Security-Motion sensor status 0 => 8
Line 136: 2021-03-30 20:12:19.650 INFO ZWAVE: Node 22: value updated: 113-0-Home Security-Motion sensor status 8 => 0  ----> keep triggering sensor, where is this coming from?
Line 137: 2021-03-30 20:13:07.167 INFO ZWAVE: Node 22: value updated: 113-0-Home Security-Cover status 0 => 3          ----> moved sensor so it cannot see me anymore
Line 138: 2021-03-30 20:13:10.276 INFO ZWAVE: Node 22: metadata updated: 49-0-Illuminance
Line 139: 2021-03-30 20:13:10.280 INFO ZWAVE: Node 22: value updated: 49-0-Illuminance 25 => 2
Line 140: 2021-03-30 20:13:38.023 INFO ZWAVE: Node 22: value updated: 113-0-Home Security-Cover status 3 => 0          ----> tamper alarm retracted by sensor
Line 141: 2021-03-30 20:13:39.042 INFO ZWAVE: Node 22: value updated: 113-0-Home Security-Motion sensor status 0 => 0  ----> sensor reports no motion

I do not have this issue when running OZW 1.6. I don't think the sensor is sending a 'no motion event'. It almost looks there is a maximum somewhere defined that motion is allowed to be detected, however I do not see such a parameter in the configuration settings of the sensor.

I have this behaviour on both Fibaro motion sensors. Even when I don't touch the sensor, but actually stop moving (so tamper alarm does not trigger), it shows same behaviour. When I test for such behaviour on a Shenzen Neo PD03Z motion sensor, I do not see this issue.

Expected behavior

Motion is still detected. No motion detected only when there is really no motion.

Actual behavior

After exactly 5minutes, Zwavejs report no motion, even while I'm still dancing in front of the sensor.

Steps to reproduce

Start moving in front of the (Fibaro FGMS001) and keep monitoring the motion value changed event.

Proposed changes

Problem/Motivation

Today happened short power outage. HA node successfully started.
After some time I discovered: all ZWave nodes still unavailable.
In short - only manual re-interview for all nodes + integration restart helped.

Aeotec Stick was Ok, but other nodes not - only friendly name in list.
After every node re-interview: device info in Control Panel appears, like model etc.
But HA still not getting any data. Integration restart solved this las issue.

Expected behavior

Expected: all devices become available w/out user intervention - after HA server was restarted,

Actual behavior

All Z-Wave devices unavailable. In Control Panel they looks like:

Logs attached. Hope it will find the issue.
zwavejs2mqtt-store_20210405_11.zip
zwavejs2mqtt-store_20210405_12.zip

Steps to reproduce

Not sure.

Proposed changes

Problem/Motivation

Fresh install using documented steps does not seem to work with Aeotec z-stick Gen5.

Expected behavior

Z-Wave devices would pair / be included during inclusion.

Actual behavior

The following was observed in the add-on logs: 2021-03-23 08:31:59.159 INFO ZWAVE: Zwave client not connected startInclusion { success: false, message: 'Zwave client not connected' }

Steps to reproduce

1. Install Home Assistant OS 5.12 on Raspberry Pi 4. Minimally configured (add your user, home location, etc)
2. Install MQTT 5.1.1 add-on
3. Install zwavejs2mqtt 0.8.0 add-on
4. Start add-ons
5. Open zwavejs2mqtt web-ui
6. Configure ZWave serial port to /dev/ttyAMA0. Save. Restart add-on.
7. Return to Add-on web-ui and attempt to start inclusion.
8. View logs.

Full Add-on Log

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Z-Wave JS to MQTT
 Fully configurable Z-Wave JS to MQTT gateway and control panel
-----------------------------------------------------------
 Add-on version: 0.8.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 5.12  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.3.4
 Home Assistant Supervisor: 2021.03.6
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] configuration.sh: executing... 
[cont-init.d] configuration.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[08:31:35] INFO: Starting the Z-Wave JS to MQTT...
 ______                       _     ___                  _   _   
|___  /                      (_)   |__ \                | | | |  
   / /_      ____ ___   _____ _ ___   ) |_ __ ___   __ _| |_| |_ 
  / /\ \ /\ / / _` \ \ / / _ \ / __| / /| '_ ` _ \ / _` | __| __|
 / /__\ V  V / (_| |\ V /  __/ \__ \/ /_| | | | | | (_| | |_| |_ 
/_____|\_/\_/ \__,_| \_/ \___| |___/____|_| |_| |_|\__, |\__|\__|
                            _/ |                      | |        
                           |__/                       |_|        
2021-03-23 08:31:35.889 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-03-23 08:31:38.434 INFO APP: Version: 2.4.0
2021-03-23 08:31:38.437 INFO APP: Application path:/opt
2021-03-23 08:31:38.585 INFO MQTT: MQTT is disabled
2021-03-23 08:31:38.616 INFO ZWAVE: Connecting to /dev/ttyAMA0
2021-03-23 08:31:38.678 INFO APP: Listening on port 44920 host 0.0.0.0 protocol HTTP
[08:31:38] INFO: Starting NGinx...
2021-03-23 08:31:43.883 INFO APP: GET / 200 38.063 ms - 1875
2021-03-23 08:31:43.983 INFO APP: GET /static/js/app.9d761e16bb97b07c691f.js 304 9.590 ms - -
2021-03-23 08:31:44.004 INFO APP: GET /static/css/app.9e03b038c7ace6a5beeb.css 200 17.011 ms - 641157
2021-03-23 08:31:44.283 INFO APP: GET /api/auth-enabled 304 25.077 ms - -
2021-03-23 08:31:44.351 INFO APP: GET /static/logo.png 200 4.368 ms - 10014
2021-03-23 08:31:44.566 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 200 2.863 ms - 82492
2021-03-23 08:31:46.880 INFO APP: GET /api/settings 200 162.530 ms - 739
2021-03-23 08:31:46.972 INFO APP: GET /api/auth-enabled 304 8.908 ms - -
2021-03-23 08:31:59.153 INFO ZWAVE: Calling api startInclusion with args: [ false, [length]: 1 ]
2021-03-23 08:31:59.159 INFO ZWAVE: Zwave client not connected startInclusion { success: false, message: 'Zwave client not connected' }

Problem/Motivation

Everspring SM103 devices no longer show correct state in HA. These are window door sensors who should report open closed status. This used to work prior to recent update about 10-20 days ago.

Expected behavior

Sensor change when door window open and closed on to off etc

Actual behavior

Sensor reports on either on or off on different devices. No change on opening or closing of door.

Can see in debug status that the zwavejs is receiving the data as the level changes from 0 to 99 appropriately on open close but this does not transmit to HA

Rest of devices in zwave report and work as expected. No issues with inclusion or exclusion. I have rebuilt the zwave network from scratch on a different device and with different zwave stick with the same issue. Updated to most recent zwave2mqtt and HA

Steps to reproduce

Use a SM103 in zwave network

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I am trying to use an automation to control config parameters of my Thermostat Valves (Eurotronic Spirit Z-Wave). Config file here:

(https://github.com/zwave-js/node-zwave-js/blob/2a13c7de52b070a0ab0216293169b614d44adf2f/packages/config/config/devices/0x0148/spirit.json#L151-L167)

The appropriate values are integers between -50 and 50 as well as the special code -128.

Expected behavior

The relevant part of my script "Heating: Correct TRV Salon Temp", reduced to the minimum, does the following:

- service: zwave_js.set_config_parameter
      data:
        parameter: "8"
        value: 8
      target:
        device_id: 32ab6dc7b858f9a872df75b8d891bef7

I would then expect to see this value in the zwavejs2mqtt configuration view for the node.

Actual behavior

No parameter is set (nothing in the zwavejs2mqtt log) and an error is generated in the HASS log. I have attempted to wrap the value in quotes etc, but it did not help.

2021-03-08 19:22:14 ERROR (MainThread) [homeassistant.components.automation.correct_trv_salon_temp] Heating: Correct TRV Salon Temp: Error executing script. Unexpected error for call_service at pos 2: 'Value' object has no attribute 'configuration_value_type'
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 262, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 463, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1488, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1523, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/services.py", line 107, in async_set_config_parameter
    zwave_value = await async_set_config_parameter(
  File "/usr/local/lib/python3.8/site-packages/zwave_js_server/util/node.py", line 59, in async_set_config_parameter
    zwave_value.configuration_value_type == ConfigurationValueType.ENUMERATED
AttributeError: 'Value' object has no attribute 'configuration_value_type'
2021-03-08 19:22:14 ERROR (MainThread) [homeassistant.components.automation.correct_trv_salon_temp] While executing automation automation.correct_trv_salon_temp
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/automation/__init__.py", line 412, in async_trigger
    await self.action_script.async_run(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 1041, in async_run
    await asyncio.shield(run.async_run())
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 254, in async_run
    await self._async_step(log_exceptions=False)
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 262, in _async_step
    await getattr(
  File "/usr/src/homeassistant/homeassistant/helpers/script.py", line 463, in _async_call_service_step
    await service_task
  File "/usr/src/homeassistant/homeassistant/core.py", line 1488, in async_call
    task.result()
  File "/usr/src/homeassistant/homeassistant/core.py", line 1523, in _execute_service
    await handler.job.target(service_call)
  File "/usr/src/homeassistant/homeassistant/components/zwave_js/services.py", line 107, in async_set_config_parameter
    zwave_value = await async_set_config_parameter(
  File "/usr/local/lib/python3.8/site-packages/zwave_js_server/util/node.py", line 59, in async_set_config_parameter
    zwave_value.configuration_value_type == ConfigurationValueType.ENUMERATED
AttributeError: 'Value' object has no attribute 'configuration_value_type'

I am running hass.io with core-2021.3.2 and upgraded the add-on to the new version today (0.6.1) with zwavejs2mqtt 2.1.2. There were some issues with v 2.1.0 but those got cleared up with today's version but the problem remains on the HASS side.

Here is a reference to my discussion on the Z2M github. As of today it is possible to set the value for this parameter through the Z2M Web GUI, but I need programmatic control.

zwave-js/zwave-js-ui#806

After update to 0.11.0 I don`t get any status on my nodes(unknown), also manufactor and model is gone.
I see in the log the the nodes are providing info and they are displayed in last active.

Any idea to solve this?

Yale YRD110 Zwave locks are not reporting any additional parameters of the lock event state. Using an event listener for zwave_js_event and also keymaster_lock_state_changed I see the following information:

zwave_js_event:
{
"event_type": "zwave_js_event",
"data": {
"type": "notification",
"domain": "zwave_js",
"node_id": 58,
"home_id": 4172338759,
"device_id": "01bb8f2c1b64539cfc8dbf6b1c188f91",
"label": "RF unlock operation",
"parameters": {}
},
"origin": "LOCAL",
"time_fired": "2021-03-30T22:08:50.643068+00:00",
"context": {
"id": "a8cd0b551a5a6ac98e7f06fc6920f335",
"parent_id": null,
"user_id": null
}
}

keymaster_lock_state_changed:
{
"event_type": "keymaster_lock_state_changed",
"data": {
"notification_source": "entity_state",
"lockname": "garagedoor",
"entity_id": "lock.garage_door",
"state": "locked",
"action_code": 130,
"action_text": "Unknown Alarm Type Value",
"code_slot": 1,
"code_slot_name": "Aaron"
},
"origin": "LOCAL",
"time_fired": "2021-03-30T22:04:43.730096+00:00",
"context": {
"id": "fcc515f6beb3467940f5e77aa4874aff",
"parent_id": null,
"user_id": null
}
}

Do to additional parameters not being captured the "action_text" is left with an unknown value state.

Problem/Motivation

Searching the Home Assistant Add-on Store, I don't see Z-Wave JS to MQTT listed

Expected behavior

I expected to see Z-Wave JS to MQTT listed and installable.

Actual behavior

Z-Wave JS to MQTT is not listed.

Steps to reproduce

Proposed changes

I had it installed before but was having issues controlling a lock. Decided to start from the beginning, uninstalled everything z-wave related and went to re-install but don't see the Z-Wave JS to MQTT in the add on store.

Problem/Motivation

Is there some way of updating to the latest (2.1.1) z2m while running hass.io with this plug in v 0.6.0? There was a patch which would restore the workings of my heating system in that and it's a little bit cold to be waiting here for an official update.

Thanks!

Disconnected one ZWave plug from powers.
First issue: device become Dead after 15+ minutes only. May be it is ok, not sure.
Second issue: when issue turn_on/off commands towards Dead device - errors thrown in log,

• as well as commands towards Alive devices goes very slow - with noticeable delay.
  Third issue: Dead device still active in HA UI - all switches possible to toggle. Thats not good.

zwave_js_server.exceptions.FailedCommand: Command failed: unknown_error
2021-02-27 00:54:04 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [547647517264] Command failed: unknown_error
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 136, in handle_call_service
await hass.services.async_call(
File "/usr/src/homeassistant/homeassistant/core.py", line 1455, in async_call
task.result()
File "/usr/src/homeassistant/homeassistant/core.py", line 1490, in _execute_service
await handler.job.target(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 204, in handle_service
await self.hass.helpers.service.entity_service_call(
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 595, in entity_service_call
future.result() # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 664, in async_request_call
await coro
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 632, in _handle_entity_call
await result
File "/usr/src/homeassistant/homeassistant/components/zwave_js/switch.py", line 64, in async_turn_off
await self.info.node.async_set_value(target_value, False)
File "/usr/local/lib/python3.8/site-packages/zwave_js_server/model/node.py", line 250, in async_set_value
result = await self.client.async_send_command(
File "/usr/local/lib/python3.8/site-packages/zwave_js_server/client.py", line 64, in async_send_command
return await future
zwave_js_server.exceptions.FailedCommand: Command failed: unknown_error

Problem/Motivation

Lost control of Nortek Security & Control LLC Z-Wave Plus Thermostat GoControl GC-TBZ48 Thermostat

Expected behavior

climate.thermostat entity was available and functioning with 0.4.1.

climate.thermostat entity Became unavailable with 0.4.2

Steps to reproduce

update to zwavejs2mqtt 0.4.2 (climate entity disappears). Selective restore 0.4.1 from snapshot (climate entity OK). Note: other entities of thermostat are unaffected. Only the climate integration seems impacted.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

When the HA entity for a relay is actuated, the On/off value for relay 1 is also sent/received. For example, by toggling RLY2, the value for RLY2 changes momentarily, but RLY1 also registers a value change. The physical RLY2 will actuate. but RLY1 does not. This also occurs with RLY3, as RLY1 will also report a state change. In addition, the target value and the current value for the switch & relay will not match the configuration & state when selected within the ZwaveJS2MQTT console.

2021-03-31T19:24:38.622Z CNTRLR [Node 012] Mapping unsolicited report from root device to first supporting end point #1 2021-03-31 15:24:38.624 INFO ZWAVE: Node 12: value updated: 37-1-currentValue false => true 2021-03-31 15:24:38.633 INFO ZWAVE: Node 12: value updated: 37-2-currentValue true => true 2021-03-31 15:24:39.625 INFO ZWAVE: Node 12: value updated: 37-2-currentValue true => false 2021-03-31 15:24:56.275 INFO ZWAVE: Node 12: value updated: 37-1-currentValue true => false 2021-03-31T19:24:56.374Z CNTRLR [Node 012] Mapping unsolicited report from root device to first supporting end point #1 2021-03-31 15:24:56.380 INFO ZWAVE: Node 12: value updated: 37-1-currentValue false => true 2021-03-31 15:24:56.392 INFO ZWAVE: Node 12: value updated: 37-1-currentValue true => false 2021-03-31 15:24:57.335 INFO ZWAVE: Node 12: value updated: 37-1-currentValue false => false

Expected behavior

RLY1 will not have a value sent/received when RLY2 or RLY3 are actuated by HA/ZwaveJS2MQTT. RLY2 or RLY3 will show within HA the actual state of relay when configuration for switch set to "Toggle Switch."

Actual behavior

All relays configured as toggle switches -> relay to follow switch position.

Within HA entity:

RLY2 toggled on -> value for both RLY2 & RLY1 switched from "off->on" then toggle within HA for RLY2 will show "off" At that point, RLY2 needs to be re-toggled to move relay again.

Steps to reproduce

See above

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

During the boot of the container, I notice that scenes.json and git are not found.
There was also a second json not found, but it seems to have created this somewhere along the road... Unclear if that’s the intention for scenes.json as well.

[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] configuration.sh: executing... 
[cont-init.d] configuration.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[11:24:05] INFO: Starting the Z-Wave JS to MQTT...
 ______                       _     ___                  _   _   
|___  /                      (_)   |__ \                | | | |  
   / /_      ____ ___   _____ _ ___   ) |_ __ ___   __ _| |_| |_ 
  / /\ \ /\ / / _` \ \ / / _ \ / __| / /| '_ ` _ \ / _` | __| __|
 / /__\ V  V / (_| |\ V /  __/ \__ \/ /_| | | | | | (_| | |_| |_ 
/_____|\_/\_/ \__,_| \_/ \___| |___/____|_| |_| |_|\__, |\__|\__|
                            _/ |                      | |        
                           |__/                       |_|        
2021-01-31 11:24:07.098 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-01-31 11:24:13.760 INFO APP: Version: 1.0.1
2021-01-31 11:24:13.763 INFO APP: Application path:/opt
2021-01-31 11:24:13.955 INFO MQTT: MQTT is disabled
2021-01-31 11:24:13.993 INFO ZWAVE: Connecting to /dev/serial/by-id/usb-xxxx_xxxx-if00
2021-01-31 11:24:14.074 INFO APP: Listening on port 44920
[11:24:14] INFO: Starting NGinx...
2021-01-31 11:24:14.196 INFO ZWAVE-SERVER: ZwaveJS server listening on port 3000

Expected behavior

Boots with no problems

Actual behavior

2021-01-31 11:24:07.098 WARN STORE: scenes.json not found /bin/sh: git: not found

Steps to reproduce

Install the add-on, start the add-on

Proposed changes

?

Problem/Motivation

Ever since upgrading to v0.9.1, my garage tilt sensors are failing to log events.

Expected behavior

Expect tilt sensors to register open/close (on/off) as normal.

Actual behavior

No recognition of events. I've tested/changed batteries, manually triggered tilt changes, etc.

Steps to reproduce

Are other tilt sensors working? Mine are "Vision Security" ZG8101 (bought from Monoprice). They've always worked fine, including since moving to Z-Wave JS (and I've always used zwavejs2mqtt since making the switch).

Proposed changes

This is where my knowledge ends... I have no idea why they're not working anymore or how to get them back. Unfortunately, I chose not to backup the prior version of the addon when I upgraded to v0.9.1... I know, I know... this will teach me!

Problem/Motivation

more readable interface

Expected behavior

Two colums layout in User Code panel

Actual behavior

Three columns layout

Steps to reproduce

Just go to a lock and ask to see User codes

Proposed changes

User Codes are seen as pair Status/Code, but the layout is three columns. Wouldn't it be easier to read pairs in two columns layout, or at least to have a local menu enabling to have a two column layout.

Problem/Motivation

Abnormal status for unavailable/dead Z-Wave device.

Expected behavior

Z-Wave Dead devices MUST become with Status = Unavailable in HA and still visible in dashboards etc., just grayed.

Actual behavior

Dead device disappear from dashboards, despite still Available in Entities list.

Steps to reproduce

Just disconnect power from Z-Wave device and wait.

Proposed changes

While powered:

Device powered off:

Entity status is NOT unavailable - see column status:

Thats how it mast be: status = Unavailable, no message in entity card.

Problem/Motivation

After updating to 0.4.0, I see the following error in the logs:

INFO: Starting NGinx...
nginx: [emerg] invalid number of arguments in "proxy_set_header" directive in /etc/nginx/servers/ingress.conf:12

I don't think that the server is able to start up properly as a result

Expected behavior

No errors, everything starts up cleanly

Actual behavior

See description

Steps to reproduce

Update to 0.4.0 and try running the container

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

As no need for me in MQTT functionaltity right now, decided to switch it off.
Right after that - devices become Dead, no recover back.

2021-03-04 15:00:57 ERROR (MainThread) [homeassistant.components.zwave_js] Failed to connect: Cannot connect to host a0d7b954-zwavejs2mqtt:3000 ssl:default [Connect call failed ('172.30.33.2', 3000)]
2021-03-04 15:00:57 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Z-Wave JS' for zwave_js integration not ready yet. Retrying in background

After enabling MQTT gateway back - still all network Dead, only Aeotec stick is alive.
No other changes done in HA/ & add-on config, AFAIK.

Expected behavior

MQTT gateway enable/disable must not have any effect on Z-Wave network, IMHO.

Actual behavior

All devices Dead.

Steps to reproduce

Disable MQTT gateway.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

After restart the non-battery powered devices can not be interviewed.

Expected behavior

Every device should be interviewed.

Actual behavior

Only the battery powered devices show up on the UI.
So the manufacturer, the product and product code fields are empty, and these devices /and related entities/ are unavailable, on HA side.

Steps to reproduce

Restart the add-on.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Is it appropriate to request we bump the version of the underlying project? I'm unsure of the best way to make this inquiry, I didn't want to simply submit a pull request. If there's some other processes working on this, just ignore me.

Proposed changes

Bump the dockerfile to use the latest zwavejs2mqtt v1.4.0 release.

Hello,

I use home assistant OS without any add-on except zwavejs2mqtt which is in the latest version and the z-wave js integration that goes with it. However my C421 home MCO switches are not considered a multilevel switch (I think). I can still move them up and down I don't really know how but it works. On the other hand, it is impossible for me to do the STOP / PAUSE action ...

If you need a log please let me know where they are so I can send them to you. If I need an additional add on to retrieve these logs let me know

This is an issue that had already been addressed and corrected by adding a force multilevel switch for my device. When I did not yet have the add-on version it was good the force multievel switch worked but there it does not seem to work or badly ...
I noticed that if the module was in an unknown state everything was working in the management of the multilevel switch however when it is added correctly this is no longer the case and the stop button no longer works ...

I won't go into details because I don't really know how it works.

Hope we can solve this problem.

Thank you in advance

Edit, I have open the same problem in this URL : zwave-js/node-zwave-js#2454

mcohome fancoil climate entity is unavailable after latest update.
Although temprature sensor is running

Problem/Motivation

To fix duplicate mapping for ZEN16 Multirelay. See zwave-js/node-zwave-js#1748 (comment)

Expected behavior

RLY1, RLY2, RLY3 all should map separately in current value on Zen16 Multirelay.

Actual behavior

RLY1 duplicates the mapping on RLY2 & RLY3.

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

Update ZwaveJS to v7.0.1 per issue here: zwave-js/node-zwave-js#2160

Problem/Motivation

Number of UNKNOWN / unavailable entities grows.

Expected behavior

As device functionality remains same - same amount of entities will stay.

Actual behavior

IMHO on every "Interview" more UNKNOWN entries appears in device Meter section.
As well new unavailable entities appears in HA through integration.

Steps to reproduce

Restart add-on.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

2021-03-04 15:15:14.848 INFO ZWAVE: Node 2: metadata updated: 112-0-1
2021-03-04 15:15:14.852 INFO ZWAVE: Node 2: metadata updated: 112-0-2
2021-03-04 15:15:14.870 INFO ZWAVE: Node 2: metadata updated: 112-0-3
2021-03-04 15:15:14.886 INFO ZWAVE: Node 2: metadata updated: 112-0-4
2021-03-04 15:15:14.890 INFO ZWAVE: Node 2: metadata updated: 112-0-5
2021-03-04 15:15:14.892 INFO ZWAVE: Node 2: metadata updated: 112-0-6
2021-03-04 15:15:14.894 INFO ZWAVE: Node 2: metadata updated: 112-0-7
2021-03-04 15:15:14.896 INFO ZWAVE: Node 2: metadata updated: 112-0-8
2021-03-04 15:15:14.899 INFO ZWAVE: Node 2: metadata updated: 112-0-9
2021-03-04 15:15:14.901 INFO ZWAVE: Node 2: metadata updated: 112-0-10
2021-03-04 15:15:14.963 INFO ZWAVE: Node 3: value updated: 50-0-value-66817 0 => 0
2021-03-04 15:15:14.969 INFO ZWAVE: Node 3: value updated: 50-0-previousValue-66817 0 => 0
2021-03-04 15:15:14.971 INFO ZWAVE: Node 3: value updated: 50-0-deltaTime-66817 43 => 24
2021-03-04 15:15:15.072 INFO ZWAVE: Node 3: metadata updated: 112-0-1
2021-03-04 15:15:15.075 INFO ZWAVE: Node 3: metadata updated: 112-0-2
2021-03-04 15:15:15.089 INFO ZWAVE: Node 3: metadata updated: 112-0-3
2021-03-04 15:15:15.102 INFO ZWAVE: Node 3: metadata updated: 112-0-4
2021-03-04 15:15:15.105 INFO ZWAVE: Node 3: metadata updated: 112-0-5
2021-03-04 15:15:15.107 INFO ZWAVE: Node 3: metadata updated: 112-0-6
2021-03-04 15:15:15.110 INFO ZWAVE: Node 3: metadata updated: 112-0-7
2021-03-04 15:15:15.112 INFO ZWAVE: Node 3: metadata updated: 112-0-8
2021-03-04 15:15:15.115 INFO ZWAVE: Node 3: metadata updated: 112-0-9
2021-03-04 15:15:15.118 INFO ZWAVE: Node 3: metadata updated: 112-0-10
2021-03-04 15:15:15.145 INFO ZWAVE: Node 2: value updated: 112-0-1 1 => 1
2021-03-04 15:15:15.356 INFO ZWAVE: Node 3: value updated: 112-0-1 1 => 1
2021-03-04 15:15:15.482 INFO ZWAVE: Node 2: value updated: 112-0-2 1 => 1
2021-03-04 15:15:15.656 INFO ZWAVE: Node 3: value updated: 112-0-2 1 => 1
2021-03-04 15:15:15.769 INFO ZWAVE: Node 2: value updated: 112-0-3 1 => 1
2021-03-04 15:15:15.975 INFO ZWAVE: Node 3: value updated: 112-0-3 1 => 1
2021-03-04 15:15:16.081 INFO ZWAVE: Node 2: value updated: 112-0-4 0 => 0
2021-03-04 15:15:16.255 INFO ZWAVE: Node 3: value updated: 112-0-4 0 => 0
2021-03-04 15:15:16.360 INFO ZWAVE: Node 2: value updated: 112-0-5 120 => 120
2021-03-04 15:15:16.526 INFO ZWAVE: Node 3: value updated: 112-0-5 120 => 120
2021-03-04 15:15:16.640 INFO ZWAVE: Node 2: value updated: 112-0-6 1 => 1
2021-03-04 15:15:16.815 INFO ZWAVE: Node 3: value updated: 112-0-6 1 => 1
2021-03-04 15:15:16.929 INFO ZWAVE: Node 2: value updated: 112-0-7 300 => 300
2021-03-04 15:15:17.096 INFO ZWAVE: Node 3: value updated: 112-0-7 300 => 300
2021-03-04 15:15:17.210 INFO ZWAVE: Node 2: value updated: 112-0-8 16 => 16
2021-03-04 15:15:17.379 INFO ZWAVE: Node 3: value updated: 112-0-8 16 => 16
2021-03-04 15:15:17.510 INFO ZWAVE: Node 2: value updated: 112-0-9 50 => 50
2021-03-04 15:15:17.687 INFO ZWAVE: Node 3: value updated: 112-0-9 50 => 50
2021-03-04 15:15:17.780 INFO ZWAVE: Node 2: value updated: 112-0-10 13 => 13
2021-03-04 15:15:17.946 INFO ZWAVE: Node 3: value updated: 112-0-10 13 => 13
2021-03-04 15:15:18.527 INFO ZWAVE: Node 2: interview completed, all values are updated
2021-03-04 15:15:18.676 INFO ZWAVE: Node 3: interview completed, all values are updated
2021-03-04 15:17:05.237 INFO APP: GET /health/zwave 200 4.050 ms - 1875
2021-03-04 15:17:39.765 INFO ZWAVE: Node 2: value updated: 50-0-value-65537 -21474826.26 => -21474826.26
2021-03-04 15:17:39.771 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-65537 -21474826.26 => -21474826.26
2021-03-04 15:17:39.775 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-65537 155 => 147
2021-03-04 15:17:39.791 INFO ZWAVE: Node 2: value updated: 50-0-value-66049 0 => 0
2021-03-04 15:17:39.795 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66049 0 => 0
2021-03-04 15:17:39.799 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66049 155 => 147
2021-03-04 15:17:39.821 INFO ZWAVE: Node 2: value updated: 50-0-value-66561 0 => 0
2021-03-04 15:17:39.825 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66561 0 => 0
2021-03-04 15:17:39.828 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66561 155 => 147
2021-03-04 15:17:39.851 INFO ZWAVE: Node 2: value updated: 50-0-value-66817 0 => 0
2021-03-04 15:17:39.854 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66817 0 => 0
2021-03-04 15:17:39.858 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66817 155 => 147
2021-03-04 15:18:28.850 INFO APP: GET /api/settings 200 99.401 ms - 23668
2021-03-04 15:18:28.958 INFO APP: GET /api/auth-enabled 304 5.570 ms - -
2021-03-04 15:18:35.678 INFO ZWAVE: Node 3: value updated: 37-0-currentValue false => true
2021-03-04 15:18:35.746 INFO ZWAVE: Node 3: value updated: 37-0-currentValue true => true
2021-03-04 15:18:36.639 INFO ZWAVE: Node 3: value updated: 37-0-currentValue true => false
2021-03-04 15:18:36.705 INFO ZWAVE: Node 3: value updated: 37-0-currentValue false => false
2021-03-04 15:18:37.019 INFO ZWAVE: Node 3: value updated: 37-0-currentValue false => false
2021-03-04 15:18:37.487 INFO ZWAVE: Node 2: value updated: 37-0-currentValue false => true
2021-03-04 15:18:37.502 INFO ZWAVE: Node 2: value updated: 37-0-currentValue true => true
2021-03-04 15:18:38.557 INFO ZWAVE: Node 2: value updated: 37-0-currentValue true => true
2021-03-04 15:18:38.929 INFO ZWAVE: Node 2: value updated: 37-0-currentValue true => false
2021-03-04 15:18:38.943 INFO ZWAVE: Node 2: value updated: 37-0-currentValue false => false
2021-03-04 15:18:40.014 INFO ZWAVE: Node 2: value updated: 37-0-currentValue false => false
2021-03-04 15:18:40.847 INFO ZWAVE: Node 3: value updated: 50-0-value-65537 0 => 0
2021-03-04 15:18:40.851 INFO ZWAVE: Node 3: value updated: 50-0-previousValue-65537 0 => 0
2021-03-04 15:18:40.856 INFO ZWAVE: Node 3: value updated: 50-0-deltaTime-65537 24 => 208
2021-03-04 15:18:40.910 INFO ZWAVE: Node 3: value updated: 50-0-value-66049 0 => 0
2021-03-04 15:18:40.913 INFO ZWAVE: Node 3: value updated: 50-0-previousValue-66049 0 => 0
2021-03-04 15:18:40.917 INFO ZWAVE: Node 3: value updated: 50-0-deltaTime-66049 24 => 208
2021-03-04 15:18:41.016 INFO ZWAVE: Node 3: value updated: 50-0-value-66561 0 => 0
2021-03-04 15:18:41.019 INFO ZWAVE: Node 3: value updated: 50-0-previousValue-66561 0 => 0
2021-03-04 15:18:41.025 INFO ZWAVE: Node 3: value updated: 50-0-deltaTime-66561 24 => 208
2021-03-04 15:18:41.084 INFO ZWAVE: Node 3: value updated: 50-0-value-66817 0 => 0
2021-03-04 15:18:41.087 INFO ZWAVE: Node 3: value updated: 50-0-previousValue-66817 0 => 0
2021-03-04 15:18:41.091 INFO ZWAVE: Node 3: value updated: 50-0-deltaTime-66817 24 => 208
2021-03-04 15:18:42.059 INFO ZWAVE: Node 2: value updated: 37-0-currentValue false => true
2021-03-04 15:18:42.071 INFO ZWAVE: Node 2: value updated: 37-0-currentValue true => true
2021-03-04 15:18:43.127 INFO ZWAVE: Node 2: value updated: 37-0-currentValue true => true
2021-03-04 15:18:46.883 INFO ZWAVE: Node 2: value updated: 50-0-value-65537 -21474826.26 => -21474826.26
2021-03-04 15:18:46.887 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-65537 -21474826.26 => -21474826.26
2021-03-04 15:18:46.892 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-65537 147 => 68
2021-03-04 15:18:46.912 INFO ZWAVE: Node 2: value updated: 50-0-value-66049 0 => 0
2021-03-04 15:18:46.915 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66049 0 => 0
2021-03-04 15:18:46.919 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66049 147 => 68
2021-03-04 15:18:46.942 INFO ZWAVE: Node 2: value updated: 50-0-value-66561 0 => 239.3
2021-03-04 15:18:46.945 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66561 0 => 0
2021-03-04 15:18:46.950 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66561 147 => 68
2021-03-04 15:18:46.972 INFO ZWAVE: Node 2: value updated: 50-0-value-66817 0 => 0
2021-03-04 15:18:46.975 INFO ZWAVE: Node 2: value updated: 50-0-previousValue-66817 0 => 0
2021-03-04 15:18:46.979 INFO ZWAVE: Node 2: value updated: 50-0-deltaTime-66817 147 => 68
2021-03-04 15:19:05.257 INFO APP: GET /health/zwave 200 3.330 ms - 1875
2021-03-04 15:21:05.271 INFO APP: GET /health/zwave 200 2.790 ms - 1875

Problem/Motivation

Firmware update doesn't work using the addon-zwavejs2mqtt.

Expected behavior

Firmware update should work properly using addon-zwavejs2mqtt.

Actual behavior

Whenever "Begin firmware update" node action is selected, after you select the firmware file and the file has to be sent to zwavejs2mqtt, the following error can be seen in logs:

2021/02/19 16:37:38 [error] 418#418: *2061 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-zwavejs2mqtt, request: "POST /socket.io/?EIO=4&transport=polling&t=NUwkOdc&sid=XCa3GYmkbC7UkAYzAAAI HTTP/1.1", upstream: "http://127.0.0.1:44920/socket.io/?EIO=4&transport=polling&t=NUwkOdc&sid=XCa3GYmkbC7UkAYzAAAI", host: "10.10.111.4:8124", referrer: "https://10.10.111.4:8124/api/hassio_ingress/HF_cM1Ef8ZQhxN1KonodqGhXcHda5DE6tScRqD_P11o/control-panel"
If you expose the container port and use it directly (eg: 10.10.111.4:44920), the firmware update works without any problem, so it's not a problem with zwavejs2mqtt itself.

Steps to reproduce

1. Open zwavejs2mqtt web ui.
2. Select a device.
3. On Node actions selectbox, choose "Begin firmware update"
4. Click ok and select the firmware file.
5. Check the addon logs, you will see the error desribed above.

Proposed changes

Most probably, there's something missing or wrong in the ingress configuration (nginx) since accessing the container directly works as expected.

As a workaround, you can connect to zwavejs2mqtt container, install SSH on it, then use SSH to expose the port to the host and access zwavejs2mqtt directly (where 10.10.111.4 is the host IP address and 172.30.33.2 is the container IP address):
Eg. ssh -NfL 10.10.111.4:44920:0.0.0.0:44920 [email protected]

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Some of my ZMNHJD devices have a multilevel sensor reported (air temperature) and some not.
When I was with OpenZWave, all my devices worked fine, the temperature entities were reported as well (although I don't use it because I don't have a probe).

I removed and reinstalled many times ZWaveJS2MQTT and it's not always the same devices that have this sensor missing, but always 2 of them (I have 5 devices, so 3 are working fine). I did a re-interview many time.

Also this devices, that had the temperature sensor missing, don't work because I'm unable to control the multilevel switch to change the heater mode (eco, comfort, etc).

Expected behavior

Have the multilevel sensor reported on ALL devices and able to control the multilevel switch to change the heater mode.

Is this the right place about this type of issue ?

Problem/Motivation

I recently went from OZW to Zwave JS with the official add-on. Had the devices there but was having intermittent issues with my automations with my Leviton switches work some times but not others. So I deinstalled the official add one and installed the mqtt2zwave add-on.

After doing this, my Leviton switches, one is a "Leviton - DZ15S - Scene Capable Push On/Off" the other is a dimmer. Both went to a dead status. So after many exclusions and inclusions where the switches would be added in but would always show as unknown. Also, attempted healing the network many times. In the end I did a factory reset on my AEON z-stick and added my motion sensor back in and then tried to add the DZ15S back in which resulted in the same result. Many reboots were done as well.

nodes.json_before_readding.txt

It won't let me upload the new, it says it is empty.

Expected behavior

I would expect after an inclusion that the devices would be recognized. Interviews always return with:

Actual behavior

2021-04-09 20:49:16.684 INFO ZWAVE: Node 4: interview stage COMMANDCLASSES completed
2021-04-09 20:49:16.694 INFO ZWAVE: Node 4: interview stage OVERWRITECONFIG completed
2021-04-09 20:49:16.751 INFO ZWAVE: Node 4: interview stage NEIGHBORS completed
2021-04-09 20:49:16.754 INFO ZWAVE: Node 4: interview stage COMPLETE completed
2021-04-09 20:49:16.780 INFO ZWAVE: Node 4: value added 4-37-0-currentValue => undefined
2021-04-09 20:49:16.784 INFO ZWAVE: Node 4: value added 4-37-0-targetValue => undefined
2021-04-09 20:49:16.787 INFO ZWAVE: Node 4: value added 4-134-0-libraryType => undefined
2021-04-09 20:49:16.790 INFO ZWAVE: Node 4: value added 4-134-0-protocolVersion => undefined
2021-04-09 20:49:16.793 INFO ZWAVE: Node 4: value added 4-134-0-firmwareVersions => undefined
2021-04-09 20:49:16.795 INFO ZWAVE: Node 4: value added 4-114-0-manufacturerId => undefined
2021-04-09 20:49:16.804 INFO ZWAVE: Node 4: value added 4-114-0-productType => undefined
2021-04-09 20:49:16.807 INFO ZWAVE: Node 4: value added 4-114-0-productId => undefined
2021-04-09 20:49:16.809 INFO ZWAVE: Node 4: value added 4-43-0-sceneId => undefined
2021-04-09 20:49:16.813 INFO ZWAVE: Node 4: value added 4-43-0-dimmingDuration => undefined
2021-04-09 20:49:16.819 INFO ZWAVE: Node 4 ready: Unknown manufacturer 0xXXXX - Unknown product 0xXXXX (0xXXXX)
2021-04-09 20:49:16.822 INFO ZWAVE: Controller status: Scan completed
2021-04-09 20:49:16.825 INFO ZWAVE: Network scan complete. Found: 3 nodes
2021-04-09 20:49:16.849 INFO ZWAVE: Node 4: interview COMPLETED, all values are updated
2021-04-09 20:49:22.909 INFO APP: GET /health/zwave 200 6.197 ms - 1875
2021-04-09 20:50:18.515 INFO APP: GET /api/store 200 32.056 ms - 735

I am now seeing:

2021-04-09 20:50:18.515 INFO APP: GET /api/store 200 32.056 ms - 735
Error: Not Found
at /opt/app.js:979:15
at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13)
at /opt/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12)
at next (/opt/node_modules/express/lib/router/index.js:275:10)
at /opt/node_modules/express-session/index.js:502:7
at readCallback (/opt/node_modules/session-file-store/lib/session-file-helpers.js:193:20)
at /opt/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)
2021-04-09 20:50:24.258 INFO APP: GET /api/store//data/store/settings.json 404 25.652 ms - 136
2021-04-09 20:51:22.940 INFO APP: GET /health/zwave 200 5.265 ms - 1875
Error: Not Found
at /opt/app.js:979:15
at Layer.handle [as handle_request] (/opt/node_modules/express/lib/router/layer.js:95:5)
at trim_prefix (/opt/node_modules/express/lib/router/index.js:317:13)
at /opt/node_modules/express/lib/router/index.js:284:7
at Function.process_params (/opt/node_modules/express/lib/router/index.js:335:12)
at next (/opt/node_modules/express/lib/router/index.js:275:10)
at /opt/node_modules/express-session/index.js:502:7
at readCallback (/opt/node_modules/session-file-store/lib/session-file-helpers.js:193:20)
at /opt/node_modules/graceful-fs/graceful-fs.js:123:16
at FSReqCallback.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:63:3)

I looked at the file in the "Store" area and it is there but does not look like it is in good shape. I downloaded it and will include.

I did not have this error until I did an exclude where the node was node 3. I excluded and included the node and it is now it is node 4.

Steps to reproduce

Not sure, at this point not sure how to get the nodes.js fixed. I do have a backup from when the Leviton switch was node 3.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

I've been noticing this error in my Supervisor logs now and then:
21-02-03 07:58:19 ERROR (MainThread) [supervisor.api.ingress] Ingress error: 400, message='Invalid response status', url=URL('http://172.30.33.2:8099/socket.io/?EIO=4&transport=websocket&sid=_xxxxxxxxxxxxxxxx')

The IP address is that of addon_a0d7b954_zwavejs2mqtt and this happens every time I open the "ZWave JS" panel /web interface.
I'm not sure if this is an issue or not to be honest. I just wanted to report it to confirm.

Expected behavior

Unclear

Actual behavior

Shows error. Unclear if it retries and is successful or...

Steps to reproduce

Unclear

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

Problem/Motivation

Post upgrade to 2021.4.x all scene notifications from zwavejs2mgttt stop showing up in HA. I was checking zwave_js_event in HA for these changes. I have read some breaking changes notes that imply this service should have changed. I have reinstalled both zwavejs2mqtt and the HA zwaveJS integration but after clean installs and reboots of both of these the only service I see associated to zwave in the developer tools -> events tab is zwave_js_event.

When watching log for zwavejs2mqtt debug logs I can see the scene being triggered

2021-04-18 09:22:29.875 INFO ZWAVE: Node 31: value notification: 91-0-scene-003 0 2021-04-18T14:22:29.878Z CNTRLR « [Node 031] received CentralScene notification { "nodeId": 31, "ccId": "Central Scene", "ccCommand": "0x03", "payload": "0xa48003" }

but when watching the zwave_js_event in the developer tools -> events tab no events are received.

I have two HA systems with a certain USB dongle in them. They both use this path:

by_id: /dev/serial/by-id/usb-0658_0200-if00

Note the final - (dash) is not an _ (underscore). In the addon notes for zwavejs2mqtt, in Setting up the Home Assistant Z-Wave JS integration, 3. Enter ... , Serial Port (eg ...) the path is given as:

/dev/serial/by-id/usb-0658_0200_if00

In the unlikely cough event that someone simply copy and pastes the above they will get an error. It took me a while to spot why 8)

Problem/Motivation

Selecting ADD/REMOVE DEVICE and Inclusion from Z-Wave JS WEB UI ends up in UI error message "Error while calling api startInclusion: Zwave client not connected"

Expected behavior

Ability to add devices

Actual behavior

Error message

Steps to reproduce

System: Home Assistant OS 5.11 (armv7 / raspberrypi4)
Log settings in ZWaveJS2MQTT UI:
General: Log enabled, Log Level: Silly
Zwave: Log enabled, Log Level: Silly
Disable MQTT Gateway -option enabled

2021-02-19 09:32:24.486 WARN STORE: scenes.json not found
2021-02-19 09:32:24.496 WARN STORE: nodes.json not found
/bin/sh: git: not found
2021-02-19 09:32:28.256 INFO APP: Version: 1.1.1
2021-02-19 09:32:28.258 INFO APP: Application path:/opt
2021-02-19 09:32:28.351 INFO MQTT: MQTT is disabled
2021-02-19 09:32:28.382 INFO ZWAVE: Connecting to /dev/ttyAMA0
09:32:28.385 DRIVER ███████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ███████╗ ██╗ ███████╗
╚══███╔╝ ██║ ██║ ██╔══██╗ ██║ ██║ ██╔════╝ ██║ ██╔════╝
███╔╝ ██║ █╗ ██║ ███████║ ██║ ██║ █████╗ █████╗ ██║ ███████╗
███╔╝ ██║███╗██║ ██╔══██║ ╚██╗ ██╔╝ ██╔══╝ ╚════╝ ██ ██║ ╚════██║
███████╗ ╚███╔███╔╝ ██║ ██║ ╚████╔╝ ███████╗ ╚█████╔╝ ███████║
╚══════╝ ╚══╝╚══╝ ╚═╝ ╚═╝ ╚═══╝ ╚══════╝ ╚════╝ ╚══════╝
09:32:28.388 DRIVER version 6.2.0
09:32:28.390 DRIVER
09:32:28.390 DRIVER starting driver...
09:32:28.430 DRIVER opening serial port /dev/ttyAMA0
2021-02-19 09:32:28.448 INFO APP: Listening on port 44920
09:32:28.482 DRIVER serial port opened
09:32:28.487 SERIAL » [NAK] (0x15)
2021-02-19 09:32:28.503 INFO ZWAVE-SERVER: ZwaveJS server listening on port 3000
[09:32:38] INFO: Successfully send discovery information to Home Assistant.
2021-02-19 09:35:53.523 INFO APP: GET / 200 65.269 ms - 1875
2021-02-19 09:35:53.681 INFO APP: GET /static/css/app.fdb61245954270e06feb.css 200 19.610 ms - 640650
2021-02-19 09:35:53.722 INFO APP: GET /static/js/app.30b0f469d1365694e17a.js 200 10.557 ms - 1686076
2021-02-19 09:35:54.773 INFO APP: GET /static/logo.png 200 4.740 ms - 10014
2021-02-19 09:35:54.847 DEBUG SOCKET: New connection A-fEeT5IfyAKGqOFAAAB
2021-02-19 09:35:54.886 INFO APP: GET /static/fonts/MaterialIcons-Regular.fa3334f.woff2 200 10.050 ms - 82492
2021-02-19 09:35:54.900 DEBUG SOCKET: Event INITED emitted to A-fEeT5IfyAKGqOFAAAB
2021-02-19 09:36:02.074 DEBUG SOCKET: Event ZWAVE_API emitted to A-fEeT5IfyAKGqOFAAAB
2021-02-19 09:36:02.088 INFO ZWAVE: Calling api startInclusion with args: [ false, [length]: 1 ]
2021-02-19 09:36:02.091 INFO ZWAVE: Zwave client not connected startInclusion { success: false, message: 'Zwave client not connected' }
2021-02-19 09:36:18.693 DEBUG SOCKET: User disconnected A-fEeT5IfyAKGqOFAAAB

Proposed changes

N/A

Can't seem to get it to work. I did also try the official add-on "Z-Wave JS" and although no UI, it was able to see my devices. I removed that and installed this one but keep getting this error.

Complete log output: https://pastebin.com/Ci2QuEB6

My hardware:

serial:
  - /dev/ttyUSB0
  - >-
    /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_81300EB9-if00-port0
  - /dev/ttyUSB1
  - >-
    /dev/serial/by-id/usb-Silicon_Labs_HubZ_Smart_Home_Controller_81300EB9-if01-port0

The official add-on used /dev/ttyUSB0. I tried that and the full /dev/serial/by-id/.....
I don't have any secure devices but I was still able to get the network key from my HA .storage/core.config_entries file.