Shelly Cloud - new Component? How to implement it? API is available

goliath_2k · January 11, 2019, 2:36pm

Although mqtt is available I would love a component to be done. I want to keep Alexa functions and for that we need to have shelly with cloud access.

johnflorin · January 11, 2019, 3:00pm

Isn’t this it? https://gist.github.com/ispiropoulos/90a5f215e71f4dde635e3e3407fb5804 Custom component, but looks clean enough…my Shellys are in transit, so don’t know how well it works yet.

JesCR · January 14, 2019, 8:14pm

Hi
i have a shelly1, mqtt enable with the settings:
Clean Session on
Retain on
Max QoS 2

In Hass.io, in my config:
- platform: mqtt
name: “Shelly_Entrada_LuzPuerta”
state_topic: “shellies/shelly1-1CF901/relay/0”
command_topic: “shellies/shelly1-1CF901/relay/0/command”
qos: 1
payload_on: “on”
payload_off: “off”
retain: false
optimistic: false

the shelly is connected to a wall switch (to control a entry door light).

I see the switch in HA, but always off and if i try to turn on, it get back to off in a couple of seconds.

What could be wrong?

P.S. i had some sonoff, with espurna and tasmota, and full control with HA, the mqtt server is the hass.io default.

Thanks!

ashscott · January 14, 2019, 8:17pm

When that happens, it usually means that the Shelly is not available to HA.

Either off line or not configured correctly.

Get a copy of MQT Lens from the chrome app store and see if you can publish and subscribe to it using the topics in your config.

You can configure as many switches you like and they’ll show up and operate just how you are experiencing, without them physically existing. Chances are that’s what you’ve got going on.

JesCR · January 15, 2019, 7:35am

Thanks @ashscott
I use MQTT.fx and i could subscribe to shellies/shelly1-1CF901/relay/0/command, but i’m new with mqtt and i doin’t know how to properly check (publish?) if the mqtt client of the shelly is working fine.

Will try with mqttlens when i get back home and post a screenshot

woody4165 · January 15, 2019, 7:49am

@mrodrigues take a look here and here

Bieniu · January 15, 2019, 10:26am

This is example of configuration with availibity for firmware 1.4.4:

github.com

bieniu/home-assistant-config/blob/master/lights.yaml#L33-L53


- platform: group
  name: Bulbs Salon
  entities:
    - light.bulb_salon_1
    - light.bulb_salon_2

You have to add autoaton rule to announce Shelies at HA start:

github.com

bieniu/home-assistant-config/blob/master/automations.yaml#L2152-L2161


  entity_id: remote.salon
action:
  - delay: "00:00:02"
  - condition: template
    value_template: "{{ trigger.to_state.attributes.current_activity != 'PowerOff' }}"
  - service: remote.send_command
    entity_id: remote.salon
    data_template:
      device: "Amplituner"
      command: >-

JesCR · January 15, 2019, 7:50pm

Ok, a little embarrasing, i just forgot to put the 1883 port to the ip in the shelly settings
Works now!

finity · January 16, 2019, 8:23pm

Ok. thanks for that.

Just to clarify…

Do I need to add the “shellies/shellyswitch-5B2604/online” to the “Will Topic” in the Shelly configuration WebUI? Obviously I would change the detail of the center section to my own details (in my case “shellies/shelly1-32CADF/online”).

What then do I put in the “Will Message” section?

Could you post a screenshot of your webui showing that section of the config?

Bieniu · January 16, 2019, 10:30pm

You have to use default settings like this:

shellies/shellyswitch-XXXXXX/online for Shelly2

finity · January 16, 2019, 10:51pm

Thanks!

Working good now.

My shelly 1 default topics are in the form of “shellies/shelly1-32CADF/relay/0”, “shellies/shelly1-32CADF/relay/0/command” and “shellies/shelly1-32CADF/online”. I had that part correct so it was the proper “Will Message” that was tripping me up.

woody4165 · January 17, 2019, 10:33am

Hi @Bieniu

what is unique_id for? Is it mandatory ?

Do I need to have retain to true? I prefer to have it to false.

Thanks

Bieniu · January 17, 2019, 10:47am

unigue_id isn’t mandatory. It will give you entity_registry support.

This is the entity of my Shelly1 with the changed name using the entity registry.

finity · January 17, 2019, 5:44pm

where did you find the documentation for that being an option?

it’s not listed in the options on the component page for the MQTT switch. I haven’t really looked anywhere else aside from an unfruitful quick google search…

(and yes, I caught the mis-spelling and searched for “unique_id”)

Bieniu · January 17, 2019, 6:20pm

I added this option and information about it to the documentation a few months ago. The documentation changed when the devices registry was added. You can use unique_id with all MQTT entities (switch/light/sensor/fan/binary_sensor/etc.)

finity · January 17, 2019, 7:54pm

do you have a link?

i looked in the docs for the mqtt switch and i didn’t see it there.

nickrout · January 17, 2019, 7:59pm

finity · January 17, 2019, 8:07pm

ok…

i understand (kind of… ) about the need for a unique id to be included in the entity registry. I thought that was implemented through the integration of the component.

Based on these statements…

… what I was asking is where is it documented that “unique_id:” is a good configuration variable to use in the config of any mqtt device?

nickrout · January 17, 2019, 8:25pm

Mentioned here https://www.home-assistant.io/docs/mqtt/discovery/

I agree it isn’t immediately obvious and clear. It is a shame shelly doesn’t seem to provide mqtt discovery.

Bieniu · January 17, 2019, 11:00pm

I’m writing a script that will automatically add Shelly switches to HA via discovery.