Added Shelly device integration app, with support of

🧰 Built-In Apps and Drivers
1

From the 2.4.3.122 release notes:

  • Added Shelly device integration app, with support of:
    • v1 switches, relays, lights, natural gas and leak sensors.
    • v2+ switches, relays, dimmers, lights, power meters, temperature, and humidity sensors.

Can we get some more details on this new app?
Is it intended to replace this:

1 Like
2

The new built-in in app supports the Shelly Wi-Fi devices. We are not familiar with the community effort to support these devices. You could try the new built-in app, and maybe you can share yor opinion by comparing the two integrations.

1 Like
3

Hi @bobbyD, The community drivers and the old way of adding using the virtual switches used to create a parent / child set of devices with the parent being the device inputs and the child being the relay or light output control, Ive added a Shelly WiFi v2 RGBW Light and its fantastic that I can control the device and it updates its states promptly, however I am unsure of where the i1 - i4 inputs are? Are they not exposed with this integration or am I missing something dumb? I can see them in the device data but not in the commands nor are they available as buttons in rule machine, see attached image,

image
image741×642 79.8 KB

cheers

Duncan

4

Hi Duncan,

the RGBW2 has only 1 switch input, for the 4 channels. the RGBWplus has 4 switch inputs.
With the classic RGBW driver, the RGBW2 module has only 1 control.
But using the "integration" app, for the same module I get a parent and 4 child devices, and in the Rule Machine I can select the child/channel

image
image694×459 34.3 KB

image
image914×256 19.1 KB

5

Hello, I have a problem that this integration is getting disabled without any clear reason occasionally and causing problems in my automations. Is there updates available to fix that problem?

6

Hi Marc,

I can see the output controls, just not the input controls. When you try to create a rule, or push a button, there was no interface for those devices. It used to be that the parent device handled the inputs and the child devices were the output channels.

Cheers

Duncan

7

Hi Duncan,

you're right, there's no way to acces the inputs. you cannot use the RGBW2plus as a button device. you'll have to use one of the shelly I4 versions

cheers,

Marc

1 Like
8

@gopher.ny might be able to help with this as they have adopted Shelly as a native driver for HE?

Cheers

Duncan

9

Q1:
image

So the best selection I can see to accommodate a Shelly1 Gen4 device is as shown above, is that right? Or is this Integration not at the Gen4 level yet?

Q2: (assuming this selection is adequate)

Am I missing where the driver/integration picks up any configured Shelly Components and allows them to be actionable data in HE ? I have configured such on the Shelly device and now I'd like to have them passed to the hub.

EDIT ADD: Just noting the following in the Debug Log and this prompts me to ask the additional question of how to get that Temp Data through to the Device page and somewhere that it can be used in HE. Unless it's already available and I just haven't looked deep enough.

parse [id:0, output:false, sectionName:switch:0, sectionType:switch, source:WS_in, temperature:[tC:49.7, tF:121.5]]

Thanks in advance for any and all replies.

@bobbyD