Teken

Let’s see if Michel can offer this information to save time spooling up Wire Shark to obtain the same.

That’s depending upon the model year it was purchased in. Early models behaved the way you just stated. While later models came back on upon power restore. There’s a use case for both so understanding why the third generation of last known state was a good balance.

I’ll test when I get back home what’s the REST command?!?

Safer is dependent upon its use case and application. I offered my feedback to insure others who may follow you or not consider the implications as to the possibilities of doing so. Depending upon what model Insteon bulb you have one operates as you noted in the on-off state. Whereas the later generations incorporated last known state.

Regardless it’s a feature that should exist and be accessible to those who wish to use it. Keep in mind if you need to regularly reboot anything there’s obviously a problem! The only time that’s not true is where something requires a hard reboot to update firmware as is the case in many industrial hardware. Then again if the ISY Series Controller used the same methods to flash it’s system it would be a game changer and offer more resiliency. This is coupled with sending real-time low level operating status that is linked to the various operations of the controller and not to a NIC just to determine operational status etc. Maybe one day!

This is done at the device level.

I was thinking about something completely different - thanks! I thought you were going to say when there was this huge push from the likes of Staples, HD, etc to offer their own hubs only to fail and pull out in less than two years! [emoji1787][emoji2357]

My answer still stands there isn’t anything I’m aware that allows us to automatically reboot the controller without human manual intervention. Whether that be from a smart application, cloud portal, Polyisy. All of them requires a person to actively press the soft reboot button.

That’s remote control vs automating the same via a script / program. As far as I’m aware no such feature exists where another computer can reboot the ISY Series Controller without human intervention. That also doesn’t address knowing 100% the controller is fully operational. Anyone who has seen their controller still run some programs / all. All the while they have zero control over the same via the AC can affirm this very scenario. Nobody serious uses only ping alive, heart beat, to determine a fully operational state. As it doesn’t offer that insight due to the dozens of other factors at play. Think someone pinging a box at home. Are you actually getting a response from the brains of said box vs the hardware NIC?!? Anyone who has ever experienced the Windows BSOD can tell you the box is absolutely bricked and yet you can ping it! This is why one doesn’t rely only on hardware level, software level, application level, transport level etc.

Some things to consider as it pertains to personal safety when considering automating. Things that control and manage water like the main feed, fire sprinkler, sump. Anything that manages the HVAC system. Things that produce heat like a coffee maker / kettle. To anything that moves or spins should not be integrated with a switch - outlet to come on by default. Unless you’re absolutely sure the same can not ever cause harm. In the various industries this is known as fail safe vs fail secure. As others noted many of these have built in memory to offer *Last known state* whether on / off. The vast majority of hardware in the past always defaulted to a off state (Fail Safe) due to safety and liability reasons. Fail secure devices are normally used for devices that must always have power to guard against adding to a problem. They are normally used on fire control, security alarms, fridge, freezer, sump, well, air exchange systems etc. Any device you believe offers fail secure (On when power is applied) should be validated as so by short cycling the device. This does not mean unplugging the device as you will never ever be fast enough to switch off the power from on-off-on! You either do this at breaker or wire it to a power bar with a toggle switch. You’ll quickly find out what you believe is Fail Secure hinges upon how much time has elapsed as many use capacitors to buffer their electronics to avoid unintended operations / change of state. Now with the growing so called cloud power devices you must be doubly sure to validate! There have been countless examples where the cloud was rebooted and caused a device to turn on / off! Well outside of what the device was set up to do in the past reliably. Think millions of people who had NEST turn off the heat in the dead of winter! [emoji2357][emoji1787][emoji107] Test, validate, confirm - don’t guess! [emoji3516]

It’s been a while refresh my memory about Wink? [emoji848]

Correct, I’ve seen the button in the portal but like you never seen a way to call this to action from another source. This is something that must exist in the Polyisy because there’s going to be situations where the box will be hung up and a remote boot that can be automated to remediate the same. Ping alive is not a serious solution or heart beat. Using a combination of both offers a little more insight but this too falls short in actually knowing the operating state of the controller! [emoji3516]

You have a link to this - never seen that before?!?

No current method to tell the ISY Series Controller to reboot. This feature has been asked for years I don’t know if it’s even on the endless *To Do List*.

One thing to consider which isn’t directly related to the problem at hand. But has plaque many routers in the past is how they handle friendly names. Some absolutely will freak out if you exceed the number of characters allowed. Others will drop off or won’t update correctly if special characters are used or spacing is present. As odd as this sounds a few in the past were bricked as when the router was rebooted and saw a label with the exact same model number as part of the friendly name extremely bad coding told the router to shut down or loop! [emoji2357]

It’s best practice to either assign a Static IP or reserve the same based on the MAC address but not both. Many routers allow a reservation within the DHCP Pool which should not be used. It should be outside of the DHCP Pool to avoid a IP conflict. Some custom firmware like Tomato and others depending upon version had a bug where it would duplicate the IP Address and obvious network conflict would ensue. This was famously seen on no less than three generations of LinkSys routers! [emoji107] Other things to consider while you’re rebooting all the network hardware is to clear all web cache / Java cache. Along with completing a IP & DNS Refresh / Renew on all systems so it will obtain the latest IP address either assigned or leased. Good luck! [emoji106]

Anything else on the network dropping off?!? If so that would really point to the router / mesh combo. Have you assigned a static IP address or reserved a DHCP address locked to the MAC address of the controller? If it’s just plain DHCP with no reservation hardware dropping off or not able to obtain a new DHCP lease is very common. This is more so where a network appliance does not follow and respect the standards where it must release and renew its IP address upon coming back on line / seen by the router. When such a problem exists this can create a IP conflict. Best case one or two devices can’t be seen and operate. Worse case it literally takes down the entire network! [emoji2357]

When did this start and what is the frequency of the problem of not being able to connect? What has changed in the network if any? How is it now being directly connected to the main router?

To be clear when you say can’t communicate this is from accessing via the AC? When the controller is in this state can you ping it on the network? Does it remain visible on the network router?

First thing to do is turn OFF internet access. It doesn’t operate as one would expect read the WiKi or search as to how that option when enabled is active.

If the starter kit includes the Insteon Hub you’re good to go. [emoji106]

From a three prong approach you can make a full ISY Back Up. Next back up the individual programs / network resources as they exist now. From there delete any unnecessary programs and save the same in those two steps outlined up above. A true test would be to delete everything like programs and import the same to validate this process works. I firmly believe it will so long as existing programs / network resources are not present. As an aside if you haven’t purchased a Polyisy this may also give you that needed room. As the Node Servers in their various flavours allows independent actions from using State / Variables and only focus on programs to act on the same. Just something to consider as you try to limit breaking that 1000 barrier! [emoji106][emoji481][emoji481]

Were you intending to import a backup on an existing production system or bare metal one? [emoji848]

Just going off memory as this has been a very long time since doing so maybe something has changed?!? [emoji848] You’ll want to rely on a restore ISY as a first line of defence if something ever goes wrong. RE: Export it works in so far as it allows you to back up critical programs, network resources, etc. RE: Import works on a new bare metal image or controller that doesn’t have the same. Keep in mind the operating system does not call out or delete duplicate entries! Meaning if you literally exported everything. Moments later said let’s try this on my production controller. You’ll quickly find duplicates of the same?!? [emoji2357] Maybe 5.XX has resolved this obvious problem??? [emoji1785]

Have you tried the AC for that specific firmware version instead of the universal Launcher?!? [emoji848]