I want to control the AC outputs of the MultiPlus to be able to control the AC outlet I have installed. Without thinking I installed a 12v to 120v controlled relay thinking I would control it from the CerboGX. What is the best way to control outlets, I assume the Cerbo would be more of a in case I cannot shut off/on the MultiPlus.
What I would like to be able to do is:
1: Cut power to the outlet to force a power cycle for devices if I lose communication and cannot reboot them independently (used for failover)
2: To cut power to AC devices once battery levels get low, CerboGX and modem will continue to run off battery bank so I can see status of system.
I have the MultiPlus II 12/500/20 and a CerboGX.
What is the best way to do this? Also to be able to have some automations for it would be great?
Everything is wired up and working with breakers etc my only challenge is this and adding my shunt and connecting batteries.
Personally I like to use MQTT compatible smart plugs like tasmota firmware loaded ESP based smart plugs. I run the MQTT broker in the GX device and also Node-Red in the GX device to write the automation.
I appreciate the input, I was hoping to use an option that’s already built in. I can see I can control the inverter and charger On/Off/Charge Only/Inverter Only and I see a relay option too.
I know the CerboGx has a relay and I was hoping to use one of those if it makes sense ie: If battery voltage drops to xyz trip relay 1 for example. But the main question is aside from me manually doing it in the multiplus device can I set it up without a solid state relay and use the multiplus relay direct or do I need the solid state relay to trip it?
Should I set it up on the Cerbo or the Multiplus? Does one benefit over the other feature wise or failover wise? Ie: Cerbo is always connected but maybe the Multiplus locked up the Cerbo could still trip a device.
Like Gerd said, Shelly is really good has switching on their devices as well, so you can also control with the Cerbo relay if you want. If you need more relays on the Cerbo, there is an extender IO for the Cerbo that just came out. Node Red, smart switches like TP-Link Tapo work really well in Node Red, and you can make your own smarts in the apps. There is not really anything built in.
I ended up just using relay 1, its for override only. I am using a solid state 12vdc to 120vac relay for this. Its conveniently in the system reachable within 2 clicks. I just wonder other than having an on-screen display option (enabled/disabled) or switch to click on the screen how I can achieve this.
Overall im trying to keep this all on the one system with no “external” devices that can be triggered like thru Shelly’s website. If I have to reboot a system I can do so from the web with all devices, this is just an SHTF incident that the remote devices wont remotely reboot from a GUI that I can have them force cycled.
You can run shelly local with node red and disable the cloud. Its SHTF ready with the switch inputs that you can control from the cerbo. The switch input is also smart, long press, toggle short press for a few automations.
Any idea if the toggle feature would run from On to Off and back On within lets say 15 seconds? Might be worth looking at. Right now on my DC load side the modem and Cerbo will never power off but I would perhaps want to control the modem and possibly Cerbo for a power cycle if the GUI cant be reached. Do you have a specific model you recommend? On the DC side it would be 2 channels and on the AC side a single channel. Also I know Shelly makes relays with ethernet which is preferred but im out of space on the modem…. Whats the next best WiFi? Would it be reliable in a metal box if the box has WiFi via external antenna on it?
This is a remote system that will be hundreds of miles away. I can reach everything with a GUI and reboot it this is only for SHTF if something doesnt respond. My issue is IF I cant tell it to cycle and on a timed restart ie: 30 seconds I am screwed once I click off. Right now im using Cerbo Relay 1 and a solid state relay with heatsync and its great but maybe there is more to use the RedNode thats of benefit.
I am killing a 120vac circuit as well as a 12vdc circuit. Right now the 12vdc is always on but it will be pointless if I cant have it restart by itself. Perhaps adding a timed relay on the battery side would be more beneficial. Chances of the modem and Cerbo going MIA are probably 0.01% chance but it would be nice. Is there a benefit from switching my solid state to like RedNode? Maybe this is all pointless and I should leave it as-is. This is my first Victron system and im trying to make sure I cover bases.
The shelly uni is a 2 channel controller with lots of inputs and outputs to send automation from the cerbo relays. Can be DC-powered up to 36V. You can add sensors and measure voltage.
This is a 1pm there are built-in timers for auto on and off. The 1pm is a round red one the blue ones are good as well. I have not owned the latest gen ones, they might be even better.
They also have wifi backup so you can run 2 wifi sources. The AC din style 1 pm can host its own wifi I use that as a backup. I have my rpis and cerbo on lan as well as wifi so there are no outages. Its pretty solid and with node red you are unlimited. I also have a Shelly 1 pm installed in the water heater shield where the power connects behind the metal enclosure. It works fine at about 75dBm. Says it’s low but still works. I have a shelly 3em in the switchboard for the energy meter for ESS. Its a metal box into the concrete wall about 20m from the wifi mesh. It works fine.
I run a remote off-grid MP2 system that has comms via a 4G SIM card router.
I have recently replaced the router. The old one would occasionally (perhaps around 60 days) drop its connection to the ISP and was unrecoverable without a site visit (not a problem in my case).
I have configured the settings of the new router to reboot at 2am every day and haven’t had any comms drop out failures for months.
I suppose the drop outs were something to do with the router failing to keep alive the lease on its 4G connection with the ISP.
The other problem I’ve had only once in several years is when a load was left on inadvertently and the batteries drained below the cut-off SoC threshold. At that time all my PV was AC coupled so I was in a real catch22 where the PV couldn’t charge the batteries until the batteries were a bit more charged . Here also a site visit was needed.
I now have some DC coupled PV in addition to the AC coupled so if this drain-down happens again, the system will recover without intervention.
I see what everyone is saying about the Shelly’s. Looks like to use the NodeRed though I have to run a Pi instance or something? Not trying to run additional hardware or do a complicated integration. I have a ControlByWeb X-410 with logic and MQTT capabilities that I could use but that add another $300 to production cost and doesn’t make much sense hence why I was using the Cerbo relays.
As far as the modem dropping, I service hundreds of solar units and thats a real issue, as you said usually tripping out for service just to reboot. For my modems I would normally put in an auto reboot like I use to on the Teltonika’s however I switched modems to a quad band as a dealer and for my amazing price point and unlimited on all carriers I have to use their modem and there is not an option to reboot on a schedule or else we would not be having this conversation to begin with.
Was just looking at the easiest way to integrate a way to trip it IF needed. I think the Cerbo will likely never lock up, have there been issues with a Cerbo being unresponsive? Seems like the only way to be completely redundant would be to use something like an X-410 externally so if the Cerbo even locked up I could force reboot it. The modem is the real concern over anything else.
Again all this equipment and its capabilities are new to me so its a learning curve and this is the last mile for me.
So its looking like there was a software update recently (in the last month) and there is now a scheduled reboot option for the modem, issue is it looks like its daily. There is no selection for Daily/Weekly/Monthly. I will have to discuss more with them as weekly would be preferred. I know the X-410 can do this as well as reboot of the DNS fails. Not sure about Cerbo and what it can do in this regards. If it would reboot based on losing internet then that would be a sufficient solution as well.
You run Node-RED off the Cerbo by installing the large image. You can build a dashboard so you can control devices or relays, check status remotely. You could have a flow that pings to an external IP, e.g., 8.8.8.8, and if it does not get a response, activate a relay to switch the shelly on and off. You could also program a power cycle in Node-Red to switch the Shelly off, then on, for example.
Looks like as part of the new firmware they have auto reboot and under another section auto reboot on a specific schedule so ive worked around the issue for the most part. I just want a manual way to override it if needed. I know alot of people are talking about Shelly but the wiring is more complex than the X-410 where I can power it with 9v-28v and that will control all 4 relays for me and I can program logic like the PLC’s. It also has MQTT do you think this is something that could be added to the Node Red dashboard? Its 4 relays and 4 inputs which is great option.
I have no idea that looks really expensive. The Shelly is pretty simple to wire. The best one I like to use is the Shelly1pm. You have remote control over wifi or connect the switch to the relay on the Cerbo. You can use AC or DC power.
I just ended up rolling with the X-410 by the time I buy all the Shelly’s I need for 4 relays it’s the same cost but atleast I get logic programming and it’s one powered device vs 4 devices. I’ll continue to look into the Shelly but this is made for IOT and controls and at a cost of $12 a year for web access it’s not a bad option. If I forgo the inputs then next time it would be about the cost of 2 Shelly’s. They have units that are about $165 with 4 relays.
. Here also a site visit was needed.