Shelly integration via RPC protocol

Configuration
1

I noticed that I had a lot of mdns multicast traffic comming from my 14 Shelly Dimmer 2 gen 2. So first I tried to change the CoIoT settings from mcast to the ip address of the home assistant server. This resulted in a double of the amount of multicast traffic.

The integrations home page describes that the device should be able to be configured via the RPC protocol. So I disabled CoIoT and tried to add the device manually. But then home assistant can not connect to it.

Anyone has an idea of how to solve this?

2

Only Shelly Gen2+ devices use RPC. Dimmer 2 is a Gen1 device, without CoIoT it won’t work with Shelly integration.

3

Thanks for your reply.

Any idea of how I can get rid of all the multicast traffic that is taking up so much air time?

What is the reason the multicast traffic doubles when I try to switch to unicast according to the documentation and put the ip address of my home assistant server, instead of “mcast”?

4

I think you should ask these questions to Shelly support.

1 Like
5

okey, I sent them an email now, let’s see what they reply.

6

To be honest, you shouldn’t expect a solution to the problem. First-generation devices are museum pieces that have reached “end of life” status.

BTW You can configure the device using MQTT and disable CoIoT GitHub - bieniu/ha-shellies-discovery: Script that adds MQTT discovery support for Shellies devices

7

Okey, I’ll have a look at the MQTT integration in case I don’t get any luck with the shelly support.

Yes, they are old. But of course, I bought like 14 of them a couple of months before they released their new gen 3 dimmer… :frowning:

Btw, is there anything special I have to do in the HA integration to make it accept the unicast traffic?

8

No, the integration accepts the multicast traffic.