ae7nm

I installed the new Ring node server recently . I have Policy. I upgraded to v 5.6.0 first then I enabled IOX capability. Then I followed the instructions in the email. The ring node server was installed, but it didn't work. On the control node, when I clicked on Test Ring the test results showed Failed. The programs I had written did not respond to the doorbell. After trying several things, I read the More Info page on the pg3x ring entry. It said that: PG3 Remote connection must be enabled Settings are in Portal under Select Tools | Maintenance | PG3 Remote connection When I did that, everything worked. Since not everyone will have Remote Connection enabled, you might want to make a note of this in the requirements and instructions.

It's working properly now. I'm not sure what update fixed it.

When I switched from an ISY 994 to ISY on Polisy, the set time command sets the thermostat to GMT rather than local time. The Admin console has the correct local time. All of the scheduled events work properly. When the set time command is run, the thermostat is set to the correct time in GMT. This command worked for years on the old hardware. I do not use thermostat programing so it's not a problem. It is weird. though.

Something new. I got around to disconnecting my old ISY 994 from the LAN. When I restarted the admin console, the Node server Online box was blank. There was no text at all. When I restarted the node server, the box changed to Connected then Disconnected like it has been behaving. All the other data is updating periodically as I expected.

If I restart the node server, it does not correctly display the status.

It shows disconnected on the Admin Console. Both PG3 dashboard and the node detail page show connected. Today I restarted OpenWeatherMap and it updated to 3.1.4. I rebooted Polyglot and restarted the Admin Console. It still says disconnected. Here is the log package. OpenWeatherMap_6-6-2022_70350_PM.zip

I was mistaken. After several hours of observation, it looks like OpenWeatherMap is updating the weather data even though the Node server Online status is "Disconnected." I am guessing this is some kind of bug. I noticed that another user noted this. The only problem it causes is that I have a set of programs that cause a fall back to a scheduled thermostat setback control scheme when OpenWeatherMap is not working. I just disabled them for now. I looked at the logs. They seem to make sense with no warnings, errors, or any evidence of the node server stopping.

I have OpenWeatherMap PG3 installed on a polisy. Node server Online says Disconnected. The polisy dashboard on Polyglot V3 says that its current status is connected. If I stop the node server then start it again, the Node server online changes to Connected for 1 or 2 seconds, the current weather data updates, then the Node server Online status changes to Disconnected. The current weather data does not update after that. The cloud version worked perfectly.

The UDI Wiki has a page about the IOLinc. It should contain information about this behavior. I am not sure if this issue originates in the 2450 or in UDI's software?

Brian H Seems like we are on the same page on this. Thanks for the help. Do you know how we can get Insteon/UDI to fix the documents?

I agree, referring the to the relay as activated or not activated makes more sense. The examples in the manual connect the loads through the N/O contact. I am not sure how to describe the state of a mechanical or magnetic latching relay, however. As an example of how you would the N/C terminal, traditional Lionel electric trains with transformer control interrupt track power momentarily to cycle through STOP, FOREWARD, STOP, REVERSE. One could connect the track power through the N/C contact of a I/O Linc set to a momentary mode to control a train's direction. The old X-10 devices used a relay that used cams and pawls to alternate between states as the coil was pulsed. They used feedback from the contacts to the IC to decide whether to pulse the coil or not. Sometimes they would pulse more than once. When you turned on a light you would hear a rapid click, click, click.... As I said, I am using version online of the manual (Rev. 1/21/2014) that I downloaded. I am reasonably familiar with all sorts of relays. I am a retired electrical engineer. I have a master's degree in electrical engineering. I specialized in instrumentation and analog circuit design. I also designed a lot of switching power supplies. At any rate I generally understand what is going on. I just try to keep it simple in my posts.

Thanks, Brian H. It's good to know that my observation is not unique. I think that stusviews just missed the point that the IOLinc does what is expected when the On Value is 100%, but behaves differently from other devices when its on value in a scene is 0%. The UDI WikI page for linking the 2450 IOLinc is silent on the subject. I just reread the Insteion manual (Rev. 1/21/2014) in hopes of enlightenment. (Does anybody read these things?) I could not find any description of behavior of the behavior in question. I wonder whether the difference in response to the ON Level in scenes is in the IOLinc firmware or in the UDI software. Has anyone noticed that on page 4-5 it states. Normally Closed-​-W​hen the I/O Linc output relay is closed, the Normally Closed and Common terminals are connected. Normally Open-​-When the I/O Linc output relay is open, its Normally Open and Common terminals are connected. This is an unusual meaning of "relay of closed," It is usually the other way around. These statements also seem to contradict statements in the rest of the document. At any rate the term closed is ambiguous in this context. It would be better to state what happens when an on command is sent and the state of the outputs when the status light is bright or dim. On page 10 it states "The I/O Linc Status LED will be dim if the relay is open or bright if the relay is closed. Based on observation and test the statements on pages 4-5 quoted above are wrong. In actuality, when the status light is bright (relay is closed), the Normally Open and Common terminals are connected together and vise versa.

Same as before. I am beginning to think that this behavior is an undocumented feature.

For most devices turning on a scene sets the included devices sets the devices as specified in the scene attributes for each controller device. Turning off a scene turns off all the devices in a scene regardless of their on settings. It appears that the 2450 IOLinc works a little differently. When I set the On Level to 0% (OFF) turning the scene off turns the relay on. Why? Is this and undocumented feature? Does it have to do with the state of the IOLinc when I added it to ISY? Here are some details: (2450) IOLinc v.41 ISY v.4.5.1 Latching Mode Relay follows Input checked Trigger Reverse is not checked nor are any other options checked The sensor input is connected to the flame on contact closure output of the remote receiver in my gas fireplace. The N/O and COM relay outputs are connected to the flame on inputs of the fireplace valve controller board where the remote receiver outputs used to connect.. I have a scene that has several controllers (Keypad Links and mini wireless remotes) that has the relay in the IOLinc as a responder. The scene also has the senseor of the IOLinc as a controller. All of this works great. I can turn the fireplace on and off with the wireless remote that came with the fireplace, from the Insteon controller, of from my Amazon echo. The lights in keypad buttons that are linked to the scene respond to the wireless remote control that came with the fireplace thanks to the IOLinc sensor being included in the scene. The status LED on the IOLinc turns on bright white when the fireplace is on, as expected. The IOLinc sensor state follows the output of the fireplace's wirelesses remote. I have another scene called ALL that includes most of the devices in my house. I use it to mimic the X-10 ALL Lights On and ALL Units Off commands. I set the On Level for some devices to OFF (0%) for some of the devices that I don't want to turn on when I turn on the ALL scene. This worked fine .for all of the devices but the IOLinc. Turning off the ALL scene unexpectedly turned the fireplace on. When I set the On level of the IOLinc to ON (100%) in the ALL scene and all of the controllers of the ALL scene, it fixed the problem. Except, of course, the fireplace turns on when ALL is turned on. Why does the IOLinc behave differently than other devices? Is there any way that I can keep from turning on my fireplace when the ALL scene turns on and still have it turn off when the ALL scene is turned off?