If you search for zcombo in the forums you will find some posts where people mention pulling the battery tray and pressing button while it interviews. I suggest bringing up the log while doing so and repeatedly holding button in while inserting tray. You will see in log when it goes to sleep and pull the tray again… after a couple tries it should say interview complete.
Thanks for the suggestion, but I don’t believe that addresses the problem. I have had no difficulty with adding the Zcombo to my network.
The problem is that after z-wave js add-on 0.1.10 (0.1.12 and 0.1.13), updating the add-on causes some battery devices to show entities unavailable. Does that mean everytime I update the add-on I will have to wake all my battery devices? This seems like a bug to me. Note that the problem occurs with some, but not all battery devices. Simply updating the add-on should not require me to wake up or add/exclude devices to make them work.
Have you waited for them to report information? Whenever you restart home assistant, entities without a state will be unavailable until they update from the sensor. Every single integration works this way with the exception of a few, namely MQTT and helpers.
Yes I have waited as long as 24 hours. On updating from add-on 0.1.10, it appears that information about the network is being lost. I’ve tried stopping and starting the add-on, reloading HA, etc. When I reload 0.1.10 from a snapshot, everything works fine (all entities show up). Nothing else seems to work. I am trying to not go through the process of waking up battery devices or including and excluding nodes every time an update to the add-on occurs.
What’s in your logs? Also please make sure to use the forum correctly. When replying to a person, use the following reply button so they get a notification:
1 Like
Anyone know why we can’t set the Inovelli switches with the configuration values from this site anymore?
LINK
It looks like I have to set each bitmask individually for Parameter 16 now unless I’m missing something? This just changed in the last week or so, or at least I just noticed that my notifications no longer work using something like this:
service: zwave_js.set_config_parameter
data:
value: '67046058'
parameter: '16'
target:
entity_id: light.porch_lights
With that I get the error:
Failed to call service zwave_js/set_config_parameter. Configuration values of undefined type can’t be set
Thanks Petro! Gee I thought no one cared. Sorry for my ineptitude using the forum tools.
Here’s what works:
Here is what the integration shows for the problematic node under add-on 0.1.10:
Here is what the log shows:
12:20:41.182 CNTRLR [Node 018] trying to load device config
12:20:41.188 CNTRLR [Node 018] device config loaded
Updating the add-on to 0.1.13 gives the following:
And here are the node entities. Note that they are greyed out and show as unavailable:
This condition is not resolved by restarting HA crore or the add-on, or letting the system run for over 24 hours.
Here is what the add-on log shows:
12:36:26.823 CNTRLR [Node 018] device config loaded
12:36:26.824 CNTRLR [Node 018] BatteryCC: doing a partial interview...
12:36:26.825 CNTRLR » [Node 018] querying battery status...
Reloading a snapshot of 0.1.10 results in normal behavior.
can you provide dumps for both .10 and .13?
Not sure what you are asking for. While I’ve used HA for a long time, I haven’t dived very deep under the hood.
Here is the dump for add-on 0.1.10:
{
"nodeId": 18,
"index": 0,
"status": 1,
"ready": true,
"deviceClass": {
"basic": {
"key": 4,
"label": "Routing Slave"
},
"generic": {
"key": 161,
"label": "Alarm Sensor"
},
"specific": {
"key": 0,
"label": "Unused"
},
"mandatorySupportedCCs": [
32
],
"mandatoryControlledCCs": []
},
"isListening": false,
"isFrequentListening": false,
"isRouting": true,
"maxBaudRate": 40000,
"isSecure": false,
"version": 4,
"isBeaming": true,
"manufacturerId": 312,
"productId": 2,
"productType": 1,
"firmwareVersion": "0.5",
"deviceConfig": {
"filename": "/usr/lib/node_modules/zwave-js/node_modules/@zwave-js/config/config/devices/0x0138/zcombo.json",
"manufacturerId": 312,
"manufacturer": "BRK Brands, Inc.",
"label": "ZCOMBO",
"description": "Smoke and Carbon Monoxide Alarm",
"devices": [
{
"productType": "0x0001",
"productId": "0x0002"
},
{
"productType": "0x000c",
"productId": "0x0001"
}
],
"firmwareVersion": {
"min": "0.0",
"max": "255.255"
},
"associations": {},
"paramInformation": {
"_map": {}
}
},
"label": "ZCOMBO",
"neighbors": [
1,
16,
2
],
"interviewAttempts": 1,
"interviewStage": 3,
"commandClasses": [
{
"id": 112,
"name": "Configuration",
"version": 1,
"isSecure": false
},
{
"id": 113,
"name": "Notification",
"version": 1,
"isSecure": false
},
{
"id": 114,
"name": "Manufacturer Specific",
"version": 1,
"isSecure": false
},
{
"id": 128,
"name": "Battery",
"version": 1,
"isSecure": false
},
{
"id": 133,
"name": "Association",
"version": 1,
"isSecure": false
},
{
"id": 134,
"name": "Version",
"version": 1,
"isSecure": false
}
],
"endpoints": [
{
"nodeId": 18,
"index": 0
}
],
"values": [
{
"endpoint": 0,
"commandClass": 112,
"commandClassName": "Configuration",
"property": 1,
"propertyName": "Send double alarms",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": true,
"valueSize": 1,
"min": 0,
"max": 255,
"default": 0,
"format": 1,
"allowManualEntry": false,
"states": {
"0": "Single Alarm",
"1": "Double Alarm"
},
"label": "Send double alarms",
"description": "Causes the device to send double alarm messages",
"isFromConfig": true
},
"value": 0
},
{
"endpoint": 0,
"commandClass": 113,
"commandClassName": "Notification",
"property": "alarmType",
"propertyName": "alarmType",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 255,
"label": "Alarm Type"
},
"value": 13
},
{
"endpoint": 0,
"commandClass": 113,
"commandClassName": "Notification",
"property": "alarmLevel",
"propertyName": "alarmLevel",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 255,
"label": "Alarm Level"
},
"value": 255
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "manufacturerId",
"propertyName": "manufacturerId",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 65535,
"label": "Manufacturer ID"
},
"value": 312
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "productType",
"propertyName": "productType",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 65535,
"label": "Product type"
},
"value": 1
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "productId",
"propertyName": "productId",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 65535,
"label": "Product ID"
},
"value": 2
},
{
"endpoint": 0,
"commandClass": 128,
"commandClassName": "Battery",
"property": "level",
"propertyName": "level",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"min": 0,
"max": 100,
"unit": "%",
"label": "Battery level"
},
"value": 98
},
{
"endpoint": 0,
"commandClass": 128,
"commandClassName": "Battery",
"property": "isLow",
"propertyName": "isLow",
"ccVersion": 1,
"metadata": {
"type": "boolean",
"readable": true,
"writeable": false,
"label": "Low battery level"
},
"value": false
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "libraryType",
"propertyName": "libraryType",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Library type"
},
"value": 6
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "protocolVersion",
"propertyName": "protocolVersion",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Z-Wave protocol version"
},
"value": "3.52"
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "firmwareVersions",
"propertyName": "firmwareVersions",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Z-Wave chip firmware versions"
},
"value": [
"0.5"
]
}
]
}
]
}
}
}
]
Here is the dump for 0.1.13:
{
"nodeId": 18,
"index": 0,
"status": 1,
"ready": true,
"isListening": false,
"isFrequentListening": false,
"isRouting": true,
"maxBaudRate": 40000,
"isSecure": false,
"version": 4,
"isBeaming": true,
"manufacturerId": 312,
"productId": 2,
"productType": 1,
"firmwareVersion": "0.5",
"deviceConfig": {
"filename": "/usr/src/node_modules/@zwave-js/config/config/devices/0x0138/zcombo.json",
"manufacturerId": 312,
"manufacturer": "BRK Brands, Inc.",
"label": "ZCOMBO",
"description": "Smoke and Carbon Monoxide Alarm",
"devices": [
{
"productType": "0x0001",
"productId": "0x0002"
},
{
"productType": "0x000c",
"productId": "0x0001"
}
],
"firmwareVersion": {
"min": "0.0",
"max": "255.255"
},
"associations": {},
"paramInformation": {
"_map": {}
}
},
"label": "ZCOMBO",
"neighbors": [
1,
16,
2
],
"interviewAttempts": 1,
"interviewStage": 3,
"endpoints": [
{
"nodeId": 18,
"index": 0
}
],
"values": [
{
"endpoint": 0,
"commandClass": 112,
"commandClassName": "Configuration",
"property": 1,
"propertyName": "Send double alarms",
"ccVersion": 1,
"metadata": {
"type": "number",
"default": 0,
"readable": true,
"writeable": true,
"description": "Causes the device to send double alarm messages",
"label": "Send double alarms",
"min": 0,
"max": 255,
"states": {
"0": "Single Alarm",
"1": "Double Alarm"
}
},
"value": 0
},
{
"endpoint": 0,
"commandClass": 113,
"commandClassName": "Notification",
"property": "alarmType",
"propertyName": "alarmType",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": true
},
"value": 13
},
{
"endpoint": 0,
"commandClass": 113,
"commandClassName": "Notification",
"property": "alarmLevel",
"propertyName": "alarmLevel",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": true
},
"value": 255
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "manufacturerId",
"propertyName": "manufacturerId",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"label": "Manufacturer ID",
"min": 0,
"max": 65535
},
"value": 312
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "productType",
"propertyName": "productType",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"label": "Product type",
"min": 0,
"max": 65535
},
"value": 1
},
{
"endpoint": 0,
"commandClass": 114,
"commandClassName": "Manufacturer Specific",
"property": "productId",
"propertyName": "productId",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"label": "Product ID",
"min": 0,
"max": 65535
},
"value": 2
},
{
"endpoint": 0,
"commandClass": 128,
"commandClassName": "Battery",
"property": "level",
"propertyName": "level",
"ccVersion": 1,
"metadata": {
"type": "number",
"readable": true,
"writeable": false,
"label": "Battery level",
"min": 0,
"max": 100,
"unit": "%"
},
"value": 98
},
{
"endpoint": 0,
"commandClass": 128,
"commandClassName": "Battery",
"property": "isLow",
"propertyName": "isLow",
"ccVersion": 1,
"metadata": {
"type": "boolean",
"readable": true,
"writeable": false,
"label": "Low battery level"
},
"value": false
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "libraryType",
"propertyName": "libraryType",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Library type"
},
"value": 6
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "protocolVersion",
"propertyName": "protocolVersion",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Z-Wave protocol version"
},
"value": "3.52"
},
{
"endpoint": 0,
"commandClass": 134,
"commandClassName": "Version",
"property": "firmwareVersions",
"propertyName": "firmwareVersions",
"ccVersion": 1,
"metadata": {
"type": "any",
"readable": true,
"writeable": false,
"label": "Z-Wave chip firmware versions"
},
"value": [
"0.5"
]
}
],
"deviceClass": {
"basic": {
"key": 4,
"label": "Routing Slave"
},
"generic": {
"key": 161,
"label": "Alarm Sensor"
},
"specific": {
"key": 0,
"label": "Unused"
},
"mandatorySupportedCCs": [
32
],
"mandatoryControlledCCs": []
},
"commandClasses": [
{
"id": 112,
"name": "Configuration",
"version": 1,
"isSecure": false
},
{
"id": 113,
"name": "Notification",
"version": 1,
"isSecure": false
},
{
"id": 114,
"name": "Manufacturer Specific",
"version": 1,
"isSecure": false
},
{
"id": 128,
"name": "Battery",
"version": 1,
"isSecure": false
},
{
"id": 133,
"name": "Association",
"version": 1,
"isSecure": false
},
{
"id": 134,
"name": "Version",
"version": 1,
"isSecure": false
}
]
}
]
}
}
}
]
Seems like this is an issue specific to that device.
Thanks for the help.
I’m not sure what you mean by your post.
It appears that the device is communicating properly with the server and the alarm level and alarm value are correct.
Just a guess, but it seems like the server is not properly communicating the values to HA to populate the entities. Or maybe HA is not picking up the values.
It’s dangerous to know just a little bit.
It’s either a bug in HA or a bug in the server. It’s an issue, I’d go back to 0.10 and log an issue.
Issue logged here:
Are you using polling with just the Z-Wave JS integration or did you have to add Z-Wave JS to MQTT addon also? I need to set poling on a couple of switches.
Apologies if I’m missing something, but am I correct in understanding that:
- The “official” ZwaveJS add-on does not include the ZwaveJS control panel (which limits the ability to do things like a z-wave repair, see the network map, etc).
- There is no way to use the control panel (even if installed elsewhere) to connect to the Official ZwaveJS instance.
- The “community” ZwaveJStoMQTT add-on does include the control panel, but it completely replaces the official add-on and the two don’t work together.
I’d like to stick to the official add-on because I don’t currently need mqtt and just to feel like I’m on the long-term solution, but the control panel seems like a near necessity at this point. Is it really best to just install the community add-on? I assume any custom device names would be lost if I ever switch from community back to official?
Thanks
1 Like
The “official” control panel in HA is growing with each release. 2021.4 adds support for viewing and changing device configuration. If you don’t absolutely need to remove a failed node or do a network heal immediately I’d hold out for that functionality to be added to the core control panel.
4 Likes
Yes, it was in the last week or two. In zwavejs2mqtt docker container 2.2.0 you could do it that way on the Inovelli Red dimmer, but their other devices (the switch, and light / fan combo) had it set separately. While it was like that, the max value was lower than it should have been though, so anything set to the “Chase” effect was rejected. It was split apart to be like the others by container 2.4.0. Sorry, I don’t have the zwavejs2mqtt versions to match the containers.
I posted a script to handle it, if that’s helpful:
weren’t we supposed to see the beta for 2021.4 yesterday? eagerly awaiting that functionality 
on another subject, I am on the verge of including a FGS-223 Fibaro Double switch, but read mixed experiences on the device. Is this yet fully supported on the current Z-WaveJS core integration/add-on?