Ed Sybesma

Thank you. I had been under the impression that the heartbeat only sent an ON signal and not could not send an OFF signal if the battery was dead. I now understand, however, from the earlier e-mails that it does send OFF signals before the battery dies.

I have been using the programming logic supplied by Techman for several years with my Leak sensors. This sensor happens to be an open/close door/window sensor. I can see that I may use the logic from MrBill in the future, and either of these can be used as workarounds for what I am seeking to do right now. However, I have a more basic question: What event or other circumstance causes the ISY/Polisy Status to change from ON to OFF in the display for the module in the Main tab of the Administrative Console? Partial screenshot as follows:

Thank you for that information. Are you saying that the heartbeat signal status switches between ON and OFF due to something in Polisy or due to the Insteon module? It is my understanding that Polisy/ISY do not query this particular wireless Insteon module and that the only heartbeat activity in the module is to send out a signal approximately one time per day to indicate that the heartbeat is still working. I have a program which notifies me when that signal is reached and indeed it does tell me of that once a day. I actually have two of these Insteon modules working and the status shown under Polisy does not change back and forth for the other one.

I have an Insteon 2843-222 Open Close Sensor installed under Polisy. In the Main device listing tab of the Administrative Console, it shows up as 2 devices, 1 for the sensor itself and the second one for the heartbeat. The sensor is working properly, so I know that it should have a heartbeat and I also receive a heartbeat signal approximately daily. Nevertheless, the Device listing for the heartbeat in Administrative Console frequently changes back and forth between ON and OFF. I do not have any programming commands which attempt to alter the setting for or query the heartbeat device. In fact, I don’t think either are possible for this device. What could cause this Device heartbeat item to switch OFF?

The Insteon business has been purchased by new owners and is now separate from Smarthome. According to an e-mail received July 12: Dear Smarthome subscriber, Hello, my name is Ken and I'm the CEO of Insteon Technologies, a new company made up of a small group of passionate Insteon users that acquired the Insteon business. Together we are committed to responsibly re-building the company. Our commitment to you, the Insteon family, is to listen, communicate and be as transparent as possible in everything we do. You are receiving this letter because you were a subscriber to the Smarthome email list. Moving forward Insteon is no longer connected to Smarthome and therefore no further email communications will be sent to this list. To continue to receive emails relevant to Insteon, click the Subscribe link below to join the Insteon Newsletter. Subscribe We look forward to sharing more Insteon news with you there. Kind regards, Ken

Interesting. I would not have known that from the thread on this topic. Thank you for making it known and @io_guy for "making it".

Yes. That solves the issue. I did not previously understand quite what was going on. I now see that the fourth line of the original input was directing me to the web config server. Thank you very much.

Those numbers did in fact properly appear in the first place. I just concealed them with x's just in case (contrary to my expectation) they could have been used by anyone to hack my system.

Thanks again for your help. Unfortunately, the last tip doesn't seem to be helping. I have 16 web.config files on my drive. Some of them are human readable and some not. None of them are new enough to have anything to do with running the NodeLink. Of the ones that are readable, none have anything to do with NodeLink or ISY. What am I missing?

