[OH3] Migration of MQTT Rollershutter

Setup, Configuration and Use Migration
, ,
1

Hey,

I am trying to upgrade to OH3. I have some rollershutters in my home. They don’t react like normal rollershutters in Openhab, so I added them as “dimmer” - because they only take a percent-value.

Now this rollershutters take a taget value (via MQTT), for example 100%; then they begin to drive and send a status via MQTT representing the current position. 10%, 15%, 20% till they reach the desired value. In OH2.5 there was no problem.

In OH3 they get their target value, but when the first status-update arrives, OH fires the “commandTopic” with the item changed in this moment. So the rollershutters start to drive, post their first status update (in this example maybe 10%), then OH sends a new target-value 10% and they stop at this 10%.

I searched the web and this forum but I could not find any hint. So I would be thankful for any advise; private messages can be in german, too :slight_smile:

Thanks
Dominik

  - id: knx702
    channelTypeUID: mqtt:dimmer
    label: Rolllade Wohnzimmer
    description: null
    configuration:
      commandTopic: ambid/to_KNX/6-2-2/GrpVal_Write/req
      formatBeforePublish: "{ Value: %s }"
      stateTopic: ambid/from_KNX/7-0-2/GrpVal_Write/ind
      transformationPattern: JSONPATH:$.Value
2

Litte Update: it seems, OH3 fires a “itemCommandEvent” if it “rounds” the value. So I send a 25.1 to the item, it takes this value, rounds it to 25 (because its a dimmer and takes only integers) and fires a change event to 25. Now I am investigating, why this behaviour is different to 2.5. Anyone can help?

2021-01-20 09:14:05.210 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 39 to 11.0                            
2021-01-20 09:14:08.366 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 11.0 to 18.0                          
2021-01-20 09:14:11.514 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 18.0 to 25.1                          
2021-01-20 09:14:11.579 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'mqtt_ambihome_knx702' received command 25                                
2021-01-20 09:14:11.584 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'mqtt_ambihome_knx702' predicted to become 25                             
2021-01-20 09:14:11.586 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 25.1 to 25                            
2021-01-20 09:14:13.681 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 25 to 23.1                            
2021-01-20 09:14:13.734 [INFO ] [openhab.event.ItemCommandEvent      ] - Item 'mqtt_ambihome_knx702' received command 23                                
2021-01-20 09:14:13.737 [INFO ] [penhab.event.ItemStatePredictedEvent] - Item 'mqtt_ambihome_knx702' predicted to become 23                             
2021-01-20 09:14:13.741 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 23.1 to 23                            
2021-01-20 09:14:15.208 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'mqtt_ambihome_knx702' changed from 23 to 22.7

Also there is a typo in the logging engine :wink: “penhab” instead von “openhab”.

3

I think I can’t really help with your Rollershutter Problem… But the mentioned typo isn’t really one, if the line is to long the logger has to display, it’ll cut the first chars, so this is an expected behavior…

1 Like
4

Oh ok, it’s a feature, thanks :slight_smile: