I am running OpenHAB 2.5.0.M1 on a Windows machine which is working since weeks without issues. Yesterday I noticed a thing with my HomeMatic rollershutters.
I can control them but I can only run the DOWN command. If I try to set a dedicated percentage or the UP command they will moved down and ignore the command.
2 days ago everything was working fine. I have deleted one rollershutter thing for testing and re-added it but without any success.
In my Homematic app directly the shutters are working absolutely fine. So the issue must be on OpenHab site.
Does any one has an idea where I can have a look for a solution?
Perhaps you could begin by looking in events.log when you issue a failing command. Look also in openhab.log at that time.
Tell us more, how are your Items and Things configured.
Thanks for you answer. I am using the Homematic Binding and have configured all Things and Items directly in PaperUI. Until yesterday it was no problem.
I also tested to manually add an item in the items file directly but the same issue. In the openhab.log I cannot find anything related to this item/issue.
The events.log looks normal:
2019-08-14 13:01:45.066 [ome.event.ItemCommandEvent] - Item 'RL_Essen_links' received command 20
2019-08-14 13:01:45.066 [nt.ItemStatePredictedEvent] - RL_Essen_links predicted to become 20
2019-08-14 13:01:45.070 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 1 to 20
2019-08-14 13:01:45.244 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 20 to 1
2019-08-14 13:01:51.275 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 1 to 20
2019-08-14 13:02:54.175 [ome.event.ItemCommandEvent] - Item 'RL_Essen_links' received command UP
2019-08-14 13:02:54.176 [nt.ItemStatePredictedEvent] - RL_Essen_links predicted to become UP
2019-08-14 13:02:54.184 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 20 to 0
2019-08-14 13:02:54.348 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 0 to 20
2019-08-14 13:03:16.864 [vent.ItemStateChangedEvent] - RL_Essen_links changed from 20 to 100
First test: Shutter is completely open and I send command for 20% which was succesful. Then I tried to move it back to completely open (UP) but it moves completely down. So the command UP and DOWN is doing the same thing (not inverted).
Its absolutely unclear why it was working over weeks and since yesterday I am having this issue.
For now I have implemented a workaround: I control my shutters with Habpanel or with the Openhab Application via sitemap.
In this I changed the UP command to “1” which is working for now.
It won’t fix anything, but I would make autoupdate false on your Item. That will get rid of the “prediction” and subsequent state update, leaving only the real feedback from your device.
Okay, so this has changed since your first post. I don’t know if that is a clue.
Since you have now upgraded to 2.5M2, it may be worth deleting and rediscovering the roller Thing
Yep, this is a per Item setting.
autoupdate is essentially a dummy binding that listens for commands, makes an educated guess about the outcome, and directly updates the Item’s state. e.g. command a Dimmer ON, predict state 100%.
It’s good for giving a responsive UI when the target device responds slowly or not at all.
When you’ve got a roller that you expect to respond slowly, it can be a nuisance e.g. jiggly icons or sliders.
If i use the command up on the sitemap for the rollershuter is see this on the log.
2019-10-03 21:52:06.223 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:52:06.224 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:52:06.233 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '0' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:52:06.234 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '0' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:52:06.404 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:52:06.404 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
When i press down, i see this in the log:
2019-10-03 21:58:32.069 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
2019-10-03 21:58:32.070 [WARN ] [ui.internal.items.ItemUIRegistryImpl] - Exception while formatting value '100' of item DG_OF_Rolladenaktor_01_Ch4_Level with format '%.2f %unit%': Conversion = 'u'
If i remove the link to the channel the rollershutter item it self correctly recieves the update “0” for up and “100” for down, but with the homematic channel there is a crazy conversion.
For my normal switches in the room i solved it that way, that i send a “1” for up, because there happens the same, when i send a “0”.
I think there is problem in the homematic binding.
I really looking for a solution of the problem.
