Zwave rollershutters not responding

For Z-Wave related questions in Domoticz

Moderator: leecollings

Post Reply
gwabber
Posts: 20
Joined: Saturday 02 September 2017 14:32
Target OS: Linux
Domoticz version: 3.8153
Location: Netherlands
Contact:

Zwave rollershutters not responding

Post by gwabber »

Hey all,

From time to time I have problems with Zwave. The network goes bust and I have to reset the device.

Now I have a problem I have not encountered before. I have three Fibaro Rollershutters 3's to open and close my blinds.

Out of nowhere, two of them stopped responding from the Domoticz UI. For some reason, I can still control them from the OpenZwave controlpanel.

But, when I control the blind with the physical button, the switch in de Domoticz UI changes it's status...


What is going on? The controller is an Aeotec stick.


Thanks in advance!
VMWare ESXI, Ubuntu 20.04. Zwave and RFXCom
solarboy
Posts: 300
Joined: Thursday 01 November 2018 19:47
Target OS: Raspberry Pi / ODroid
Domoticz version: 2024.6
Location: Portugal
Contact:

Re: Zwave rollershutters not responding

Post by solarboy »

There is a setting to disable non-local control, I only have Rollershutter 1 & 2 but in #2 the setting is the first dropdown menu in the Device settings called "local protection".

"
Intel NUC with Ubuntu Server VM (Proxmox),mosquitto(docker),RFXtrx433E,zwavejsUI (docker),Zigbee2mqtt(docker),SMA Hub (docker),Harmony Hub plugin, Kodi plugin,Homebridge(docker)+Google Home,APC UPS,SMA Modbus,Mitsubishi MQTT, Broadlink,Dombus
rrozema
Posts: 470
Joined: Thursday 26 October 2017 13:37
Target OS: Raspberry Pi / ODroid
Domoticz version: beta
Location: Delft
Contact:

Re: Zwave rollershutters not responding

Post by rrozema »

Next time, instead of resetting the non-responding device, use the 'Refresh Node Info' ("Vernieuw Node Info") button to have Domoticz re-query the node for its device definitions. That way the device will not get a new ID, but Domoticz will re-connect all existing devices to it or create new ones where they don't exist yet. However, before you press that button, in another window, open the Domoticz log window to see when Domoticz has received the node's information. You can tell by a series of lines with Value_Added in them. One line for each class the device sent (minus some that Domoticz choses to ignore). Maybe you also need to enable a higher logging level on your zwave hardware, I don't know what logging is needed: i have mine set to log all Info, Status and Problem messages. It can take a while before all command classes are received. I have seen situations where not all classes were received and I needed to retry the button a couple of times before the device was properly recognised: you may have to retry a couple of times.
For my Fibaro FGR223 Roller Shutter Controller 3 it's quite a list. You'll find it below and yours must match it, if your device has the same firmware. If one or more are missing after you've waited patiently: try again until all devices are registered. If your device has different firmware you will have to retry a couple of times and compile your own list of classes for that device. Then check that you've got them all registered.

Code: Select all

Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Level, Instance: 1, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Level, Instance: 2, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Level, Instance: 3, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Bright, Instance: 1, Index: 1
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Bright, Instance: 2, Index: 1
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Bright, Instance: 3, Index: 1
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Dim, Instance: 1, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Dim, Instance: 2, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Dim, Instance: 3, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Step Size, Instance: 1, Index: 6
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Step Size, Instance: 2, Index: 6
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Step Size, Instance: 3, Index: 6
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Inc, Instance: 1, Index: 7
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Inc, Instance: 2, Index: 7
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Inc, Instance: 3, Index: 7
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 1: Dec, Instance: 1, Index: 8
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 2: Dec, Instance: 2, Index: 8
Value_Added: Node: 135 (0x87), CommandClass: SWITCH MULTILEVEL, Label: Instance 3: Dec, Instance: 3, Index: 8
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Electric - kWh, Instance: 1, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Electric - kWh, Instance: 2, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Electric - W, Instance: 1, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Electric - W, Instance: 2, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Exporting, Instance: 1, Index: 256
Value_Added: Node: 135 (0x87), CommandClass: METER, Label: Exporting, Instance: 2, Index: 256
Value_Added: Node: 135 (0x87), CommandClass: CENTRAL SCENE, Label: Scene 1, Instance: 1, Index: 1
Value_Added: Node: 135 (0x87), CommandClass: CENTRAL SCENE, Label: Scene 2, Instance: 1, Index: 2
Value_Added: Node: 135 (0x87), CommandClass: CENTRAL SCENE, Label: Scene Count, Instance: 1, Index: 256
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Power Management, Instance: 1, Index: 8
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Power Management, Instance: 2, Index: 8
SendSwitchIfNotExists: Device '135.instance.2.index.8.commandClasses.113' (Power Management) with DeviceID '00008736' matches '135.instance.1.index.8.commandClasses.113' (Power Management). Domoticz will use the Dimmer (and hide the Switch).
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: System, Instance: 1, Index: 9
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: System, Instance: 2, Index: 9
SendSwitchIfNotExists: Device '135.instance.2.index.9.commandClasses.113' (System) with DeviceID '00008737' matches '135.instance.1.index.9.commandClasses.113' (System). Domoticz will use the Dimmer (and hide the Switch).
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 1, Index: 256
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Previous Event Cleared, Instance: 2, Index: 256
SendSwitchIfNotExists: Device '135.instance.2.index.256.commandClasses.113' (Previous Event Cleared) with DeviceID '00008700' matches '135.instance.1.index.256.commandClasses.113' (Previous Event Cleared). Domoticz will use the Dimmer (and hide the Switch).
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Error Code, Instance: 1, Index: 266
Value_Added: Node: 135 (0x87), CommandClass: ALARM, Label: Error Code, Instance: 2, Index: 266
Value_Added: Node: 135 (0x87), CommandClass: MANUFACTURER PROPRIETARY, Label: Venetian Blind slat position, Instance: 1, Index: 0
Value_Added: Node: 135 (0x87), CommandClass: MANUFACTURER PROPRIETARY, Label: Venetian blind tilt position, Instance: 1, Index: 1
As a side note: the situation where not all devices are properly registered in Domoticz is usually caused by stopping Domoticz shortly after it got started. For example by it crashing at some point during start-up. The next time you start domoticz, the information in your ozw_cache file may be corrupted. As long as zwave is not properly initialized, you should leave Domoticz running.
Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest