Rollershutter 0-100-0 state

Tags: #<Tag:0x00007f616f05af50>

Hello people,
I am new here.
Have a http binding controlled rollershutter system.
added the items to the items file
added the items to the sitemap
each time I send either UP or DOWN command, the state initially jumps to respectively 0 and 100 prior to actually taking the inputted state updates (which my server send to openhab via the REST api PUT calls)
in my evens.log this also shows the rollershutter concerned is item ‘Rol_SCHU’
As you can see it ‘spikes’ after receiving a command.(see **) Is there a way to avoid this? It is not only unpleasant in the GUI, it also pops up in persistence (everyChange)
Other than that the functionality itself works like a charm.

events.log

2018-05-20 17:00:02.922 [ome.event.ItemCommandEvent] - Item 'Rol_SCHU' received command DOWN
**2018-05-20 17:00:02.928 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 0 to 100**
**2018-05-20 17:00:03.385 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 100 to 0**
2018-05-20 17:00:03.769 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 0 to 1
2018-05-20 17:00:04.165 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 1 to 3
2018-05-20 17:00:04.538 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 3 to 5
2018-05-20 17:00:04.927 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 5 to 6
2018-05-20 17:00:05.284 [ome.event.ItemCommandEvent] - Item 'Rol_SCHU' received command STOP
2018-05-20 17:00:05.352 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 6 to 8
2018-05-20 17:00:05.732 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 8 to 10
2018-05-20 17:00:08.166 [ome.event.ItemCommandEvent] - Item 'Rol_SCHU' received command DOWN
**2018-05-20 17:00:08.175 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 10 to 100**
**2018-05-20 17:00:08.529 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 100 to 11**
2018-05-20 17:00:08.791 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 11 to 12
2018-05-20 17:00:09.158 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 12 to 14
2018-05-20 17:00:09.496 [ome.event.ItemCommandEvent] - Item 'Rol_SCHU' received command STOP
2018-05-20 17:00:09.546 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 14 to 16
2018-05-20 17:00:09.961 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 16 to 17
2018-05-20 17:00:15.604 [ome.event.ItemCommandEvent] - Item 'Rol_SCHU' received command UP
**2018-05-20 17:00:15.621 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 17 to 0**
**2018-05-20 17:00:15.964 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 0 to 18**
2018-05-20 17:00:16.399 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 18 to 16
2018-05-20 17:00:16.807 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 16 to 14
2018-05-20 17:00:17.183 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 14 to 13
2018-05-20 17:00:17.581 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 13 to 11
2018-05-20 17:00:17.972 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 11 to 9
2018-05-20 17:00:18.358 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 9 to 8
2018-05-20 17:00:18.741 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 8 to 6
2018-05-20 17:00:19.105 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 6 to 4
2018-05-20 17:00:19.530 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 4 to 3
2018-05-20 17:00:19.908 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 3 to 1
2018-05-20 17:00:20.289 [vent.ItemStateChangedEvent] - Rol_SCHU changed from 1 to 0

Thank you,

Best regards
Lenny
PS: running openHAB 2.2.0 (APT-GET install) on Raspbian 8.0 (Jessie)
PPS: I am aware of the delay in ‘state updates’ after the STOP command has been issued, this is not a problem in my setup!

This behaviour is normal, you are getting the position feedback from the blind as it moves.
So you send a 100 command. The blinds obeys and starts from 0 and goes up until you press stop. As long as it is functional where exactly is the problem?

Hi Vincent,

Thanks for the reply. While you’re right in assessing there is not a real problem with this, it looks a bit ugly in my persistence data. Every movement of the shutters is basically spiked.
I could also create a few text items to store the respective rollershutter positions. those I suppose would not be impacted by the UP/DOWN command.
I was not aware that the UP command was a 0 command and DOWN a 100 command.
Good to know,

Any other suggestions? If not I suppose I work around it as I said!

Best regards

Lenny Zaman

If it’s only a “look” issue, there is no issue.
If you want to restore the values on OH startup then use mapdb and restoreOnStartup
and don’t persists your rollershutters in the other DB if you don’t like the look of it.