tmorse305

Open a browser and go to the web config server page for NodeLink. There you will add the ISY credentials. The port is 8090, and the ip is the ip for the computer running NodeLink.

I don't have any experience trying to operate a 994 without an network connection. Others may be able to comment on that. You would think the programs would still be running but maybe it gets hung up trying to establish a network connection to something, (portal, polyglot, etc). Not sure you still have access to it but maybe try a reboot to see what happens.

So your 994 and modem are still plugged in? Leaving them for the new home owner? Were any of the other scene buttons tied to an actual program on the 994 or were they just scenes stored in the Insteon devices?

I use NodeLink for logging. It can keep track of devices, programs and variables. It's very useful for tracking down intermittent problems.

Hi @JimboAutomates, I'm running version 3.0.2 on Polisy 3.0.55 with ISY at 5.4.2. From the AC perspective everything seems ok, the NS is up there are values populated for the thermostats that seem correct. I cannot control the thermostats from the AC however. If I try to change the fan mode for example nothing happens. Looking at the NS, the log will not display there is only one long entry: 2022-04-04 13:21:08,111 Thread-5974 urllib3.connectionpool WARNING connectionpool:urlopen: Retrying (Retry(total=29, connect=30, read=29, redirect=None, status=None)) after connection broken by 'ReadTimeoutError("HTTPSConnectionPool(host='api.ecobee.com', port=443): Read timed out. (read timeout=10)")': /1/thermostat?json=%7B%22selection%22%3A+%7B%22selectionType%22%3A+%22thermostats%22%2C+%22selectionMatch%22%3A+%22521789884617%22%2C+%22includeEvents%22%3A+true%2C+%22includeProgram%22%3A+true%2C+%22includeSettings%22%3A+true%2C+%22includeRuntime%22%3A+true%2C+%22includeExtendedRuntime%22%3A+true%2C+%22includeLocation%22%3A+true%2C+%22includeEquipmentStatus%22%3A+true%2C+%22includeVersion%22%3A+true%2C+%22includeUtility%22%3A+true%2C+%22includeAlerts%22%3A+true%2C+%22includeWeather%22%3A+true%2C+%22includeSensors%22%3A+true%7D%7D, that's it. Under the node tab there are no nodes. I've have tried a couple of restarts but no luck. Suggestions? Thank you.

Hi @glarsen, I just installed 3.1.6 on PG3(3.0.55). There is an error on startup, see attached log. Thank you for your help. RainMachine_4-1-2022_95312_AM.zip Update: After multiple restarts I stopped the NS around 10 this morning. This afternoon I thought I would give it another try, and it came right up first try. Thanks anyway I'm all set.

Yes I get that but the content in the customization is generic. How does it get linked up to ecobee when the message is sent? Are the variables in the customization populated from attributes of the program calling it it?

Hi @JimboAutomates, very nice addition. I'm missing something in the example you provided. How is information about it being the ecobee Node server communicated? I see the generic customizations you created but I'm missing how it gets linked to the ecobee ns when the program calls it. Also wouldn't the Short Custom Content line need to be ahead of the Send Sys Short in the example? Thank you.

You said you are trying to load var.2.12 with the value from 2/50. Doesn't this GET do the opposite? I think the NR needs to be set up on ISY1 to set the ISY2 variable.

404? Hmmm works for me. Here is a screen shot:

It's a 10K resistor. You install in parallel with the led loads. http://www.pcslighting.com/pulseworx/products/tools/lds#wiring-diagram

Thanks @bpwwer, I downloaded 1.0.2 but it won't even start up for me.

Hi @bpwwer, I downloaded VUE tonight but it will not run. Here is the log info. I'm running PG3 version 3.0.45. I have configured the username and password parameters. Suggestions to try? Thank you. 2022-03-15 20:30:31,058 MainThread udi_interface INFO polylogger:set_basic_config: set_basic_config: enable=True level=30 2022-03-15 20:30:33,427 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.34 Starting... 2022-03-15 20:30:33,439 MainThread udi_interface ERROR udi_interface:write: Traceback (most recent call last): 2022-03-15 20:30:33,440 MainThread udi_interface ERROR udi_interface:write: File "./vue.py", line 10, in <module> 2022-03-15 20:30:33,444 MainThread udi_interface ERROR udi_interface:write: from nodes import vue 2022-03-15 20:30:33,445 MainThread udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/00:0d:b9:56:10:78_3/nodes/vue.py", line 10, in <module> 2022-03-15 20:30:33,446 MainThread udi_interface ERROR udi_interface:write: import pyemvue 2022-03-15 20:30:33,447 MainThread udi_interface ERROR udi_interface:write: ModuleNotFoundError 2022-03-15 20:30:33,448 MainThread udi_interface ERROR udi_interface:write: : 2022-03-15 20:30:33,448 MainThread udi_interface ERROR udi_interface:write: No module named 'pyemvue'

@mmb, So what exactly should I not be confused about?

@mmbAren't they both referencing the same thing?

I'm running 5.3.0 and 3.0.41. I saw the upgrade message in the AC regarding the newer version for IoP. I'm so glad I checked the forum before pushing the button. I have version 100 of the Bios. Should I just wait for the dust to settle a little more before upgrading? One concern, I know there are new versions of the NSs I'm using out there. Some require 5.4.0. If I have to reboot a NS or Polisy will the NS update even though it's not compatible with my current version of IoP? Thank you

Keep an open mind, you just never know.

Thanks, upgrading to the 5.4.0_3 solved the problem for me. All routines are working again including IFTTT. Thanks for your help and patience's as we all try to sort this problem out. It really looks like an Amazon problem but it has to be a mixture of both Amazon and ISY since the _3 version has fixed it for me. Now I just have to remember to disable/enable the skill each time I reboot ISY until they fix the throttling issue.

Even after the upgrade it still shows 5.4.0. Can you see 5.4.0_3 in your AC?

The thing is if I manually play the routine the IFTTT fires correctly

I just tried your test and it still fails even after disable/enable skill.

I just tried your method Delete the skill then reenable it (on phone) I didn't discover devices Tried the routine if failed. Deleted the routine re created it. Tried the routine it failed My routine involves IFTTT, do any of your routines use IFTTT?

Is anyone else having trouble with routines that use a motion sensor/ISY variable? The variable is changing, and I can see the motion sensor is triggered in the Alexa app but the routine does not fire. If I manually trigger the routine it performs the trigger correctly. There was some discussion in another thread regarding the ISY upgrade to 5.4.0, @Michel Kohanim thought it was Alexa throttling but this is days later and mine still doesn't work. It looks like an Amazon problem but I'm curious if anyone else is seeing this?

@JimboAutomates recently add support for Telegram which is also fast and reliable. The one advantage Telegram has over Pushover is that the messages show up in CarPlay. Pushover doesn't support CarPlay currently.

There is also some configuration help built into the Node Server itself.