Goose66

I can add that to the to-do list. However, I do not have this alarm panel any more so I will have to release a version with this feature untested. The next time we find a bug or something that needs to be fixed, I will add this feature.

I see no Bond trial option - just the purchase option. The submission was from a long time ago so it would have been something that was there, and is now gone. But more specifically, he is saying he selected Bond trial and got MyQ trial. When the Bond PG3 node server was initially released there was a trial and a purchase option. I can’t say for sure that I kept the trial option over subsequent releases, however. It is certainly possible that the OP thought he was installing a trial of Bond when he was really installing a trial of MyQ. But if that’s the case it’s mighty coincidental that such a mistake was made between two node servers from the same developer.

I don't see a Bond node server Trial option in the Node Server Store either. I see that when I first released the PG3 version of the node server I noted there was a 1-month free trial. And IIRC when I uploaded the latest version to the Node Server store, I uploaded it for both the Trial and the Purchase options. As far as the missing Trial option for the Bond node server and you getting the MyQ node server trial when you selected the Bond node server trial, those sound like database corruption problems in the Node Server Store to me, which we node server developers have no control over. That is a @bpwwer issue/question.

2. The "Thermostat Online" state basically reports the success or failure of the last polling call (updated every short poll).

1. The Venstar node server does not maintain a connection* to the thermostat where it can get real-time status updates. Instead it relies on polling to retrieve the latest status every short poll interval. However, unlike the MyQ or iAquaLink node servers, the poling takes place on your LAN directly to the thermostat and doesn't utilize a cloud service as a go-between. Accordingly, the polling call is not very expensive network-wise, and can be done frequently (defaults to 15 seconds). Therefore, there is no need for a "Force Update" command. If the 15 seconds is not real-time enough, you can set the short poll interval to 10 seconds or less. Note that the node server also updates the remote sensor states, the system runtimes, and the alert states every long poll interval. * technically it does maintain an HTTP session so that subsequent calls to the thermostat after the initial call are more efficient. But there is no two-way connection allowing the thermostat to update the node server with current status values in real-time, like the EnvisaLink-DSC or Bond node server.

3. If the EnvisaLink is not firewalled and can connect to the EyezOn web service, then you don’t need the “disablewatchdog” setting. This is also documented in the node server "More Info."

2. The “Alarm Panel Connected" reflects the status of the connection between the node server and the the EnvisaLink device. It is really only updated to True when the node server logs into to the EnvisaLink device and to false when the node server disconnects or attempts to send a command to the device and it fails. It’s not updated in real-time. The node server does have a heartbeat functionality, however. It sends an AWAKE command to the ISY on a periodic basis based on a periodic communication received from the alarm panel. The heartbeat functionality is documented in the node server "More Info."

1. Some background: If you “Query” a node from the Admin console, the node server will generally just respond with all of the current status values for the node. The node server doesn’t necessarily query the device for the latest values unless the node server programmer specifically overrides that functionality and adds the device query. The EnvisaLink DSC node server uses the default query approach. Further, the EnvisaLink-DSC node server generally doesn’t poll but instead listens for status update commands from the EnvisaLink device. Other than initial startup functionality, the only thing that the node server does on the short poll interval is update the zone timer values. What the Force Update command does is cause the node server send a command to the EnvisaLink device to resend all its status reporting commands with current status values, similar to what happens on startup. The node server then processes the commands as received. After a Force Update command it may take several seconds for the EnvisaLink to send all the status reporting commands and for the node server to update the ISY.

<rant> A “node” is an individual item (“leaf”) in the tree structure in the left panel of the ISY Admin Console. Nodes have states (“driver values”) and send and/accept commands. Each node usually represents a device, but a node may represent a group of devices, a gateway or hub, a connection to a cloud service, or even a node server instance. The thing you install, upgrade, and configure in PG3 is a “node server.” A node server creates and supports nodes in the ISY. Every node in the ISY that’s not native (Insteon, Zigbee, Zwave) has an associated node server managing the corresponding device. </rant> Thank you for your time.

