We have a number of M4315-Pro units in the field as we use them on every new project.  I'm a bit confused about the various re-boot options.  I'm not alone, their tech support is a bit confused as well...

The option that's most important to us is the notification and power-cycle when the internet goes down as per the unit ping settings commands.

There are two ways to accomplish this:

The first is to create a ping query on the "Network Management" page found of the unit/location home page.

I was once told to use Google 8.8.8.8 as the ping address and then set outlets to cycle if a ping fails...  I was then told to not use Google, but rather an inside address such as the router address: 192.168.1.1

The thought being that the Panamax server is pinging from outside the LAN so it could still see an 8.8.8.8 so using an inside IP like 1.1 would be more accurate.

You with me?

The other option is to set an "Auto Reboot Setting" sequence on the unit itself that will begin the sequence of my choosing (modem... 5 mins later... router, etc.) "when the device loses connection to the BlueBOLT servers"...

Support (nice guys don't get me wrong) told me when I asked if we should do one or the other said, "I don't really know.  Sometimes these things are added and it's not really thought through..."  Hmmm.

One thing to add, and the reason for my tech support call today, is a unit is sending me false positive Online/Offline emails.  I can tell if the internet is down as I can see the remote IP cameras on my phone...  Telling me that the are, in fact, online.

So what type of configuration are you folks using??

Look into ovrc. I found a lot of the time, I was getting incorrect status on bluebolt when I logged in.

Using the router doesn't seem correct, it can be used as another test but what happens if the modem is down and the router is fine responding to pings as it should. You still have no internet. I asked a rep from Panamax yesterday if the M4000 pro ping query can trigger a reboot if the ping fails (from being disconnected from the internet). I was told it can, it doesn't need to communicate with the server to trigger the reboot. I really wish these things had detailed logs and more thorough emails.

IMO the best way to reboot a BlueBolt is to unplug it from the wall, and then install another brand. Every single one we installed since they brought them to market either failed, would not auto boot properly or would constantly spit out annoying false network down emails. Maybe you have a better experience...but from the sound of it, you're getting the same exact response from TS we were 3 years ago.

If anyone discovers a rock solid (meaning i dont have to replace them every 12-18 months) solution for controllable (IP preferred but i will take anything at this point) power/surge strips please share.

If you're like me, you hit the blue button for your device- and wait, and wait, then you hit it again just as it goes dark- and repeat...