It’s a Shelly 3EM that I have, bought in 2024, however, I don’t know the generation, how can one find out?
Here is the list of what devices the devoloper has tested and has worked atleast.
HTTP based driver for Shelly energy meters to be used on VenusOS
What’s the reason why switchable devices cannot have the “pvinverter” role? I have an unused Shelly Plus 1PM and would like to use it to measure the output of an Hoymiles inverter. Thanks a lot.
What is missing in the list is the the Shelly Pro EM - I would like to replace the ET112, which does not work well to count my old Inverter…
Did somebody already test the PRO EM?
My Shelly Pro EM 50 only shows up as a switch, which doesn’t do me any good.
My Shelly EM Mini Gen4 (1.7.0-miniemg4prod0) isn’t working, my other Shelly devices are recognized and working fine.
What could be the problem?
It looks like shellies with authentication turned on are not discovered. At least that’s what my experiments seem to show. Can someone confirm that?
My gen3 PM minis are not found either, while gen3 1PM minis are found correctly. They have basically identical configs. No authentication differences.
Gen3 PM mini is very similar to Gen4 EM mini. Seems like the discovery algorithm misses some Shelly models.
Same story here - my 1PM Mini vanished with ~58. Back to ~54 and all working again. I didn’t have time to diagnose, just needed it working but clearly a bug in ~58.
Cheers
Phil
From Version -58 Shelly RGBW PM is recognized not only in 4x White mode, but also in RGB(W) including a color wheel in the switch pane. GREAT!! Preset function seems not working yet. However, the Shelly which is set to 4x White mode is now treated as an AC Load, but not shown as AC Load on the overview page. Since I use these on 12V in a Boat or RV, I’m wondering if this is meant to be an AC Load. See below screenshots.
Cheers
Swen
Hi @kaischmitz,
Yes this is correct. When a Shelly device is secured with a password, it can also not be probed so it won’t show up in the discovered devices list.
We have the ambition to support secured Shelly devices as well, but currently it is not supported.
Hey
Shelly RGBW PM represent only 1 channel instead of 4. In my configuration it working as 4 different light not rgb.
Maybe I need to change something in Shelly config?
I am experiencing the same issue. In Light mode I only see one channel instead of four.
I have checked the settings thoroughly, but I cannot find any option that allows this configuration.
Hi @Obstein and @mikisound,
Shelly RGBW PM “White mode” or “4X lights” mode is not supported yet, but it will definitely be supported in the future.
Thanks @rzee , I’ve disabled authentication on the device in question (Shelly 1PM Mini Gen3) and it gets detected and power/ energy are read correctly.
I still see two issues though:
- I cannot find a way to tell Venus OS that this device is on phase L2 - it automatically assumes it’s on L1
- I cannot tell Venus OS that this shelly measures the power of an AC coupled PV inverter. The only choice I have is “AC load” regardless of the position setting. Mine is on AC output.
I was hoping to get a more decent view in VRM. Currently it shows 0A as soon as there’s a feed in on the respective phase from the AC coupled inverter and I have no idea if the calculations for power and energy will be accurate.
Two comments:
- The Github page only claims success with gen4 devices. That does not mean gen3 will not work but it can explain you still have issues?
- According to the Github page, only metering devices without a switchable output can be configured other than acload. It basically says all metering devices with an integrated switch are acload only
The Pro3EM is metering only and can be changed to other roles. Which in code is quite a thing requiring smoothening as lots of other calculations are depending on it (like ac loads and critical loads). But a simple 1 phase load or in future an ev charger or heatpump require no further calculations on the device. It’s just storage in VRM to record consumption and create forecasts.
This may also explain why you cannot select the phase to which the shelly is connected. This was introduced a couple of weeks ago but for metering devices without switch only I guess:
v3.70~50 till 54
- Shelly support: add option to set which phase a single-channel Shelly is connected on
Thanks for the hints.
I have a hard time understanding why devices with a switch would be precluded from being used as an energy meter for a PV inverter though.
In fact I think that’s even what most people would want. Not sure about other countries, but in Germany small PV inverters with a standard plug are now legal so a shelly plug device would be the perfect fit for that job.
Update: Just created Allow pvinverter role for shelly devices that have a switch · Issue #16 · victronenergy/dbus-shelly · GitHub
To integrate ALL Shellys, please use Node-RED in combination with the “virtual devices” node and the “node-red-contrib-shelly” nodes. This allows you to integrate everything exactly as you want with minimal effort.
Want to assign the role of “PV inverter” to a Shelly? No problem… Select the phase it is connected to? Nothing could be easier…
For our German readers, the good “Helmut” at “Schatten PV” have published a very informative “how-to” video. This method gives you MUCH more flexibility.
Learn how to use the tools that Victron provides us with FREE of charge 
No good if you don’t have/ don’t want Node red
Thanks to Victron, EVERYONE has the option of installing the large image from VenusOS and thus using NodeRed without any detours. They provide you with everything you need to easily integrate hardware from third-party manufacturers with your own system (and that’s something you shouldn’t forget). I accept the reasoning ‘I don’t want NodeRed’, but I also say clearly that you will have to live with the limitations. At least some initiative can be expected from the user in such projects, and they will get to know their system a little better in the process
Of course, such seamlessly integrated solutions are nice, but this is certainly not the focus of software development, so it takes time and, in the course of mass production, may ultimately not be as flexible as the solution with NodeRed. Never forget that we, with our wishes, are individual cases in a huge pool of Victron users who don’t care about such things at all.