pinlawr

Sorry for the late reply, and thanks for the help. I guess I had email notifications off. I ran into this (bitstring problem) a while back when it was first a problem on my PG3 instance and used the above instructions to fix it. Everything worked fine until the move to PG3x. My pip3 list shows "bitstring 3.1.9", but I went ahead and tried the steps you sent just to verify and it made no difference. I'm still getting the same "no module named 'lifxlan'" error, even with pip3 list showing that "lifxlan 1.2.7" is installed. I'll go open a ticket.

Hello! I've been running the LiFX node server on my Polisy for awhile now, migrated from PG2 to PG3 a while ago. Just moved to PG3x. Now when the node server tries to start all I get is the same lines in the log over and over until I stop it. 2023-08-31 16:08:57,295 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.1.0 Starting... 2023-08-31 16:08:57,300 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2023-08-31 16:08:57,301 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/000db952cee0_12/lifx-poly.py", line 10, in <module> 2023-08-31 16:08:57,302 MainThread udi_interface ERROR udi_interface:write: import lifxlan 2023-08-31 16:08:57,303 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2023-08-31 16:08:57,303 MainThread udi_interface ERROR udi_interface:write: : 2023-08-31 16:08:57,304 MainThread udi_interface ERROR udi_interface:write: No module named 'lifxlan' 2023-08-31 16:08:58,914 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 I SSH'd in and manually and ran the install.sh script and it re-installed the lifxlan module. I can see "lifxlan 1.2.7" in the list when I "pip3 list". Other potentially relevant version info: PG3x Version 3.2.3 Frontend Version: 3.2.3 IoX Version: 5.6.4 Not sure where to go next to get the node server back up and running. Thanks for any help!

Error log was the last attachment. It just says "Net-Resource: Failed connecting to 192.xxxx". Nothing else shows in the log.

My settings are exactly as suggested. In my screenshot you can see that verify is NOT checked. I mentioned that it's set to TLS 1.2 since it's not visible in the screenshot. Resource screenshot shows it's set to a 10,000 timeout. I also mentioned that SNI doesn't make a difference checked or unchecked (and it wouldn't anyway since the cert in question doesn't use SNI). It works from a browser, curl, and postman. I also mentioned it DOES work on a ISY on Polisy, just not on the 994.

I read through the info in this thread (Can you ignore ssl validation in a Network Resource?) and I am basically having the same issue. I've attached my network settings (protocol on both is set to 1.2, since it's not visible in the screenshot). Also attached is the network resource and the simple error message I'm getting back. Toggling SNI changed nothing (which wasn't a surprise since the cert has no SNI entries). The request has to be PUT. I have the self-sign cert from the hub exported, but I don't see any way to import it as trusted, or simply tell the ISY to ignore it. I have a Polisy, but haven't moved to IoP yet. As a test, I exported/imported my network resources into IoP just as they are, and they DID work fine without any errors. Thanks for any help!

I submitted a ticket 9 days ago. I just sent them a follow up.

Not yet. I opened a ticket as suggested but haven’t received any follow up except from the initial submission. Need to go give it a bump.

Done! Thanks!

The error comes up the moment I push the Execute button (so no delay like it's waiting for a timeout). As a test, I adjusted the timeout on one to 5 seconds, the error still popped up the moment I hit execute. All of them work when ran from the console, and all are used daily (or more often) in programs that run both automatically and on demand. Also, all resources are to local devices/servers on my internal network. There are no calls to internet resources. Oh, app version is 0.9.6, just for completeness. ISY is 5.3.4.

Some, but not all, of my network resources return a 404 error when I try to use the Execute option on them from UD Mobile. At first I thought it was only programs that have a dash in the name, but that isn't consistently the problem. When I view the node info the address is correct, etc. I've re-synced UD Mobile and that doesn't help. I also don't see any errors in the event viewer. The network resources DO work when executed via the admin console, or from programs, etc. It's only when trying to use the Execute button from UD Mobile. The full error that pops up is: <?xml version="1.0" encoding="UTF-8"?><RestResponse succeeded="false"><status>404</status><RestResponse> Thanks for any help, Billy

Awesome! Thanks!

First, I could be crazy, feel free to tell me I am. Didn't the portal have the option to reboot the ISY? I don't seem to have that option anymore. Having it there was a lot easier than digging behind the device to unplug it, or launching the java client. Thanks, Billy

Disabling, then reenabling the V3 skill fixed this for me (without forgetting and rediscovering all devices).

Thanks, Michel - I sent a support email (and, my apologies, misspelled your name in the email). The request is #19484. I've left it "broken" in case the support team needs any data while it's in this state. I didn't see anything of note in the error logs, but hopefully they're useful.

Hmm. Thanks guys. Right now I'm still seeing the issue. All other Alexa skills continue to work as usual. All methods of access to the ISY work fine, except Alexa (and the Alexa app), which still have the errors mentioned in my original post. I contemplated disabling and re-adding the skill, but I would prefer that as a last resort so that I don't have to re-setup all my Alexa routines and Alexa app groups. Always open to other ideas.