Fakro ZWS12 Z-Wave window actuator problem

sihui · January 22, 2019, 11:36am

Try setting the command poll period to a shorter/longer time:

sihui · January 22, 2019, 11:46am

Selection item in HABPanel?

Selection item=Alexa_WZ_Volume  label="Lautstärke" mappings=[15="15",25="25",35="35",45="45",55="55",65="65",75="75",85="85",95="95"]

jamac · January 22, 2019, 9:49pm

I thought this might be the answer but i can’t get my changes to save. Could this be a display issue too? I assume this setting is milliseconds, ie, a 60s delay = 60,000?

sihui · January 23, 2019, 7:13pm

Nope.

Yes.

If it is a mains powered device it saves instantly (to double check I just tried it with one of my dimmers)
If your device is battery operated, you need to wake the device or wait until the next auto wake up.

jamac · January 28, 2019, 1:12pm

Here is the log file of the behavior i’m dealing with. The window was fully open (ie 100%). I selected 0% on the slider and the window started closing. After about 20 seconds the slider jumped from 0% to 72% where it remained even though the window closed all the way to 0%, ie the window never updated its state to the controller.

I’m running OH2 on a RPi with an Aeotech z-wave stick.

A couple of things that look a little weird to me.

There are a number of UNKNOWN state updates
There are a number of long delays (ie, 1500+ms)

The current command poll period is current set to the default (1500). I’ve not been able to change this setting PaperUI or Habmin.

Thoughts?

Thanks for the selection suggestion. I might have to go down that route if i can’t work this out.

jamac · January 28, 2019, 1:14pm

Just in case the image is too small here is the log in a code fence:

23:21:39.35515 COMMAND RECEIVED zwave:device:d83a65b3:node15:blinds_control 0 [PercentType]
23:21:42.22915 TX REQ SendData 29 SWITCH_MULTILEVEL_SET 0%  ACK AUTO_ROUTE EXPLORE
23:21:42.24115 RX RES SendData 29 ACCEPTED BY CONTROLLER 0 /128
23:21:42.36115 RX REQ SendData 29 ACK RECEIVED from device in 132ms 0 /128
23:21:54.38515 TX REQ SendData 33 SWITCH_BINARY_GET  ACK AUTO_ROUTE EXPLORE
23:21:54.39615 RX RES SendData 33 ACCEPTED BY CONTROLLER 0 /128
23:21:55.70415 RX REQ ApplicationCommandHandler SWITCH_BINARY_REPORT UNKNOWN 0 /128
23:21:55.72915 STATE UPDATE zwave:device:d83a65b3:node15:switch_binary ON [OnOffType]
23:21:55.95215 RX REQ SendData 33 ACK RECEIVED from device in 1567ms 0 /128
23:21:56.13115 RX REQ ApplicationCommandHandler SWITCH_BINARY_REPORT UNKNOWN 0 /128
23:21:56.15015 STATE UPDATE zwave:device:d83a65b3:node15:switch_binary ON [OnOffType]
23:21:56.17115 TX REQ SendData 34 SWITCH_MULTILEVEL_GET  ACK AUTO_ROUTE EXPLORE
23:21:56.18015 RX RES SendData 34 ACCEPTED BY CONTROLLER 0 /128
23:21:56.41315 RX REQ ApplicationCommandHandler SWITCH_BINARY_REPORT UNKNOWN 0 /128
23:21:56.42415 STATE UPDATE zwave:device:d83a65b3:node15:switch_binary ON [OnOffType]
23:21:56.64715 RX REQ ApplicationCommandHandler SWITCH_BINARY_REPORT UNKNOWN 0 /128
23:21:56.66415 STATE UPDATE zwave:device:d83a65b3:node15:switch_binary ON [OnOffType]
23:21:57.53215 RX REQ ApplicationCommandHandler SWITCH_BINARY_REPORT UNKNOWN 0 /128
23:21:57.54915 STATE UPDATE zwave:device:d83a65b3:node15:switch_binary ON [OnOffType]
23:21:57.81315 RX REQ SendData 34 ACK RECEIVED from device in 1642ms 0 /128
23:21:57.89915 RX REQ ApplicationCommandHandler SWITCH_MULTILEVEL_REPORT 72% 0 /128
23:21:57.91715 STATE UPDATE zwave:device:d83a65b3:node15:blinds_control 72 [PercentType]
23:21:58.71215 RX REQ ApplicationCommandHandler SWITCH_MULTILEVEL_REPORT 72% 0 /128
23:21:58.72915 STATE UPDATE zwave:device:d83a65b3:node15:blinds_control 72 [PercentType]
23:21:58.78615 RX REQ ApplicationCommandHandler SWITCH_MULTILEVEL_REPORT 72% 0 /128
23:21:58.80015 STATE UPDATE zwave:device:d83a65b3:node15:blinds_control 72 [PercentType]
23:21:59.24215 RX REQ ApplicationCommandHandler SWITCH_MULTILEVEL_REPORT 72% 0 /128
23:21:59.25615 STATE UPDATE zwave:device:d83a65b3:node15:blinds_control 72 [PercentType]

sihui · January 28, 2019, 1:21pm

As long as you are not able to change any parameters you need to find that problem first …

As soon as you have solved that problem please provide a unfiltered debug log in text format.

barneyd · February 24, 2021, 8:41pm

Appreciate that this is a long time ago now but for anyone finding this through a search: you can’t modify zwave module parameters for nodes configured in text files. It’s a limitation of OpenHAB.

If you need to modify module configuration, comment out the node in your .things file and then rediscover your network. Adopt the discovered thing from your inbox. You can then change parameters and save them to the module.

Once you are done, delete the temporary thing and uncomment the entry in .things and your device should reappear with its original OH configuration but remembering the changes made to the module itself.