[APP][Pro&Cloud] Shelly

Apps
, , , ,
747

I have a piece of rgwb strip of about 50cm which is a leftover from my showerproject :laughing: could send it to you (assuming you are dutch?)

748

If you are willing to buy one, I will support with donation :slight_smile:

749

That will do. Just send you my address by PM.

I ordered one a long time ago but Aliexpress never delivered. Had to cancel and get a refund. I have some more stuff that seems to have gotten lost between China and my home address due to Corona so I dont feel like ordering more stuff right now. But thanx anyway. With the strip of @zakraket I should get the job done.

750

An initial response to explain how it should work. I’ll test it further if I have a proper RGBW LED strip to test with if it actually works as intended.

It should not work that much differently from the official Shelly app. In Homey setting a color will set the color of the RGB LEDS to that color. The color wheel in Homey with predefined colors is a bit weird though as the colors on that wheel are not full blue and green (red is 100% red though). But using the color picker from the device should give you almost the correct color. I say almost because Athom choose to use a percentage based hue capability while hue is a integer between 0 and 360. So there are some rounding errors causing a slight deviation from the desired color but this is almost unnoticable.

The brightness of the colors are controlled from Homey using the dim capability which is similar to the brightness (or gain) setting in the Shelly app.

The W LEDS are controlled using the temperature wheel or flow cards. This is a bit strange since the Shelly does not actually support color temperature but just dims the white channel. But setting the temperature to 100% will completely dim the white channel. Setting the temperature to 0 will set the white to full (this may seem reversed compared to the Shelly app).

This is where it starts to get weird and where I need to test this myself. It should work as described above. You will need to set the color of the RGB LEDS to red and the light temperature to 100 (to disable the white channel). Are you sure you have set the white channel to 0 when you want to use colors (by setting the temperature to 100 in a flow).

What the toggle white mode does when changed to on is set the gain on the RGB channel to 0 and set the white channel to 100 (similar as in the Shelly app with the two sliders) and visa versa when set to off. The behaviour you are seeying seems to be different from this.

Which brings me to my conclusion. When I wrote this driver I tested it with a certain RGBW LED strip which seemed to behave differently then yours. I do not have this strip available anymore so I can test further. But perhaps a different LED strip causes these unexpected results you are seeying. I hope to know more when I test it with your leftover LED strip.

751

Okay, so the tempsetting (0-100%) dims the white channel. Seems to work. If that’s how it works, that’s fine, at least I know what to do.

The problem with the colorwheel was I think in my case that firstly the warm white channel did not dim (which I now know can be done using the temp). I also see that the color wheel seems to contain slightly different colors and not 100% green/100% blue, but there’s also an option to choose from the full rainbowcircle. So that problem can be tackled too.

Did a bit of testing with a flow that:

  • set a temperature to x% AND
  • dim to x %

When flow 1)

  • temp 0%
  • dim 0%
    Should give only warm white: works always

After running flow 1, run flow 2)

  • temp 100%
  • dim 100%
    Should dim warm white channel, + set 100% RGB channel, but: dims the whole strip to OFF, only the second time I run the flow I get 100% RGB (cool white light)
    It “forgets” a previous set color, but that seems kinda logic since setting 0-0-100 to 0% results in 0-0-0 which does not contain a specific color anymore.

When I add to flow 2)

  • set a color (to red)
    and run the flow after first running flow 1 then I see the strip dim fast from warm white to dark to red

When I change flow 1 to:

  • set a temp to 0%
  • dim to 1%
    This should keep the red color active. When I then run flow 2 it dims warm white to 0, but leaves RGB on 1% red which should be 100% red. Running the second time turns red to 100%

I will send you the strip today

752

I have received the strip and I think I tackled the issue. Are you technically capable of doing a command line install from the master branch on GitHub to test this?

If not, I’ll just push it to the app store under the assumption it’s fixed.

753

No I can’t, sorry

754

v1.20.4 - 2020-06-05

Fix for setting white channel on Shelly RGBW2 Color.

1 Like
755

Cant test now also, because I had to remove the strip from the ceiling (since i’m still building). Will be a couple of days

756

I’m looking for people who are willing to install a test version of the Shelly app and see if they run into any issues. The test version can be found here. Next to some new functionality there is a lot of code refactoring done which I would like to see tested before pushing it live. The change log looks like this.

v1.21.0

  • BREAKING CHANGES: Deprecated the device “Action event” triggercard and replaced it with a generic “Action event” card which is not device specific but contains the device name as token. This is easier to maintain. Please update your flows by replacing the device specific card with the triggercard from the app. The functionality for the device specific card will be removed with the next major release.
  • Added support for the new Shelly i3 (thanx to domotica-shop.nl for sending me a device).
  • Added a new triggercard that can trigger a flow when a device is unreachable for a specified number of minutes (under device settings). This is only available for non-battery operated devices that are being polled for their status.
  • Lots a code refactoring for easier maintenance.
757

I’m to impatient. If no one offers to be a guinea pig I guess everyone will be a guinea pig. I’m pushing it to stable and will see what happens.

3 Likes
758

v1.21.0

  • BREAKING CHANGES : Deprecated the device “Action event” triggercard and replaced it with a generic “Action event” card which is not device specific but contains the device name as token. This is easier to maintain. Please update your flows by replacing the device specific card with the triggercard from the app. The functionality for the device specific card will be removed with the next major release.
  • Added support for the new Shelly i3 (thanx to domotica-shop.nl for sending me a device).
  • Added a new triggercard that can trigger a flow when a device is unreachable for a specified number of minutes (under device settings). This is only available for non-battery operated devices that are being polled for their status.
  • Lots a code refactoring for easier maintenance.
