OffToSeeTheWizard

Unfortunately, no. I've tried this with 5+ devices. Restore, reboot, no change in behavior. Must use Query button in AC to see any state changes. Restore All Devices has been tried too. I just tried to restore one again now and still no joy.

UI and Firmware info attached. Also attached PLM Links Table if it's of any help. I believe I followed the Polisy to eISY migration steps very exactly, but that was some months ago. As I have been troubleshooting I have tried several times to restore the PLM, including even yesterday when I swapped in a known good spare PLM. Behavior is the same regardless of which PLM I use. I have performed the facory reset on the PLM(s) too. About the only thing I haven't tried is to delete the PLM. Warning messages made me abandon that idea quickly. Curious to me is that PLM reports only 129 links. It feels like that number should be much higher given the number of devices and scenes in my configuration. PLM Links Table.v5.7.0__Thu 2023.10.19 11.37.07 AM.xml

This condition has likely existed for several months and I am just finding the time to troubleshoot now. Upgraded from Polisy to eISY. Insteon device status does not update in either admin console or mobile app. If I initiate a Refresh on the device in AC it immediately updates. Same if I Refresh from UDI Mobile. If I physically toggle a wall switch, the AC and Mobile app do not update. I have restored all devices, devices individually, restored the PLM , swapped in a new PLM, restored from backup, etc. I can control all of the devices from AC and Mobile app. Zwave devices auto refresh their status. PG3 nodeservers all constantly update their status. I feel like there's a global setting someplace that's incorrect since this happens with all of the Insteon devices. Any ideas would be sincerely appreciated.

I have two homes with eISY / Polisy. One has two Ecobee thermostats and the other has one. I have a licensed copy of the NS installed in each. Is there a Custom Configuration Parameter available which would allow me to choose only the values from my chosen thermostat to be created as nodes? Every time either of the PG3x's is restarts, it populates all of the thermostats in my Ecobee account into both instances of the NS and subsequently into the Admin Console. If not available today, feature request please.

This seems to have resolved itself with the upgrade to IoX 5.6.4 and PG3x 3.3.2

Version 3.1.3 had been working in PG3x 3.1.37. Upgraded today to 3.2.1 and after reinstalling all nodeservers as instructed in the release notes, only the Ecobee ns is failing to start. I have tried reinstalling and it failed with the error in the attachment. Then I removed the ns and tried to install fresh and I get the same error. Any thoughts on how to remedy this? 8/14/2023, 15:15:45 [pg3] error: createNS: SqliteError: table nodeserver has no column named requestId at Database.prepare (/var/polyglot/node_modules/better-sqlite3/lib/methods/wrappers.js:5:21) at Object.add (/var/polyglot/node_modules/@universaldevices/pg3x/lib/models/nodeserver.js:287:6) at Object.createNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/nodeservers.js:177:16) at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Further testing update. Uninstalling Hubitat NS and sync problem is resolved. Install Hubitat into different slot and sync problem returns. Still having the same issue with Product store offering option to install 1.0.10 but it seems that 1.0.2 is always what actually gets installed.

It is Hubitat that is installed in slot 10, and, this was one I installed today. The version I purchased in the store earlier today installed as 1.0.2. As I was grabbing screenshots for you there was a message displayed indicating a new version was available. I went to my purchases and upgraded it to 1.0.10. This seemed to work. I tried to synchronize first with the NS stopped. Same error as before. Then I started the NS and it showed that it was still 1.0.2 as though it downgraded on start. Still the same error when synchronizing as before. I feel like I should be doing a Restart PG, but I don't see that as an option in the UI any more.

New version worked as advertised. It looks like the Hue nodeserver is causing the issue; but ironically that was not one of the ones I installed today. I have it installed for > 1 year I believe.

Yes, Galaxy Z Flip 5. And yes, updated and installed some new node servers so I could finally get off of PG2 as everything I was using now has a PG3x equivalent.

I own two Polisy's which are 1k miles apart. Both are IoX 5.6.3. One is PG3, the other was upgraded to PG3x today. When I go to sync the mobile app to the one with PG3, everything works as usual. However, when I try to sync the mobile app to the one which was upgraded to PG3x, it begins the process and the app crashes hard and shuts down. I have done a force stop, checked to make sure no upgrades are available, etc. Maybe it's a coincidental with the PG3x upgrade but I can't think of anything else that I have done. Has anybody seen and resolved this before? IoX 5.6.3, PG3x 3.1.37, Android 13.

