Teken

I have no doubt of your sincerity but wanted to affirm if you intend to interrupt the hot water supply to end devices please ensure that piece of hardware is certified to do so. You don't want to find out 12 months later the valve seized because the material isn't hot water approved.

Well, much success to you if you can. On a more serious note I've been working with the Aquanta team to finalize their HWT controller. In your use case with this device you could literally turn off the hot water. Keeping in mind when I say turn off it simply kills the power so what ever hot water is in the tank would still be used until fully depleted. To physically turn off the flow of water the device you're considering must be hot water approved. I don't recall what the criteria is to certify a piece of metal is hot water approved but there is a spec for it.

LMAO . . . Sorry Dad, but you have about 18 years of that happening . . .

To what end?

What exactly is the use case here? To ensure a person is never left in the dark?

Well, despite my rants about Google one has to concede and acknowledge they offer some of the most robust and reliable services on the planet. Got's to be honest . . .

As I stated pinging a PC regardless of the method does not address if a computer system is in a unknown state. This is why its not used in Enterprise / Government as the final indicator. Human - is and always will be the final indicator to the operational status of a system. Until SkyNet . . .

PhanTimiZ, Only trial and error will flesh out if this works as expected in your personal environment. Since its obvious you know the pros / cons the decision is yours. When you have time I am sure you will get that box squared away to a fully operational state. In the meantime I do hope you follow up and let the forum members know how you progress and what the final outcome is. All of this is great information for those needing a similar solution . . .

How would that help the OP determine (IF) the PC was in a *Unknown State*? Meaning all of us have seen and experienced where a computer refused to launch a application, shut down, to uninstall. What you propose makes sense in general terms of offering a possible method of detection but heavily relies upon multiple things working as expected. My question to you is this say the OP purchased the DLI remote switch and pinged some random *known* service like say Google. What does pinging Google from that appliance have to do with the PC that is hung or none responsive? Or how about the other way around so what ever application you just installed to ping some random site does reply back to the ping. How will that application running in the foreground / back ground address the fact the computer is frozen? Keeping in mind there are many levels of *Frozen* in the context of computer systems. All of us have seen the ISY lose connection in the Admin Console yet we all know in the back ground its still operating but the UI isn't displaying anything meaningful to the end user. I hope everyone reading this reply fully understands my only intent is to ensure they go into any software solution with both eyes open.

Pinging a network device in general terms is OK but should not be relied upon to determine a systems operational health. One only needs to Google to see one of many scenario's where a computer system will indeed reply back. But in every case the system was in a unknown state. This is why *Human* will always be around until SkyNet.

I believe lots of this comes down to how much do you want to spend. What are you willing to compromise on in terms of long term use vs reliability. Lastly, my belief is anything a person uses must continue to operate in a fail safe mode regardless of any HA integration. The HA aspect simply offers alert notification, additional program logic, and a measure of fail over. Regardless of what type of hardware is in use always test, validate, and follow up.

I believe given the critical nature and role of this computer system this is just a band aid to a larger issue not being addressed. From a IT perspective you're only buying time and the final outcome will be a failure. From a security perspective you leave yourself open to a window of time where you believe the system is recording and it won't be. My advice is determine what's the root cause of the issue and resolve it. It doesn't matter if its the OS needs to be re-imaged, to bad memory, HD, PSU, to even one of several application conflicts. To simply running out of resources due to resource hogging applications running in the back ground. Keep in mind *Ping Alive* is not a solve all because it relies heavily on one aspect of the OSI layer. A system can in fact ping back and the system will still be frozen . . . As Scott indicated you can certainly just gamble and take a random reboot sequence. Ultimately you are going to pay now or later . . .

For informational purposes only if you load the firmware that is listed for the Z-Wave / ZigBee. This will allow the ISY Series Controller to ignore a bad or missing PLM. ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

I love the KISS method of this solution. Thanks for the long term follow up! It's safe to say not a lot of folks take the time to do so! Pretty awesome pausom! [emoji106] ========================= The highest calling in life is to serve ones country faithfully - Teach others what can be. Do what is right and not what is popular.

Yes, as I recall UDI didn't want to make the portal a conditional logic infrastructure.

This and a similar discussions was asked about several months and was rejected.

Hello Drew, How old is your Insteon network and how many devices do you have in the home? Can you offer the model number of the Insteon devices you have as this will let us know more. On the Admin Console it may also tell you if the device is dual band in the center of the window. NOTE: If you successfully added the 2440 remote you can remove the tin foil.

Hello Drew, The following reply is mine alone so take it for what its worth. 1. My understanding is the latest PLM emits too strong of a RF signal and thus is causing all kinds of grief for those having a 2440 remote. 2. You can certainly try to move further away but would offer to you its just easier to place some tin foil over the PLM and do the same and see if it adds. Keeping in mind you must be near another dual band RF device.

You can't query a battery operated device it needs to be in linking mode to do so. If there are red exclamation marks the device didn't fully add into the system. Place the unit into linking mode again and do a restore device . . .

Hello Drew, The first couple of things of house keeping need to be done to ensure this is as painless as possible. If in doubt ensure the batteries are fresh and good to go. If so take the 2440 remote linc as far as possible from the 2413S PLM even if its in the garage etc. Place it into linking mode and then go back and try one of the two methods for linking. One is using the 2 blue / yellow whirling arrows and the other is with the light bulb where you enter the Insteon ID.

Good catch Brian - I keep forgetting for what ever reason the 2440 has a hard time being added into the network once a new 2314S PLM is replaced.

Hello Drew, Its been awhile since I linked the older 2440 but are you in fact holding the dim & bright button to place it into linking mode? Pressing any other buttons is intended for direct linking to other insteon devices. Meaning using that method assumes you have no controller like the ISY Series Controller and those links are created outside of the knowledge of the controller. NOTE: For the benefit of others in the future to place the older 2440 remote into linking mode. Press and hold both dim & bright buttons together until the LED flashes. This will place the remote into linking mode which the full users manual doesn't seem to address?

Hello Drew, I'm not sure if I understand your problem but once any remote is added you will see the separate nodes on the left hand side of the device tree. 1. You will then create a scene and call it what ever you like. 2. Then you will drag what ever remote button(s) to the newly created scene. 3. Any linked devices you wish to participate in that scene will also be dragged and dropped. Obviously you need to place the remote into linking mode and the LED will flash accordingly if done correctly. The system will automatically make the links and associations that's it. It sounds like you're mixing up doing a manual direct linking opposed to using the controller.

Ouch that's going to hurt if your not on a well! I would humbly suggest you consider installing one of those units that can be programmed for flow / time instead. These simple devices just work and doesn't rely on complicated networks and computer systems.

The appended link I just added speaks about the different methods to access the Admin Console. You have the choice of using a browser or the Java applet. Trying both will rule out something odd happening and might very well let you access the controller to see whats going on. The other portions of the WiKi discuss the different options from small to large invasive techniques to access or hard reset the controller in case you believe its gone bad. This is highly unlikely but I offer this in case its something you're considering. NOTE: If you read the WiKI it speaks about the single red error light and indicates it could be a bad SD card or improperly seated one.