Yes I undertsand what you are saying but there is a whole world (in device terms) that Node red knows nothing about and it’s yet another learning curve!
OK:
- “I don’t have” is no valid argument, since everybody can have Node Red for free.
- “I don’t want” is no valid argument, since it is only your own problem if you don’t want a working solution for your problem.
However: a valid argument would be that you are already using another solution like scripts, and that you are too lazy to uninstall the scripts and go thru the learning curve for using the Node Red solution
1 Like
Node Red has a limited (very) view of my devices. Why would I want a half baked solution ?
Obviously this thread is about the Shelly support in Venus OS 3.70 Beta. May I suggest we stick to this topic here?
3 Likes
If Node Red is no solution, then of course it is no solution. But in many cases Node Red delivers a fully baked solution. Why would you neglect a solution to your problems and continue with a system full of problems?
I ordered a Pro EM 50A on Amazon yesterday - it was for 55.- € and try to install it as a virtual device as Helmut described in his Video and will report, if it works better than the Carlo Gavazzo ET 112
My Pro EM50 only shows up as a switch device, no energy meter.
Maybe that will change, but maybe not.
Which Shelly products will be compatible (relays, energy meters, sensors, smart plugs, etc.)?
Anyone else experiencing disappearing shelly devices if intermittent network issues happen ? I have three shelly devices using auto-detect. Same network, no static ip addresses. Did some maintenance on the network without touching the Victron setup and after bringing the network online again I lost the shelly devices. Needed to hit search and voila…. all good.
Thats the choice getting into the DIY matter, it does not stop at plugging something in.
The Shelly Pro EM 50A works perfect as a virtual device in Node Red
you should configure it first as 1 phase device - and when you are ready, change the it to a 3 phase device - just change the custom devices as you see in the screenshot……
As there is victron stuff in the thread - please change the handbook for the ET112 - to use it as a Inverter is not really recommanded, because you cannot change the L1 to L3 and Venus OS counts strange - I would not have bought it…….
Shelly gen3 PM Mini devices are still not found with the latest ~59. Adding them via manual IP configuration does not help. I believe someone also had discovery issues with the gen4 EM mini, which is the newer model from my devices.
I think PM mini devices should be high on the support priority list since they are specifically intended for power/energy measurement and not switching. They are exactly what you would use for a heat pump for example, where you do not want to lose heating due to relay going off because of firmware update or something similar.
Do not mind the Unifi labeling below, it is a PM Mini device and not 1 PM mini. The point is the IP and mac. “ILP” comes from Finnish words for an air heat pump. The shelly is in the same network and VLAN as Cerbo (MP2 GX) and VM-3P75CT.
Here is also a ping from MPII GX to the Shelly:
Quick comment on your ping from MPII GX to Shelly. Those are extremely high ping times for a device on your local network, most likely cause is too many disconnects reconnects from one or both of your devices to wifi.
ping from 1 device to a wifi access point in good condition should not be more than 4 milliseconds.
1 Like
Good observation, I was wondering about that a bit as well. Unifi system shows 0.0% retries to that Shelly. I did some further testing.
Ping from wired MP2 to a wired Shelly Pro 2PM:
Ping from wired MP2 to a wifi-connected Raspberry Pi CM4 device:
Ping from wired MP2 to a wifi-connected Shelly Pro 2PM which is very close to the AP:
Other Shelly devices showed high pings as well, while basically all other devices are fast to respond. I did some digging and it seems that Shelly Eco-mode affects pings a lot. When I disable Eco-mode, Shelly wifi devices respond fast. This includes the Shelly PM mini which is still not discovered by Victron, but at least ping is fast:
It appears that Shelly uses lower clockspeed and generally less power in Eco mode, so until there are actual adverse effects from Eco mode, I will continue to use it. I did verify that the Shelly PM Mini device is still not discovered by my MPII GX even with Eco disabled and fast pings.
1 Like
I found that when authentication is on, the Plus 1 (gen 2) I had was no longer discoverable, even with entering an IP address. I disabled authentication on the shelly Plus 1 and the device became discoverable again, but only through direct http polling by the GX. No mDNS/CoAP traffic from the Gen 2 shelly devices. I reached out to Shelly for support and they are investigating.
Some feedback about the Shelly Integration - v3.70~60
This is a but would need some little fine tuning:
I have connected this 4xpower plug to VRM, but IMO this behavior should be the same for all multichannel Shelly devices.
and getting this picture:
All for plugs / channels are shown, but you have no clue which channel ist what.
(If you change one Name , all four names are being changed
It might make sense to have a combination of “SHELLYDEVICEName” && “ChanelNAME”
please add the following information from here information, so I have an Idea, which channels is what
And a litlle feature request that would help:
Could you please add the power used of the (Shelly) devices also to the Switch panel - So you could decide on the Wattage which channels are to be switched off (in case you want to save power).
(The info is already shown on the “device” list (my 2nd picture), but you cannot act there):
Thanks
2 Likes
Have implemented this with NodeRed
1 Like
Great, so I am not the only one - Have also addressed this topic to the Victron team @Metstrade yesterday…
So let’s hope it will be addresses.
@Victron (thanks for the beer & snacks at yesterday’s 50year party in Metstrade Amsterdam….)
if not I can live with my NodeRed solution 