randyth

I vote do it in a program. I don't believe scenes were designed for such logic.

I think you are having trouble because you skipped the "SSL Error 'ee key too small'" step mentioned above. So, please try following these instructions and see if that helps: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small

Yay! Glad I could help. @Michel Kohanim, perhaps someone could update the readme to include the fact that the latest RPi OS won't work with PG2?

If you use the Raspberry Pi Imager, choose Raspberry Pi OS (other) and then select Raspberry Pi OS Lite (Legacy). After installing PG2, follow these instructions to fix the “ee key too small” error. Then you should be all set.

Last I checked, the most recent Raspberry Pi OS doesn't support mongodb so you are unable to install PG2 on it. Update: I just verified that if you avoid the latest RPi OS and install the Raspberry Pi OS Lite (Legacy) port of Debian Buster instead instead, PG2 installs just fine (though you might have to follow these "SSL error" instructions to get it to start properly: https://github.com/UniversalDevicesInc/polyglot-v2#ssl-error-ee-key-too-small).

Testing this out in the morning, everything is working great. Thanks for clueing me in on needing to uninstall/re-install each NS, @bpwwer. Interesting possible side effect of all this is that one might actually be able to support multiple ISYs with PG2. Just change the System->Polyglot Settings to the desired ISY prior to installing a NS. You simply couldn't share any one NS with more than one ISY.

OK, I think I got this. Some newly installed node servers appear to work with ISY/Polisy. Not all yet, but perhaps I have to be, um, more patient? It looks like the answer is to uninstall and then reinstall all the node servers after changing the System->Polyglot Settings. Does that sound right @bpwwer?

You have me at a bit of a loss as to what the solution is here. This statement in particular confuses me: "When Polyglot starts, it queries the ISY for what node servers have been configured there" I am happy to uninstall all the node servers and re-install them. But my understanding is that this would still all take place in Polyglot, not ISY. In other words, I don't appear to be able to install or "configure" node servers from ISY's admin console. I feel like I'm being obtuse and missing something obvious (apologies). It's been so long since I set up Polyglot that I honestly don't remember doing anything on the ISY side to "configure" node servers there. So, how do I set up my ISY/Polisy so Polyglot knows about the "node servers [that] have been configured there"? In other words, how would you get ISY/Polisy talking to Polyglot/Polisy after originally setting up Polyglot/Polisy to talk to an ISY994?

I decided to cutoff my old ISY994 from the PG2 Node Servers hosted by my Polisy and point them at the ISY 5.2 hosted on the same Polisy. To do this, I simply logged into PG2 on my Polisy, went to System->Polyglot Settings and changed the ISY Settings to point at my ISY/Polisy. That is, I changed the Address/Hostname to the IP address of my Polisy, changed the port to 8080, entered the device password and clicked Save and a happy green "Settings saved successfully. If you changed the Polyglot Web Port, please restart Polyglot." message appeared. However, when I reloaded the ISY/Polisy admin console, there were no Node Servers. And, frustratingly, they still all appear in my old ISY994's admin console?! I've restarted the Polisy a few times now (via soft reboots and a complete shutdown-powerdown-powerup), but that is not helping. What am I missing (it's probably something obvious)? How do I convince PG2 on Polisy to talk to ISY on the same Polisy?

Not sure if this is related to your issue, but AWS is largely down this morning, making Alexa a lot more stupid. https://www.businessinsider.com/amazon-servers-are-down-and-its-affecting-dozens-of-services-2021-12 https://status.aws.amazon.com/

Hmm, that all looks good to me. Because I can't see the end of the body text, all I can think of is to make sure the accessCode is correct and perhaps run your JSON through a checker to test for typos.

That's it! Thanks so much @MrBill

I'm attempting to keep my ISY994i running in parallel with ISY/Polisy while I slowly migrate tasks from one to the other. Both are connected to the Portal with active licenses. However, the ISY Optimized for Smart Home v3 skill for Alexa refuses to find the devices/scenes entered for my Polisy via Select Tool->Connectivity->Amazon Echo. I have made several attempts at new device/scene discovery through voice ("Alexa, discover my devices"), the app, and the https://alexa.amazon.com/spa/index.html#smart-home site with no luck. Is this a known issue (perhaps the skill can't deal with multiple ISYs)? @larryllix, how did you handle this?

