Shelly Pro 3EM cannot be added as smart meter in FoxCloud 2.0 (Avocado 22 Pro) – error when saving

[mfritz]

Hi everyone,

I am trying to integrate a Shelly Pro 3EM as a smart meter into my Avocado 22 Pro system via the FoxCloud 2.0 app. Although the Shelly Pro 3EM can be selected in the app, I get an error message when I try to save the configuration (see screenshot).

Here is what I have already checked:

Both devices are in the same subnet (192.168.178.xxx), the Shelly is reachable via its web interface.

Modbus TCP is enabled on the Shelly on port 502.

Authentication on the Shelly is disabled (no local password).

Shelly Cloud is active and the device is online there.

Firmware of all devices is up to date.

Question:
Has anyone successfully set up this combination (Shelly Pro 3EM + Avocado 22 Pro + FoxCloud 2.0) and can tell me which exact settings are required in the app and/or on the Shelly so that the integration works without errors?

[/img][/img][/img]

[SoliD]

Hello,

I have exactly the same setup and had the same problem today.

After long debugging with tcpdump on the WiFi access point, I found two issues:
The first seems to be that the Shelly Pro 3EM (gen 2, version 1.7.1) does not send mDNS properly when connected to WiFi.
After connecting it with a LAN cable, mDNS broadcasts were sent correctly.

The other thing (which might have been the main issue: I only have one phase at home and so I set my Shelly to monophase. Well.. The Avocado has a hard coded URI which it tries to poll:

Code: Select all

http://<your_shelly_ip>/rpc/EM.GetStatus?id=0

Unfortunately this is delivering a 404 when set to monophase, because the correct URI then is

Code: Select all

http://<your_shelly_ip>/rpc/EM1.GetStatus?id=0

(which does not match the hardcoded one.)
→ So set it back to triphase even if you only use one phase.

After these two things (LAN+triphase) the Avocado was able to connect to the Shelly.
I could then even remove the LAN cable and it still works over WiFi. Let's see if that stays stable.

Oh and maybe you want to check your WiFi that client isolation is turned off.

Hope that helps.

P.S.: If a developer is reading this, you can get the device info with the URI
http://<your_shelly_ip>/rpc/Shelly.GetDeviceInfo
and the capabilities with
http://<your_shelly_ip>/rpc/Shelly.GetComponents
(regardless if the device is in mono- or triphase).
The first URI also returns the current profile and you could derive the correct path to be used (see above).