Settings, Integrations, a menu for Shelly devices is there
Can’t recall that before
Do they work ?
What version is that? I don’t have that menu option.
Beta v3.70~19
I’m on v3.70~20 and don’t have that menu, I assume your GX device knows there are some Shelby devices connected (mine are in a box on a shelf so difficult to detect)?
1 Like
Yes I think you are correct. I have other Shelly devices - a Shelly EM that I use as a grid meter with a 3rd party driver. The EM does not appear
All of my Shelly’s are Ethernet so could be “seen”
Ah, you found it!
It doesn’t fully work yet, few more weeks.
And by then i’ll also know enough to explain the details.
5 Likes
And there i was, adding 3th party driver today and tough I have gone nuts where have got
supervise dbus-shelly to my system 
Anyway i could do some testing with shellypro3em400 and shellypro3em if needed.
1 Like
Does this have any consequences for DBus script installations? I am using the script from GitHub - fabian-lauer/dbus-shelly-3em-smartmeter: Integrate Shelly 3EM smart meter into Victron Energies Venus OS sucessfully, and certainly want to continue using it.
Probably not, but time will tell: you can tell me.
Its at least not necessary for this to create insurmountable conflicts. It can work.
We’re not actively testing ourselves with modifications/plugins.
Note that I’ll move your comment & my answer to the shelly v3.70 topic after answering
Hey,
do I understand it correct that there is an upcoming direct Shelly integration but grid meters are excluded?
Or is that only valid for CCGX and all other devices (e.g. Cerbo) will support Shelly EM as grid meter?
Hence I still have to use websockets or a script to use it as grid meter in an ESS?
Any updates on the Shelly relay integration ?
Hi,
I’ve updated the system to 3.70~45 to test the Shelly integration with my Shelly EM gen1 which is measuring the current from my PV inverter connected to Multiplus II Ac out.
The device is not detected, probably because it is not sending the expected mDNS name under _shelly._tcp.local. that the dbus-shelly service is expecting.
Capturing some traffic with tcpdump on the Cerbo GX shows what this Shelly is sending:
15:44:55.203771 IP 192.168.40.21.mdns > mdns.mcast.net.mdns: 0* [0q] 6/0/0 PTR _http._tcp.local., PTR shellyem-BCF(redacted)F4B._http._tcp.local., (Cache flush) SRV shellyem-BCF(redacted)F4B.local.:80 0 0, (Cache flush) TXT "id=shellyem-BCF(redacted)F4B" "arch=esp8266" "app=shellyem" "fw_version=1.0" "fw_id=20230913-114150/v1.14.0-gcb84623" "discoverable=false" "discoverable=false", (Cache flush) A 192.168.40.21, (Cache flush) NSEC (530)
Therefore I modified Fabian Lauer’s dbus-shelly-3em-smartmeter to adapt it to the EM. It is working great but there is a minor glitch in the new Cerbo remote console.
On VRM and the old console, the PV inverter is correctly shown on the output of the multiplus:
While on the new console the pvinverter is shown on the input:
But the information about the device is correctly indicating AC Out:
Best regards,
Raúl.
Please can you post what you modified as I have a Shelly EM as well
Hi dmsims,
Sorry but my modifications are an ugly hack at the moment, hardcoding the second input from the EM to be pvinverter.
I’ve seen that my modifications are complementary to this project:
Where Vincegod is hardcoding the first input to be a grid meter.
You can use his project if this is the config you have (grid meter, input 1). Otherwise, you can change his code on dbus-shelly-em-smartmeter.py:
- Lines 52-53: change role from ‘grid’ to ‘pvinverter’ and position from 0 (ac in1) to 1 (ac out) if needed.
- Line 222: change service_name from ‘com.victronenergy.grid’ to ‘com.victronenergy.pvinverter’
- Change every occurrence of [‘emeters’][0] (EM input 1) to [‘emeters’][1] (EM input 2) if needed.
I think this should work. If it is not working please drop me a response here and I’ll try to do a proper fork of the repo and publish it (but I cannot promise it’ll be soon).
Best regards,
Raúl.
Understood and I should have been clearer. I just use it as an Energy meter
I just need to understand how you fixed this: “The device is not detected, probably because it is not sending the expected mDNS name under _shelly._tcp.local. that the dbus-shelly service is expecting.”
Ah, sorry. I was unable to fix that, that’s why I had to use this as a workaround.
I’m not sure if Victron will consider devices not using the current Shelly mDNS naming but they just mentioned on the 3.70beta thread that it I’ll be possible to add Shelly devices by its IP address and get rid of mDNS which can be a pain in complex networks.
Best regards,
Raúl.
Hi all,
I had forgotten to add the details on the Shelly integrations properly into the change log. Apologies for that, it was added in bits and pieces over various versions; and I missed the final piece of the puzzle.
But as you’ve all seen its there now. Here are the high level requirements:
- Works with Shelly gen2 (and higher) devices. Devices are discovered with mDNS and GX connects to the shelly websocket endpoint.
- Devices will by default be disabled.
- We’re not supporting to use the Shelly as a grid meter. I’m aware that that will disappoint some people. The reason for that is when it comes to ESS and inverter/charger control; a lot of time and effort goes into making our various models, combinations and configurations work well; and maintaining and verifying that. And at this moment I don’t see enough value in officially supporting (yet) another type of energy meter.
2 Likes
In all 4 of my Victron implementations (Cerbo-S GX/Cerbo GX/Cerbo GX MK2) al on firmware v3.70~46 Large in is GUIv2 ,
There is no menu item Shelly Devices. All location have shelly Gen2 devices, on ethernet-segments .
IMO, Victron isn’t taking the needs of many users into account. It’s not specifically about Shelly, but rather the fact that many users need a grid meter that communicates via Wi-Fi. As far as I know, Victron doesn’t offer such a device and doesn’t support any third-party products. For me, for example, the grid meter’s Wi-Fi capability was an absolute prerequisite for choosing a Victron system, and I think many other people feel the same way.
3 Likes
Shelly are a great brand IMHO
They do a Wifi meter with CT that works reilably, is very fast! and economical
People increasingly deploy solar plant remotely (in a domestic scenario) due to noise and safety concerns