FYI, I can confirm that the SNI support fix in 5.2 fixed the Network Resources issues I reported earlier in this thread.

SSH into your Polisy and try this: sudo service isy restart That solved the problem for me.

FYI, all I had to do was a... sudo service isy restart ...and both of the above problems went away. D'oh!

Good idea. Done. Though I will say, having a UUID of 00:00:00:00:00:01 is kinda cool.

That closes the entire Admin Console. It could be that I'm not finding the specific "System Busy" subtask in Task Manager in order to keep the console open. Regardless, I'm afraid that won't fix my lost UUID.

These instructions got the launcher recognizing my ISY/Polisy as well, but now my UUID appears zeroed out. And, I can't get past the "System Busy. Please do not power off..." dialog box after selecting the Polisy and logging in. It repeatedly -- and slowly -- counts up to 99% and then starts over at 0. I've restarted the Polisy twice now, but that doesn't appear to help.

Similar to Mr. Bill's suggestion, if you are a developer you could also look into creating a Node Server for Kaiterra.

Did you check the Use SNI box? If not, try that. Unfortunately, you cannot do this. Network Resources on ISY are for triggering events. You cannot extract data from the calls you make.

Thanks so much for taking the time to help test and think this through, @MWareman. From what I see, the results support your Cloudflare idea. @Michel Kohanim, could the fact that my "failed" ISY/Polisy NRs rely on APIs running behind Cloudflare or Cloudfront (api.notifymyecho.com uses Cloudfront) be the issue? Cheers, -Randy

You probably forgot to put quotes around the URL when using curl and wget. You might try this, for example: curl 'https://www.alphavantage.co/query?function=SYMBOL_SEARCH&keywords =tesco&apikey=demo' That works find for me, at least -- even when called from Polisy's SSH shell. I am simply using alphavantage as a test of Polisy's ability to access public APIs. I discovered this issue with Polisy's NR system when importing the NRs from my ISY994i. Network Resources on ISY/Polisy could not access api.notifymyecho.com or api.virtualbuttons.com, even though these exact APIs work flawlessly on my ISY994i. You can read more about the origin of this issue here. I am in the same boat. I have a lot of other NRs configured that work without issue in ISY/Polisy, just not any that access an API outside my local network. Do any of your functioning ISY/Polisy Network Resources access APIs outside your local network?

I did see that but find it hard to believe it's a timeout issue. Even if I increase the Timeout setting from 2 to 20 seconds (20,000 ms, the maximum setting), the "Request Failed" box appears immediately. I think Michel's interpretation of the error log is likely more indicative of the problem... ...and suspect a "cannot connect" is always accompanied by a "client timed out". My ISP's default servers (Comcast 69.252.228.129/69.252.228.133). Note that Polisy can ping these public API endpoints without issue -- it's just the ISY on Polisy Network Resources system that is struggling with them. @MWareman, Are you able to access www.alphavantage.co from a Polisy NR (er, assuming you've installed ISY on Polisy and are willing to take the time to play guinea pig)? You can check out the screenshot in my previous post for how to set it up if you have the time.

Interesting. My Polisy is connected to the same router (ethernet, not Wi-Fi) as my ISY994i and other equipment. Additionally, I can ping the URL successfully from Polisy using SSH: Another test I just did was to use the www.alphavantage.co API instead of api.notifymyecho.com. Again, the Network Resource calling www.alphavantage.co works on my ISY994i but not ISY on Polisy: This alphavantage NR results in another -1 error when called by my ISY on Polisy. Time User Code Message Mon 1900/01/01 12:00:00 AM System -170001 <s:Envelope><s:Body><u:TestNetResource xmlns:u="urn:udi-com:service:X_Polisy_Service:1"><id>1</id><flag>1</flag></u:TestNetResource></s:Body></s:Envelope> Mon 2021/11/15 09:38:53 AM 0 -170001 [TCP-Conn] -1/-140002, Net Module Rule: 1 Mon 2021/11/15 09:38:53 AM 0 -170001 <s:Envelope><s:Body><u:GetLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:GetLastError></s:Body></s:Envelope> Mon 2021/11/15 09:38:53 AM 0 -170001 <s:Envelope><s:Body><u:ClearLastError xmlns:u="urn:udi-com:service:X_Polisy_Service:1"></u:ClearLastError></s:Body></s:Envelope> -Randy