Working well now after uninstall / reinstall. Thanks!

It's still showing at v0.0.0 in the store (even after a refresh) and no choice to update.

Still nothing in the AC. There is no line in the logger that shows that GV7 is updating. It stops with GV6

Sorry, wrong screenshot with last post

Folders field is showing in the AC but but there is no value. Looking in the log, the Folder Count is shown but it looks like a line is missing to update the driver.

Confirmation of my problem. Great to know that your upgrade will help others if they find themselves in my situation. Thanks!

This issue is resolved. And the prize goes to MrBill for the correct diagnosis. I had in fact exceeded the node count for my license. As Michel explained it, the 188 Total Nodes reported by ISY Inventory doesn't account for the # of Scenes and Folders both of which factor in to the total count. With all of it added together, I had exceeded the 254 that I was licensed for. Purchasing the Pro upgrade and then uninstalling / reinstalling the nodeservers which pushed me over the limit fixed everything. Thank you to everybody for the help.

Excellent suggestion MrBill. I already had the ISY Inventory ns installed and it looks like for now I'm Ok; but at the rate I'm going a Pro upgrade will be in my future.

DennisC, thank you for your troubleshooting suggestions. It's always good to start with diagnostics. Unfortunately, an Error Code 403 = Forbidden does not provide any additional details about what to look for in the Wiki. So for testing, I simplified the configuration and captured logs. I stopped all Polisy and Polyglot Cloud nodeservers and cleared the logs. I used two of the three newer ones I've added for some tests. First, I tried the Holidays ns on Polisy. Logs are attached as are screenshots of the 10 nodes that the ns is displaying. There are no nodes in AC; not even the controller. There were no entries written into the ISY event logs. There are errors in the ns log: ISY Returned 404. Unfortunately, Error 404 is not even listed in the Error Messages portion of the Wiki (screenshot attached) Next, I tried the Flair ns on Polisy. Logs are attached as are screenshots of the 9 nodes that the ns is displaying. There are two nodes in AC. There are a few entries written into the ISY event logs but they didn't appear to indicate any errors. If I had to think back when the problem may have surfaced, it may have been when I installed and configured the Flair ns but I don't believe it is the source of the issue; and, except for the other new ones I installed after the Flair; Hubitat and Holidays all of the other nodeservers continue to work fine. I have, over the course of the last week, uninstalled and reinstalled all three of the newer nodeservers that I mentioned. Lastly, regarding the credentials between the Polisy and ISY, I believe all nodeservers use the same defined connection between Polisy and ISY; but just to make sure I reconfigured the credentials but it did not make a difference. Hopefully somebody in the community might recognize what's going on here; otherwise I guess I will submit a UDI ticket. Thanks for your ideas. holiday ns startup log.txt flair ns startup log.txt ISY-Events-Log.v5.3.0 Flair NS Startup.txt

I have 10+ nodeservers working in Polisy and Polyglot Cloud and have for months. Suddenly, whenever I try to install a new one now either on Polisy or Polyglot Cloud, the nodes won't appear in the AC. The nodeservers show in the slots in AC. The nodes show in the Polisy Dashboard details for each nodeserver. Even the simplest one with no devices or configuration like Holidays shows 10 nodes but none will appear in the AC. When I try to manually add a node from a Polisy nodeserver, I get a [LIB_ERRORS-403] error. When I try to add a nodeserver in Polyglot Cloud I get a Couldn't Add Node to ISY 403 error. I've also noticed recently that on launch of the AC I'm getting a popup AutoUpdate Status, Authorization Failed message. I believe this may be a FW issue. Currently at 5.3.0. Tried to upgrade to 5.3.1 but no improvement. Downgraded to 5.3.0 again. FW and UI are matching at 5.3.0Java is latest version and cache was cleared. I believe the common theme is "403" but I don't know what's behind it. I'm inclined to perform a factory reset of the ISY; but I hate to do that without first seeing if there are any alternatives. Thanks in advance.