Goose66

Looking through the history I don't ever see that there was a version 1.0.5. It jumped from 0.2.5 in Non-Production to 1.0.6 in Production (the latest being 1.0.7). If I recall correctly, the latest version 1.0.7 still supports the use of a personal Google Device Access Project. If everyone is amenable, I can upload v1.0.7 to Non-Production.

Also, it appears the partition node is already receiving an event (command) when the partition is disarmed, but it is currently labeled "Alarm Restored." Instead of the complex code you posted for determining disarmed, try: If 'DSC PG3 / Keypad MDPA' is switched Alarm Restored Then <Partition has been disarmed> The name of this command can be changed from "Alarm Restored" to something like "Partition Disarmed" when we make the other change(s) if this works.

Took a look at your log and sure enough it's a bug. Your EnvisaLink sends a "Partition Not Ready" for partition 1 but then follows up 3 seconds later with a "Partition Ready – Force Arming Enabled." The description of this command is the same as "Partition Ready," but I am guessing it has something to do with all the open zones that are configured as "non alarm zones." Paradoxically, the current code actually checks for the "Partition Ready – Force Arming Enabled" command and handles it the same as a "Partition Ready" command, but for what ever reason, the "Partition Ready – Force Arming Enabled" command doesn't make it to the state handler for the partition node and is instead marked by the API as an "Unhandled" command. It's a simple fix. However, it's been almost 3 years since I touched this code and a lot in the environment has changed. I'm not sure if I need to bring this one up to new standards or just make this one change and push it out. Bringing it up to new standards would mean less likely that it would be blown up by some new PG3/IoX release. I could also implement some other todos, such as upping the password to 10 characters, adding names to the state (driver) values, adding additional events (commands) for "Partition Armed" and "Partition Disarmed", adding disarm with custom user code, etc. But the problem with doing all this is I have no way of testing it because I don't have a DSC panel anymore. I would need to get a VPN setup to somebody with a DSC panel and EnvisaLink to test/debug changes. Just implementing the "Partition Ready – Force Arming Enabled" command handling would be easy (one line changed) and would (hopefully!!!) not introduce any bugs so I could just push it out. What do you think?

As to NodeLink "reading" the number of zones and partitions configured, this is not a feature of the TPI (API) presented by the EnvisaLink, so don't know how it was doing that. Similarly, a status of "Disarm" vs. "Ready/Not Ready" is simply a difference in the way the EnvisaLink-DSC plugin is designed vs. NodeLink. The EnvisaLink sends a "partition disarmed" command but that's generally immediately followed by a "partition ready" or "partition not-ready" command. Perhaps NodeLink handled these states separately. The Plugin does send a heartbeat every few minutes. From the document linked above: Don't know about "non-Alarm Zones" - never experienced or tested that. Perhaps you should try specifically bypassing these. I will try and take a look at the log files tonight to figure out why the partition never goes to "Ready".

First, a caveat: I no longer have a DSC alarm panel with an EnvisaLink so I have no way to test changes or updates to this plugin anymore. That said, the installation/configuration instructions for the plugin are here: https://goose66.github.io/nsdocs/evldsc-pg3.md Answers to many of these questions may be found there. Spcifically: 1. The EnvisaLink does not provide a way to retrieve the panel configuration. You must configure the number of zones and partitions in the Custom Configuration Parameters, if different from the defaults. You must set the number of zones to include the zone number of the keypad connected zone, even if there are not intervening zones. 2. The command outputs came be configured on your panel to be in toggle mode or on/off mode, depending on your panel series. Unfortunately, as I mentioned above, there is no way to retrieve the configuration from the panel. So the plugin only support command outputs came activation, which toggles the command output on and then off based on the configuration of the panel. Once activated, the EnvisaLink will never clear the active status, so if always says active. 3. For partition state and zone statuses, this all worked several years ago, when I was using it, so I can’t really provide any insight on what may be happening without seeing any logs. But I will say it may just work differently from NodeLink, so if you can recreate a set of conditions and generate a log file in “Debug” mode, I can tell you if it is working as designed or not. 4. If the partition state never returns to ready when disarmed, this may be why the last disarming user is not set.

I believe the point of calling these features out is that they specifically don’t need the ZMatter dongle. The ZMatter dongle will allow the eisy to communicate directly with Thread-based devices. But Matter is supported on other networks besides Thread, such as Wi-fi. Thus Wi-Fi direct to Matter devices (what I’m waiting for) and wi-fi through hub/bridge to Thread devices can all be implemented in eisy by software update alone, requiring no Thread hardware (ZMatter dongle).

This is still on the to-do list, but the steps were daunting (and potentially expensive) and I had other lower-hanging fruit to go for. If anyone wants to use in the meantime, I encourage you to setup your own Google Developer account and Google Device Access project to use. The instructions in the plugin release notes are detailed and refined.

It’s deja vu all over again! 🤪

You should be able to wire the ratgdo to use the discreet open and close terminals on the gate controller. There is a diagram on the ratgdo wiring page here: https://paulwieland.github.io/ratgdo/03_wiring.html. However, as Guy Lavoie said, monitoring open and close status probably won't work, unless you have the expansion board and use the aux relays or you install separate open and close limit switches (e.g., microswitches or reed switches).

Nodes from plugins should be deleted in the PG3 Dashboard, not from IoX Admin Console. The node list is stored in the PG3 database and most plugins recreate all of the nodes from these database entries when they restart. If you delete a node from the IoX Admin Console, it will just get recreated when you restart the plugin. Deleting it from PG3 deletes it from IoX as well. This is a known limitation in the PG3 system. Once PG3 is absorbed into IoX (v6?), this should be cleaned up.

