OpenHab App Rollershutter control

Is it possible that a zWave actor delivers different values by the same command if absolut nothing changed? Not in Openhab and not in the actor settings?

Yesterday the item worked like this:
2019-07-30 21:11:35.759 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 25
2019-07-30 21:11:35.764 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 25
2019-07-30 21:11:35.778 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 25
2019-07-30 21:12:02.236 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command DOWN
2019-07-30 21:12:02.238 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become DOWN
2019-07-30 21:12:02.248 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 100

Than i went to sleep and today without any change it works like:
019-07-31 07:15:47.849 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command UP
2019-07-31 07:15:47.853 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become UP
2019-07-31 07:15:47.865 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 0
2019-07-31 07:15:49.429 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 0 to 94
2019-07-31 07:15:49.516 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 0 to 146
2019-07-31 07:15:49.518 [GroupItemStateChangedEvent] - Shutter_Electric_Meter changed from 0 to 146 through Stairs_Shutter_Electric_Meter

After i restarted the Linux, the functionality from yesterday is back, and the % is shown, but no power consumption. that would be even ok, but if i use the wall switch, no value would delivered to openhab.

huh? Of course. Your log shows a ‘DOWN’ and later an ‘UP’ command is sent to the actuator so of course there’s different actions taken thus different outcome.

I just copied the wrong row, UP or DOWN or SET 20, if the same command was send, the info was different. Here are the same commands like where worked:

2019-07-31 12:07:49.082 [vent.ItemStateChangedEvent] - CurrentDate changed from 2019-07-31T12:06:49.077+0200 to 2019-07-31T12:07:49.078+0200
2019-07-31 12:08:08.444 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command 25
2019-07-31 12:08:08.446 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become 25
2019-07-31 12:08:08.449 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 25
2019-07-31 12:08:10.013 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 94
2019-07-31 12:08:10.095 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 139.4 to 143.2
019-07-31 12:08:57.739 [ome.event.ItemCommandEvent] - Item ‘Stairs_Shutter’ received command DOWN
2019-07-31 12:08:57.741 [nt.ItemStatePredictedEvent] - Stairs_Shutter predicted to become DOWN
2019-07-31 12:08:57.748 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 25 to 100
2019-07-31 12:08:59.312 [vent.ItemStateChangedEvent] - Stairs_Shutter changed from 100 to 32
2019-07-31 12:08:59.395 [vent.ItemStateChangedEvent] - Stairs_Shutter_Electric_Meter changed from 0 to 144.6

This is not an answer to the command but a report. It will report the percentage at that moment in time, eventually the shutter is still moving i.e. has not reached the target position yet.
Btw enable ZWave debug and see openhab.log not events.log as you do.

Here are both files, the node9_3 is where it worked ok and the node9_4 where is false.

As i see in node9_4 is an additional thing:
|12:08:59.307|9|RX REQ ApplicationCommandHandler SWITCH_MULTILEVEL_REPORT 68% 0 /128

01 09 00 04 00 09 03 26 03 44 99

This is setting the wrong value. this is missing in the node9_3.

node9_3.txt (78.0 KB)
node9_4.txt (30.4 KB)

but as i see in the node9_3 are just sent data and no data from the zwave device. the communication seem to be one way. And i think thats why there is no update if i use the wall switch.

Possibly so. Fibaro FGRMs were known to have this problem, too.
Can’t help with Qubinos, though.

Thats exactly why i dont bought the Fibaro :grinning:
I hoped that this one works better.

Maybe is there a command where i can force the device to send data? So i could make a rule which in every given time would force the devices to send the data?

I think it’s meanwhile fixed for Fibaros but I may be mistaken. Search the forum for that thread yourself please.

not the best solution and i dont know how would affect the performence of openhab by lot of devices, but i made a rule which in every 10s send a refresh command to the qubino, and so force to update the status. It seems to work now.

Do u know any reason, why this solution should not be used?

No if it does the trick then it is fine.
You might want your rule to trigger on the rollershutter item to change rather than do it any X seconds.

I did it now like this:

Items:
Switch Stairs_Shutter_Switch { expire=“1m,state=OFF” }

Rules:
rule “fix_stairs_shutter_start”
when
Item Stairs_Shutter received command
then
if (receivedCommand == “REFRESH”){
} else {
sendCommand(Stairs_Shutter_Switch, “ON”)
}
end

rule “fix_stairs_shutter”
when
Time cron “0/10 * * ? * * *”
then
if (Stairs_Shutter_Switch.state == ON) {
sendCommand(Stairs_Shutter, “REFRESH”)
sendCommand(Stairs_Shutter_Electric_Meter, “REFRESH”)
}
end

But i still have some problems with:

  1. The sendCommand(Stairs_Shutter_Switch, “ON”) is launched even if the received command is “REFRESH”
  2. The Stairs_Shutter_Switch dont change its state to OFF after 1m
  3. As i described before the device once delivered the wrong values and once no values. If it dont deliver atm the values, than the refresh dont work either.