Shelly Binding

New DEV build with updated TRV support

  • channel control#mode now has manual/auto/boost. @mvolaart
  • new channel control#profile
  • new channel control#boostTime @scheuerer
  • channel sensor#state updated

Make sure to delete and rediscover your things. Maybe you need to adjust your item linkage (sensor#mode has been moved to control#mode)

New features are not yet finally tested, there might be issues (I post another update when done).

Cool markus7017.
Just updated the binding and reinstalled my TRV now.
The new values are now visable. :slight_smile:
How can I now e.g. enable the “boost”?
I want to have a virtual switch were I can switch on the boost or not.
Can I find a hint in the documentation

Hi Markus
A couple of months ago you did some fixes for the Shelly EM to “calculate” the PF as it was not available in the /status. This has been fixed in the latest firmware

If the PF is now available from the /status which value will be used? The calculated value or the published value?

Thanks
Mark

Hi,

I’m still working on TRV implementation. There is already a new build just a few minutes ago.

Boost mode will have 2 channels
control#boost - enables/disables boost mode (on/off)
control#boostTimer - number of minutes boost will be active once started

In addition you’ll see
control#mode - manual/automatic
control#targetTemp - Temp for auto temp mode
control#position - valve position
sensor#state - valve open/closed
control#profile - Index of active profile

I think this should cover the relevant use cases. I think the design is ok, now I’m working on implementation and it requires more testing that it looks from a first point of view. E.g. what happens if valve is in manual mode when activating boost mode.

One limitation: Currently the CoAP update doesn’t include the remaining boost time. Therefore this requires polling. I need to optimize this, because usually it will be an 1h interval, because the TRV is a battery device. We also openred a feature request to add those to the CoAP status to avoid frequent polling just for this purpose.

@markus7017. Great with “the control#boost - enables/disables boost mode (on/off)”. But as far as I understood the booster feature, it has a start and stop value. So enable is good, but with the enable it will not start itself. Please check the TRV UI and you will see how it works with (start and stop).

My focus is to start the booster and after the default value from 30min it should come back to automatic mode. This should be done via a virtuell switch in OH.

And were is the lastest version of the binding? Here I can only found the version from this morning: myfiles/shelly at master · markus7017/myfiles · GitHub

@markus7017 Thank you very much for this new version. After the things were deleted i could include them without any problems. The channels to control as well temperature as valve position works as expected and also batterylevel works perfect.

Thanks again and keep up the good work!

@markus7017, your latest version from this morning, works now like perfect. The booster feature is now able to switch on/off the TRV-booster-feature and starts. TRV is directly reacting from the automatic mode to the booster mode and back.
Many thanks for your excellent development here.

A question about these TRVs. Is it possible to use an external temperature sensor?

Yes, the Shelly HT is the right sensor for doing this. Current the supporting SW for the HT has an bug. But this should be solved soon.

1 Like

I updated the DEV build to complete TRV support

  • control#mode to switch between manual and automatic mode (uses control#targetTemp setting)
  • control#boost and control#boostMinutes to control the boost mode
  • device#schedule indicates if a schedule is running
  • TRV will be polled every 60sec to get updated “remaining boost minutes”
    (this is not reported by an event, we have a pending feature request with Alterco)

Please help testuing so I could prepare the PR.

Two times a binding update today, not bad @markus7017.
But the boost-modus works again as expected :slight_smile:

and you find another update with some fixes around the control#profile channel (use 0 to disable a profile and 1..5 to select a specific profile)

I posted a new DEV build

  • polling during boost mode has been optimized/remove

Who could help to validate the TRV integration, valve state/pos, boost mode etc.?

I remember that somebody posted a problem with the vibration of DW2
on the other side I would like to confirm tilt updates.
Who has a DW2 and could run a tests that all sensor updates are processed correctly and channels get updated near-realtime (ca. 3sec delay for Wifi connect)?

Are there any other known problems with the binding? I would to get a stable status before moving to Plus/Pro integration.

Are there any binding news regarding the new PLUS and PRO series from Shelly?

New update

  • Status updates while boost mode is active optimized
  • Handling for DW2 status.sensor_error added (don’t fire alarm if sensor_error reports 0)
  • Missing channel status LED added for Dimmer2
  • log “channel updated with value xx” only if data has changed and channel is linked
  • problems with data format while initializing a bulb fixed

Not when, this will start when Gen1 support is stabilized.
I already started to work on Plus/Pro but this will take a while.

2 Likes

New DEV build

  • Dimmer1/Dimmer2: channel timerActive was missing
  • Motion: Time for motionActive and motionTimestamp was 1h off
1 Like

Hi Markus,
not sure anymore if the following behaviour was different in earlier versions or I mix it up with shelly GUI.
When using oh-stepper for setting targetTemp each time I press „+“ the command is sent immediately to the TRV. It would be better if the binding could delay this command in case you press multiple times „+“. Otherwise you need to wait about 5 seconds until you can press „+“ again. This is how shelly GUI also works.

Nope, the binding will no buffer any commands, that’s a guarantee for problems. You could use the knob element

1 Like

I starting working on Plus/Pro support, but it will take a while. Discovery works already.

8 Likes