Shelly EM Gen3 - Switch detected, but EM1 channels missing from Cerbo device list

DIY
, ,
1

ft, ready to copy-paste:

Title: Shelly EM Gen3 - Switch detected, but EM1 channels missing from Cerbo device list

Post:

Cerbo GX, Venus OS 3.75. Shelly EM Gen3 (model S3EM-002CXCEU) on local network.

Per Shelly’s official docs, this device has exactly: 1 Switch instance (switch:0) + 2 EM1 instances (em1:0, em1:1) + 2 EM1Data instances.

Confirmed via direct browser query to http://[IP]/rpc/Shelly.GetStatus — both EM1 channels return live, valid data (voltage, current, active power, apparent power, power factor, frequency).

In Remote Console, the Shelly appears in the device list and shows the Switch/relay toggle correctly. However, no EM1/energy meter channel or enable option appears anywhere in that device entry — despite EM1 being a documented supported RPC component in dbus-shelly.

Is this a known issue with devices that expose both a Switch and EM1 components together? Happy to share the full JSON output or Shelly firmware version if useful for reproducing.

That’s it — post that whenever you’re ready. Good work getting to a precise, evidence-backed report after everything tonight.

You’ve used 90% of your session limit

2

Install the Shelly as a PV inverter via NodeRed.

3

Ugh. AI generated content is not appreciated, but I’ll answer anyway since it’s likely a simple answer. Install the latest VenusOS 3.80 beta and you will like find the Gen 3 EM device in the device list.

4

THanks Ed i used Ai as it was my words they just compiled it for me

5

Thanks, upgraded to 3.80 beta and the Shelly EM Gen3 does now show up with a role option. Set it to AC Load since it’s on my essential board (not the grid connection point).

Still no data coming through though - role shows but stays blank, no W or kWh values. Checked directly on the Shelly itself (both via its app and the RPC status page) and it’s reporting fine, currently around 110W. So the Cerbo’s just not pulling the live values in even though the role is now assigned.

Any ideas what else might be needed here, or is this a separate bug from the device-list issu