I have looked at the API available for Schlage Encode lock and feel like it will be possible to build a node server for it. I started it about 3 months ago but, as I said, it fell off the radar. What I can't tell you is 1) will it definitely support Encode Plus (e.g., since it's homekit compatible may it be purposefully limited in what other APIs it supports) or 2) how long will it last (e.g., they could change or withdraw the API). Overall, many of my home automation projects have been pushed to the back burner since I moved last August and have since been waiting to see how Matter shakes out before diving in at my new townhome. I've also been working remotely at my vacation home a lot. I return from an extended absence in the second week of June and will try and look at it then.

From what I can tell, the API that the node server would us should work for any of these Schlage locks that use the mobile app and connect over Wi-Fi.

I installed a Schlage Encode Wi-Fi lock some months back and played with the API a little in preparation for developing a node server, but it just fell of the to-do list. Hopefully can circle back to it in a couple of weeks.

Looks to me like the ISY has lost connection to the node server and/or PG3. Did you just update your Admin Console (firmware)?

I am going to assume that "I can't get to the Admin Console" means you can't run the ISY Launcher from the icon on your desktop - if that's not the case, you can ignore. After installing the latest version of Java, make sure you clear your Java Cache. This is covered in the Wiki, but some of it is outdated. Here is what I suggest: 1. Search for "javacpl" in the Windows Search bar, and the results should include the "Configure Java" app (the Java Control Panel). 2. Run the "Configure Java" app as Administrator. 3. Under "Temporary Internet Files," choose "Settings..." and then "Delete Files..." 4. Make sure "Installed Applications and Applets" is checked, and then click "Ok." As it deletes the cache files, the ISY Launcher icon should disappear from your desktop. 5. Run the IoX Launcher from the Web at https://isy.universal-devices.com/start.jnlp. It may start in Chrome, but it will most likely just download, then you need to open it from the Downloads menu (or the Downloads folder). Once you run it from the Web once, it should put a new icon for the IoX Launcher on your desktop. 6. In the IoX Launcher, click (or double-click - it's a bit wonky) your Polisy in the list, and then select "Admin Console (LAN)." Hope this helps!

@drprm1 Received the DM with the log files. Good to know you found the "All Off" command and disabled it. That one really doesn't make much sense in the current ISY ecosystem because so many different types of devices are integrated in the controller. Looks like after the initial problem at 6:26 am the MyQ service behaved pretty well, i.e., if you sent an open command they went to "Opening" state and then "Open" state in a few seconds, and if you sent a close command they went to "Closing" and then "Closed" state. Hopefully the physical response you noticed in the door operation was consistent with this. From your door IDs, I am going to guess that you have the MyQ Smart Garage Control system and not actual Chamberlain/Liftmaster door openers. Because this system can only assume the open/closed state from the last position change transmitted by the sensor, it is possible that the MyQ service had a bad internal state and sent an activation to the door even though it was already closed. That would have caused it to actually open, and then when the sensor transmitted the state change, the state changed from "Closing" to "Opening" and then eventually to "Open." If you check your "History" in the MyQ app, it should show the Close commands coming through around 6:26 am yesterday from your name, and it would be interesting to see if there are subsequent entries with no name changing the state to "Open." Just to wrap up, the net-net is that I don't really see any To-Dos here for the the MyQ Node Server, and we just need to watch more carefully and see if this weird state tracking error (if that is what it was) happens again.

Thanks, @Geddy. @drprm1, try sending the log file to me again.

Oops, sorry. I meant to say that I can see I can't get messages and that I was asking @Geddy why that was the case. Maybe a little TOO MUCH shorthand. Anyway, maybe @Geddy will forward to me.

Hmmm.... @Geddy ?

