Shelly 2 as roller shutter with percentage

xenon185 · December 23, 2019, 10:13am

I think I have a problem with the retain flag.

If I monitor the mqtt topic I can see how the commands are sent.

When I retrieve the topic again, there is a different value

monitoring shelly device:

mosquitto_sub -v -h 192.168.xxx.xxx -t '#' | grep shellyswitch25-xxxxxx/roller/

Command:

shellies/shellyswitch25-xxxxxx/roller/0/command close
shellies/shellyswitch25-xxxxxx/roller/0/pos 0

When I call up the topic again, I read the following:

shellies/shellyswitch25-xxxxxx/roller/0/command open
shellies/shellyswitch25-xxxxxx/roller/0/pos 100

How can that be?
I have posted my config above

xenon185 · December 23, 2019, 10:38am

I have looked at the topics with “MQTT Explorer” and found that the command topic has a retain flag set in the broker.
How this happens I can not explain!
I deleted the flag manually and it is not set anymore So I could solve my problem

A good hint gave me this video:

MQTT Explorer

Michael_Roxin · January 19, 2020, 10:21am

Hi

My Shelly 2 worked like a charm until 104.2 (latest) Hass.io. Now they are Unavailable!

Tried to set reatain to false in both configuration.yaml and in Shelly GUI.

Tried to take away the " " in configuration.yaml.

SO my code:

- platform: mqtt
    name: 'Rullgardin dörr'
    command_topic: "shellies/shellyswitch-55BD61/roller/0/command"
    position_topic: "shellies/shellyswitch-55BD61/roller/0/pos"
    set_position_topic: "shellies/shellyswitch-55BD61/roller/0/command/pos"
    availability_topic: "shellies/shellyswitch-55BD61/online"
    payload_available: true
    payload_not_available: false
    qos: 0
    retain: false
    payload_open: "open"
    payload_close: "close"
    payload_stop: "stop"
    position_open: 100
    position_closed: 0
    optimistic: false

And I have automations lite this.

- alias: Shelly Status Info at Start
  initial_state: true
  trigger:
  - platform: homeassistant
    event: start
  action:
  - service: mqtt.publish
    data:
      topic: shellies/command
      payload: update
- alias: Shelly sync at HA start
  initial_state: true
  trigger:
  - platform: homeassistant
    event: start
  action:
  - delay: 00:00:20
  - service: mqtt.publish
    data:
      topic: shellies/command
      payload: announce
  id: 291fccda42614c799e02288d56e07224
- alias: 'Shellies Discovery'
  trigger:
    - platform: mqtt
      topic: shellies/announce
  action:
    service: python_script.shellies_discovery
    data_template:
      id: '{{ trigger.payload_json.id }}'
      mac: '{{ trigger.payload_json.mac }}'
      fw_ver: '{{ trigger.payload_json.fw_ver }}'

I have tried all night yesterday to fix this but no luck,

Michael_Roxin · January 19, 2020, 11:52am

Can someone help understand a couple of things.

When I run mosquitto add on I use my regular user. I only have one. It works almost great except the problem with shelly 2 above.

Are there any problems with using it this way? My user is administrator.

This *ucking reain flag?

I have 3 shelly 2 as roller shutter
I have 2 Shelly 1 has garage door cover
I have 5 shelly 1 as light
I have 2 shelly plug S as engergy and binary_template for dishwasher and laundry machine

All are configured in configuration . yaml.

All except the roller shutters have the retain set to true

What are the correct way here?

Mqtt was the most stable part of my system until 104.2 version it seems, would like to configure this right.

Jevermeister · July 14, 2020, 6:07pm

I don’t know if that has been solved yet. My Shelly 2.5 never sent something to the availability topic like the shelly1 switches do. Therefore shellies/shellyswitch-XXX/online" won’t be sent and Homeassistant will mark it as offline. I commented out the availability topic and both related payloads and the Shelly 2.5 works fine

MarcALE · August 1, 2020, 3:55pm

I was looking to use my shelly 2.5 as roller shutter with percentage (just as this topic) and managed to find a more straightforward way to do so:

1- Configure my shelly 2.5 as roller shutter in the Shelly app
2- Use the Shelly integration of Home Assistant
3- With the developper tool (States) find the entities associated with my Shelly 2.5:

  sensor.xxx indicates current consumption

  switch.xxx for controling the relays to open and close the shutter

  cover.xxx --> this is the one we want for rolling shutter or garage door

4- In Lovelace-ui I use the HACS custom component slider-entity-row

entity: cover.shelly_shsw_25_xxxxxxxxxxxxxxx 
icon: 'mdi:blinds'
name: Volet cuisine
type: 'custom:slider-entity-row'

xxxxxxxxxxxxxxx = YourShellyDeviceID

And that’s pretty much all there is to do !

