Hi. I’ve had my Cerbo GX stop communicating via LTE after a firmware update. The GX LTE reports online but VRM reports DNS failure to resolve name. The solution seems to be power cycle the GX LTE modem. I’m looking at creating a Node-RED flow that detects a Cerbo reboot and triggers a GX LTE power cycle.
If I run the power to the GX LTE through Relay 1 or 2 I can create a flow that will do what I want if Node-RED restarts and that will necessarily happen if the Cerbo reboots after firmware but it could also do it if it just restarts itself.
I found the Custom Input node which has a GX Device option and under that is /Device/Reboot
Default seems to be 0 which I’m seeing as “reboot false”. I’m asking whether after a firmware update that /Device/Reboot would go 1 “reboot true” and if so whether it would persist at all? Would it allow me to use it as a trigger for the flow to pause 3 minutes then open the relay for 15 seconds and then close it?
I already have that for the Cerbo but it needs the GX LTE modem rebooted to clear the DNS issue and that doesn’t do that (or at least I’ve not yet found a way to do it).
DNS faults are the ones logged. A power cycle of the modem fixes it. Even if there’s a nascent fault a power cycle still fixes it. It’s only happened when Cerbo reboots after a firmware update and, since I usually do it remotely via VRM it would be nice to get access back after the reboot.
Hey all. I’ve sorted it. This is the flow. The injects are for testing as are the time delays. The counter on the right prevents infinite power cycles in case I lose cellular cover and VRM drops off. The gate function reads the flow from the counter and stops further cycles once 3 have been attempted. It leaves the modem powered after the 3 attempts.