Thank you so much. That is a great start. When I run either "dotnet NodeLink.dll" or "dotnet NodeLink.dll NodeLink.runtimeconfig.json" (within a folder where all the files are located), I get the following result ( with some numbers intentionally concealed with x's here): 2022-04-10 16:13:35 - ISY NodeLink Server v0.11.3 started 2022-04-10 16:13:35 - OS: Microsoft Windows NT 10.0.19044.0 2022-04-10 16:13:35 - Installed .NET Runtime Version: 5.0.15 [5] 2022-04-10 16:13:35 - Web config server started (http://192.xxx.xx.x:8xxx) 2022-04-10 16:13:35 - No password specified for the ISY 2022-04-10 16:13:36 - ISY resolved to 192.xxx.xx.xx (5.0.16C) The Windows Powershell Administrator window then freezes and nothing else obvious happens. So it looks like I have gotten to the first step properly, but something else is missing. Any further ideas?

Thanks. I do have a dedicated Windows machine running 24/7. What do I need to do to run NodeLink on Windows?

Thank you for that input. Follow-up questions: I am using windows. I have previously loaded nodes for ISY through polyglot cloud. That now is unavailable. I am not otherwise familiar with running this type of file/program. What do you run/load NodeLink with: Polisy? Docker? Or? The instructions for NodeLink say: Download and run the latest version of NodeLink from: http://automationshack.com/Files/NodeLink.dll http://automationshack.com/Files/NodeLink.runtimeconfig.json Neither .dll files nor .json files run directly from Windows. I am obviously missing some basic background here, but my search of the Internet has not given me any answers. Thank you much for any help you can provide.

The Program Summary tab Shows the most recent run time and status result for programs. Is there any way to keep or obtain a log which shows the history of previous runs, similar to the Log of device events available under the Tools menu?

Well, I hate to say it, but even Luddites who do not directly themselves use cloud services or even a computer are nevertheless fully dependent upon cloud services-- or at least the Internet. If the Internet goes down, we probably lose our electrical grid or at the least our banking system, much of our interstate or international commerce, and many other systems we depend on.

I am on the West Coast, and it is affecting the West Coast as well. But what about polyglot cloud? AWS should not be affecting that, should it? Are others having trouble logging into polyglot cloud?

I have received occasional Alexa responsiveness this morning, but rarely. I also note that I cannot log into Polyglot Cloud.

hart2hart's experience and comments very well match my own, starting with the transition from X 10 to the SH introduction to ISY. In the early years with Insteon, I experienced product failures with a number of their modules, including the PLM. Product quality has definitely improved, and it has been maybe 5 years since I have experienced any Insteon module failures with one exception which was replaced under warranty.

Thanks to several of you for your reference to chip shortages as a likely explanation. I had read about it in the context of automobiles, computers, and the like, but failed to connect it to this issue. Perhaps the problem is even more pervasive than reported in the articles I have seen.

Based upon the increasing lack of available Insteon devices for sale, as well as the Insteon communications and other problems noted in the thread above, the question is whether Smart Labs is going to drop the Insteon product line entirely. Has anyone talk to them about possibly buying out Insteon? They certainly do not seem to want to pursue that line of business.

Excellent suggestions both. UDI support has always been very good, but so many others are so bad that product support is often the last place I think of to go for help. I did try unlinking and relinking the skill but, alas, that didn't help. So, on to UDI support. Thanks once again.

Bumbershoot, thanks again for your reply. I have rebooted everything in my house (including my ISY) multiple times. My ping times are similar to yours: Approximate round trip times in milli-seconds: Minimum = 74ms, Maximum = 75ms, Average = 74ms Based upon your last line, regarding ISY Portal not resolving correctly, I am guessing that the best test of that would be to simply delete my account and create a new one. (Talk about what force!) Unless you know an easier way? And, again, thanks so much for your help.

As a follow-up to my original post, and in partial response to the reply of Bumbershoot (thank you), I have put my local Internet service through multiple tests. It is operating dependably with high reported upload and download times and low latency. I have been using it extensively for other purposes and have had no problems. My ISY appears to be working perfectly. My Ring doorbell, which is connected to Alexa (not through ISY) is working properly. MobiLinc Pro is working properly (through both cellular and wireless connections). My LAN is working without problem. As best I can tell, I have ruled out all of the other obvious potential causes of this problem, yet it still persists. Does anyone have any ideas what else I might test? Thanks in advance.

For at least the last three days, I have had difficulty accessing or using ISY Portal, especially to connect to Alexa. Often it will not connect to my ISY at all. When I am connected, at least briefly, I receive various error messages including 500, 501, and others I don't recall currently. At other times, the connections to Alexa are very slow and Alexa returns (several different) verbal error messages. Sometimes Alexa commands don't work at all. Other times they can take 1 to 10 minutes before execution. Is this a known issue?

1. Regarding OpenWeatherMap.org: it takes about one day for your registration with OpenWeatherMap.org to go into effect. It will show disconnected during that time but will later connect automatically. 2. But why is the OpenWeatherMap.org discussion contained in a Ring Polyglot Cloud discussion thread? Shouldn't there be a separate discussion thread for OpenWeatherMap.org or for simply Polyglot?

Paul, thanks very much. That rounds up my understanding and it works as described. UDI might want to put some of this into its basic UDI Wiki. Ed