…
EDIT
I complete this post with additional features that may help to go further:

kevincaradant · November 12, 2020, 9:33pm

@MarcALE is it working for you in the latest version 0.117.5 of HA ?

I don’t see any slider in front of Roller ?

Any idea why ?

I installed it via HACS and that’s all

Thank you

Edit: I got it. It’s my bad sorry … I forgot on the shelly to setup the calibration mode

MarcALE · November 13, 2020, 2:14pm

It is still working fine.
I am glad you found the solution.

Just in case someone else is looking for the same subject, here is my config:

snikay · December 21, 2020, 8:31pm

can somebody confirm connection issues like @Michael_Roxin mentioned … ?

i was just about to order a dozen shellys… but seems that HA is not ready yet ?

Sliders not out of the box
connectivity issues / complete loss after HA update
interface options from shelly not yet in HA available?

would you guys still recommend shellys anyway - in use with HA?

thx

Pensee · December 21, 2020, 11:17pm

Does somebody made a blueprint for this topic yet ?

maxym · December 22, 2020, 2:38pm

I can answer on points 2 and 3 with confidence: I have no any connection issues (but heard there are some - recently Shelly is working hard on debugging the rootcause). And since I have all my shellies connected via mqtt (without even autodiscover) I have full control over all shelly features being able to work with them as I want (not as in-the-middle-layer force me to).

As of point 1, cannot say for sure since I have only one motorized window (powered by Shelly 2.5) so no enough exoerience to know all possible use-cases

rossiluis22 · December 23, 2020, 3:10pm

Thanks!!! it was very straightforward

MarcALE · December 24, 2020, 7:04pm

Hello,

I only experienced issues with my Shellies once, when Shelly was pushing some major firmware updates. It did not last long, and once the fimware was updated, everything was back to normal. Apparently there won’t be some major changes from Shelly like this one in the future.

Sliders are not “out of the box” in HA, but it is very easy to implement them. And I am pretty confident that they will update Lovealce cards in the future to integrate them.

As far as everyday use is concerned, I do not miss any Shelly option in HA.

I can only recommend the duo “Shelly + HA” in termes of ease and reliability.

snikay · February 25, 2021, 12:01am

+1 , would be great to have a blueprint for this

henalmeida1978 · April 4, 2021, 12:11pm

Hi Guys; New at OA and reading and learning a lot. Can anyone help in creating a scenario to close all shutters and open? Currently I have all the shutters working more or less as I want. The idea would be to create a scenario to close all the house or only part of the house and open of course.

The code is this:

type: entities
entities:

entity: cover.shelly_shsw_25_3c6105e5bc51
name: WC R/C
icon: ‘mdi:blinds’
type: ‘custom:slider-entity-row’
entity: cover.shelly_shsw_25_3c6105e5bc51
full_row: true
title: WC R/C
state_color: true
show_header_toggle: false

thanks in advance

henalmeida1978 · April 4, 2021, 12:12pm

other photo …

MarcALE · April 19, 2021, 5:34pm

Hello,

I suggest the following :

Create some groups with the shutters you want to open/close at once (Group - Home Assistant):
You can call services on groups :

service: cover.set_cover_position 
data:
  position: 90 #Position in %
target:
  entity_id: group.volets_maison #Replace by your group name

Please note that multiple services are available, you may use the DevTools to help you find the right one for your need:

3. Create automations
It is now just a matter of using automations (or blueprints) or scenes to create your scenarii .

Alternatively, if your automations are mostly time based or sun based, I may suggest you use the HACS integration scheduler-component by @nielsfaber and the frontend Scheduler Card by the same author.

4. Lovelace integration
When you integrate the group as an entity in lovelace UI you get a summary

When you click on it you get a very interesting summary.

5. Voice assistant integration
The name you use for the group may be called in your voice assistant (Alexa / Google Assistant…) integration with all the possible services (“open” / “close” / “open to n%”…) it may recognize.

MarcALE · April 19, 2021, 5:57pm

Blueprints are (until today) only for automations, here we are talking about showing sliders in Lovelace UI.

dave-castle · May 8, 2021, 7:28pm

maybe wrong section but ok

i got two shellies 2.5 for shutter, the windows are next to each other, but i got just one physical switch to open or close, i want to use this for both.
so if i open or close shutter with the physical switch it should operate both windows.
think should be workable with a template, but i am not that template guy, any1 can help out please?

T1ppes · May 9, 2021, 5:38pm

I don’t understand your issue…

Yes, you can connect one single physical switch to multiple Shelly 2.5s. This should result in all connected roller shutters being triggered by each of their Shelly’s at the same time, when the switch is pressed.
In Home Assistant each roller shutter of course is a single instance. If you want to control them all at once just like you do with the physical switch, then you can create a cover group and control all roller shutters simultaneously via the group. No need for a template.