1 Like
759

Do you plan on adding Shelly Dimmer 2?

760

The dimmer 2 is not released yet but see the info below about missing devices.

Missing devices

Allterco Robotics, the company behind the Shelly devices, is releasing new products very often. If you want a device added to this app which is currently missing you have three options:

  1. Wait for the API documentation to be updated. Based on the documentation I can add the device. Allterco Robotics is slow in updating their API documentation however.
  2. Donate me money so I can buy the device or send me the device itself so I can add support using the actual device.
  3. If you own the device you can send me the output of http://yourshellyip/status . This tells me the capabilities and the way the API is implemented for that device.
761

@Phuturist never reported back, but reboot works again.

762

I am using a i3. I dont know how i can use it in a flow when a input is “true” the flow is : when > action event. And device is i3 and? Than… is it also possible to add the status of the switch in the dashboard?
Thanks for the great app

763

As far as I can tell the Shelly i3 is unware of the state of the switches connected. It only allows you to filter on the actions it recieves and forwards to Homey using the action event token (which for instance is double_shortpush_2 indicating a double push event on input #2).

Could be I missed something though. Just to be be sure, could you post the output of http://yourshellyi3_ip/settings .

If I’m not mistaken about this a possible solution is adding a virtual switch and track the state of this switch based on the events. I might even be able to do this in the code and add a on/off device for each input come to think of it but it would not be foolproof as the Shelly i3 just can not be sure about the state of the connected switch.

764

I use it as a door sensor. If the contact is closed, i can see the state on the shelly. So i thought maybe…

{“device”:{“type”:“SHIX3-1”,“mac”:“A4CF12F47665”,“hostname”:“shellyix3-A4CF12F47665”,“num_inputs”:3, “num_outputs”:0},“wifi_ap”:{“enabled”:false,“ssid”:“shellyix3-A4CF12F47665”,“key”:""},“wifi_sta”:{“enabled”:true,“ssid”:“Mywifi”,“ipv4_method”:“dhcp”,“ip”:null,“gw”:null,“mask”:null,“dns”:null},“wifi_sta1”:{“enabled”:false,“ssid”:null,“ipv4_method”:“dhcp”,“ip”:null,“gw”:null,“mask”:null,“dns”:null},“mqtt”: {“enable”:false,“server”:“192.168.33.3:1883”,“user”:"",“id”:“shellyix3-A4CF12F47665”,“reconnect_timeout_max”:60.000000,“reconnect_timeout_min”:2.000000,“clean_session”:true,“keep_alive”:60,“max_qos”:0,“retain”:false,“update_period”:30},“coiot”: {“update_period”:15},“sntp”:{“server”:“time.google.com”,“enabled”:true},“login”:{“enabled”:false,“unprotected”:false,“username”:“admin”},“pin_code”:"",“name”:"",“fw”:“20200601-123434/v1.7.0@d7961837”,“factory_reset_from_switch”:true,“discoverable”:true,“build_info”:{“build_id”:“20200601-123434/v1.7.0@d7961837”,“build_timestamp”:“2020-06-01T12:34:34Z”,“build_version”:“1.0”},“cloud”:{“enabled”:false,“connected”:false},“timezone”:“Europe/Amsterdam”,“lat”:52.156700,“lng”:5.384760,“tzautodetect”:true,“tz_utc_offset”:7200,“tz_dst”:true,“tz_dst_auto”:true,“time”:“22:31”,“unixtime”:1591828280,“hwinfo”:{“hw_revision”:“prod-2020-04-21”, “batch_id”:1},“longpush_duration_ms”:{“min”:800, “max”:3000},“multipush_time_between_pushes_ms”:{“max”:500},“inputs”:[{“name”:null,“btn_type”:“toggle”,“btn_reverse”:0,“btn_on_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_on_1/",“btn_off_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_off_1/”,“shortpush_url”:null,“longpush_url”:null,“double_shortpush_url”:null,“triple_shortpush_url”:null,“shortpush_longpush_url”:null,“longpush_shortpush_url”:null},{“name”:null,“btn_type”:“momentary”,“btn_reverse”:0,“btn_on_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_on_2/”,“btn_off_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_off_2/”,“shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/shortpush_2/”,“longpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/longpush_2/”,“double_shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/double_shortpush_2/”,“triple_shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/triple_shortpush_2/”,“shortpush_longpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/shortpush_longpush_2/”,“longpush_shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/longpush_shortpush_2/”},{“name”:null,“btn_type”:“momentary”,“btn_reverse”:0,“btn_on_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_on_3/”,“btn_off_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/btn_off_3/”,“shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/shortpush_3/”,“longpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/longpush_3/”,“double_shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/double_shortpush_3/”,“triple_shortpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/triple_shortpush_3/”,“shortpush_longpush_url”:“http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/shortpush_longpush_3/”,“longpush_shortpush_url”:"http://192.168.1.150:80/api/app/cloud.shelly/button_actions/shellyi3/shellyix3-A4CF12F47665/longpush_shortpush_3/”}]}

765

Screenshot_20200610-194205_Samsung Internet
Screenshot_20200610-194205_Samsung Internet1080×2220 331 KB

766

It’s strange Shelly shows this in their app while this data is not available in their API (also not in the output you posted). There should be an on/off variable (with other Shelly devices it’s called ison) in there for me to work with. So for now there is no way for me to show this data in Homey in a reliable way, Shelly would have to updated their API for this.

I’m interested to know though what kind of contact is connected to input 1 as door sensor?

1 Like