@Javi Is there a workaround for the missing scroll bar here? Edit: sorry, that should have been for Chris Jahn. Don’t know his handle.

I guess I wasn’t appreciating that there was no scroll bar for the window. Yes, that is a serious UI issue. Very surprised it has gone this long without being fixed. Also a little surprised that the Java UI libraries don’t just automatically handle it. Could it be as simple as a flag in the window creation code? If we could just get Admin Console moved to a web-based UI… maybe IoX 6?

This is one of those "You can’t please all of the people all of the time" sort of things, I think. For those that want the runtimes, then there's no way to make it optional, I'm afraid. But I am surprised that you use the Admin Console for day to day management of your thermostats. The Admin Console is really designed for ... you know ... admin. Try UD Mobile. This should provide a better interface for making day-to-day settings on your thermostat.

Got it. Follow the instructions to the letter - particularly in the listed order. Good luck in the storm and keep your head down!

As Geddy posted, there’s currently a user limit on the Google side because UD’s Device Access project is still in “Commercial Testing” status. This process is not well documented (at least not publicly) so we were unaware. Looks like you may have been user # 11. We can do one of two things: 1) help you set up your own Google Device Access project in a personal sandbox (instructions in the Instructions and Release Notes) or 2) look into getting a refund for your purchase.

Also, remember that you can use the Nest SDM plugin with your own personal Device Access project created in a private Google Developer Sandbox. Instructions for that are in the Instructions and Release notes.

The UD Google Nest Device Access is stuck in "Commercial Testing" status until a number of authentication and API tests can be completed and verified. Until all this can be done, we are limited to 10 users, which we hit several weeks ago. Accordingly, I have taken the Nest Plugin off the Plugin Store List (marked "Inactive"). If and when the various battery of tests are completed, we can move it into the next phase of "testing" (not production yet), requiring even more rounds of verification testing, including a paid 3rd party security audit, evidently. But we should get a higher user limit at that time.

I'm getting that too when I try to reauthenticate. However, the API access and push events all continue to work on the previously obtained tokens. So I think it has something to do with our OAuth Authentication process to the Google Device Access project. None of the settings have change, so I have asked @Michel Kohanim to review the status of the project. Unfortunately, Google never fully integrated Nest Device Access into their Google Cloud Platform, so status of Device Access project is in a different environment that only he has access to. It was done that way for good reasons - just inconvenient sometimes.

Everything from our end shows still active. I would suggest trying to Authenticate again. If the problem is still happening, I can uninstall and reinstall my production version of the plugin and see what I get.

What type of firmware you running? MQTT or ESPHome?

Working on a Shelly plugin.

The plugin uses Simple Service Discovery Protocol (SSDP) to discover the thermostats which should work as long as the thermostats are on the same LAN segment as the Polisy/eISY. Once discovered, the plugin stores the IP address for each discovered thermostat, and when restarted, uses the IP address to access the thermostat so they don't have to be discovered again. So if your thermostats' IP addresses change, you will have to rediscover them. That said, simply assigning them a fixed IP address (assuming you mean DHCP reservation) shouldn't stop SSDP from working. Here are some things that could make SSDP discovery stop working: 1. Setting the thermostat to a fixed IP address in the thermostat setup screen, if you either a) set it to an IP address that's not on the same LAN segment, or b) accidentally disabled the "Local API" setting when making the change; 2. Have a Custom Configuration Parameter with key of "hostname" set to anything, such as one or more of the old IP addresses. If the "hostname" Custom Configuration Parameter is present, the plugin will bypass SSDP discovery instead try to contact a thermostat at the hostname(s) or IP address(es) listed in the parameter's value. You can either delete the Custom Configuration Parameter and try Discover again, or set the "hostname" Custom Configuration Parameter value to a list of the new, fixed IP addresses of your thermostats (separated by semicolon - no leading or trailing spaces).

Two problems: 1. It appears you are not getting event notifications from the Google Nest service. The only update of status values for your thermostats are coming from status queries performed every 60 seconds (shortpoll interval). This creates problem # 2: 2. The Google/Nest SDM API for changing temperature requires both the heat and cool setpoints to be specified if the mode is "Auto." When a "Set Heat Setpoint" or "Set Cool Setpoint" command is received from IoX, the plugin uses whichever setpoint (heat or cool) is provided in the command along with the last known value of its counterpart to call the API. Because you are not getting event notifications from the service, the last API call has effectively changed the specified setpoint, but the current status is not updated. So when the subsequent command comes it, the counterpart setpoint it uses is not reflective of the change just made. As to #2, this is not so much a bug as it is a design flaw. Had you not been putting in the two seconds between steps in your program, there is no way the current code would've worked correctly even if you were receiving status updates. The approach here has to change - look for a new version soon. As to #1, you need to make sure "PG3 Remote Connection" is configured and active for your eISY/Polisy. To configure this, login to https://my.isy.io, and from the "Select tool..." dropdown next to your eISY or Polisy, select "PG3 > Remote Connection." Make sure "Remote connection configured" and "Remote connection active" are both "Yes". If these are active and you are still not getting event messages, we can continue debugging. I will also be sure that this is put into the Installation Instructions, if it's not already in there.

Sounds like could be a bug in the plug-in. To debug, please: 1. Change the logging level for the plugin to “Debug” in the PG3x Dashboard 2. verify temps in Admin Console match temps on tstat (or use Google Home app) 3. Push keypad button 4. After a minute, check whether temps on tstat (or in Google Home app) match new temps in Admin Console. 5. If not matching, please DM me the log package.

Can you send a screen shot of the Nodes screen from the PG3x Dashboard? Also, change the Log Level to “Debug” for the plugin, restart the plugin, then DM me a log package.