There appears to be two things going on here (both which may be issues): 1. There appears to have been an "All Off" command sent to most likely all your devices. This is evident in that both of your garage door opener nodes received a DOF (Close) command at 06:26:50 am in addition to two gateway nodes and the MyQ Service node, which logged errors because they don't support Close (DOF) commands. This is (and has been for some time) possible from the top-level of the node tree. I think it is an artifact leftover from when 99% of your devices were Insteon lights. As is the case with most node servers, the MyQ node server uses the base On (DON) and Off (DOF) commands for actions, in that the ISY didn't support a lot of specific commands (like an Open or Close command) in the early days. That may not be the case now, but the MyQ node server has always used DON and DOF for open and close going all the way back to the Polyglot v1 version. But if the user goes to the top level of the node tree in the Admin Console and does an "All On" or "All Off," all of the nodes receive the DON or DOF command and will respond accordingly (or error out if DON and/or DOF are not supported). 2. It further appears that both doors received the Close (DOF) commands, sent "close" commands to the MyQ service for both doors, and then changed the status of the doors to "Closing" (again, as evident from the log entries posted). However, 10 seconds later the status returned from the MyQ service for at least the first door was "Opening." So, either something went wrong in the MyQ service in receiving the "close" command and it opened the doors instead, or the doors were opened, started closing, and hit some sort of obstacle and reopened after the command. This may be a harder issue to nail down, and would be best troubleshooted by changing the logging level for the node server to "DEBUG" in the PG3 Dashboard and then opening and closing the doors via commands from the ISY Admin Console (please allow a couple of minutes between commands so that the doors can get through the whole remote open and close cycles). Then DM me the log files. NOTE: changing the logging level to Debug WILL EXPOSE YOUR CREDENTIALS in the log file, so only DM me the log files and don't post any log entries here.

Ah, my bad.

This is one of the hardest things for folks new to programming the ISY to understand: Adding a condition to the "If" statement really creates two things: 1) a trigger event that will cause the program to run, and 2) a condition that will be evaluated each time the program runs that will determine whether the "Then" or "Else" branch is executed. So, for example, "If 'Holiday / Indoor Holiday 1' Responding is not True" creates a trigger event for the program of "Responding status of 'Indoor Holiday 1' device changes" and a condition evaluated at the start of the program to decide which branch to execute. Understanding this element, along with the "re-entrant" nature of the programs during Waits and Repeats is critical to effectively using the programming model of the ISY, and is the reason why you seldom end up using Else branches and often need two programs, with one enabled and one disabled, for getting programs to operate as expected, as is explained ad nauseum in many postings in this forum (and in the Wiki, I believe).

The If statement of the status check program should only fire when the the Responding status of the Insteon device (here, "Indoor Holiday 1") changes. AFAIK, the Responding status of an Insteon device will only change resulting from a query - that's the important bit. So you would need two programs. The first one would be the "polling" program and would be run every day to perform the polling (query) on some interval, e.g., every 10 minutes: Polling - [ID 0005][Parent 0001] If From 1:00:00AM For 24 hours Then Repeat Every 10 minutes Set 'Holiday / Indoor Holiday 1' Query Else - No Actions - (To add one, press 'Action') The next program runs each time the status changes. Each status change causes the program to be executed anew, cancelling any prior running instance of the program, i.e., sitting in the wait: Status Check - [ID 0006][Parent 0001] If 'Holiday / Indoor Holiday 1' Responding is not True Then Wait 30 minutes Send Notification to 'Default' Else - No Actions - (To add one, press 'Action') So if a query results in the Responding status of the Insteon device changing to False, then the program will run, the If statement will be true, and it will enter the wait (which should be an interval larger than the poling interval and the maximum acceptable time for your GFCI to be tripped). If the Responding status of the Insteon device changes back to True during the wait, the program runs again, cancelling the current wait, and falls into the Else branch, which does nothing. If the Responding status of the Insteon device remains False during the wait through all the subsequent queries, then eventually the Wait interval will end and the notification will be sent.

What I don’t understand about your programs is that there is no delay between the query and the running of the programs that check the Responding status. But it takes some time after a query for the ISY to mark the device as not responding. Does the program wait on the results of the query before moving to the “Run” commands? The beauty of the programs I suggested is that the polling (query) and the checking the responding status are uncoupled. As long as the program querying runs more frequently than the wait before the notification, it should work beautifully. It also gives time for multiple queries to take place with no response before sending the notification, thus accounting for occasional Insteon communication glitches (which may be frequent here).

Just tested this with a plug-in module, and it works. New Program - [ID 0006][Parent 0001] If 'Holiday / Indoor Holiday 1' Responding is False Then Wait 5 minutes Send Notification to 'Default' Else - No Actions - (To add one, press 'Action')

There does appear to be a "Responding is True" condition. Never used it - didn't even know it was there. Anyway, you probably need two programs: One that polls the device and one that checks the "Responding" status. The polling program could perform a Query action of the device every minute, and the status check program could have "If <device> Responding is False, Wait 5 minutes, then send a notification." If the Responding returns to True within the 5 minute wait, then the program will be preempted and no notification will be sent. Let us know how it works.