tmorse305

Hi @Javi, yes all of the devices are affected. The program are also affected, the states shown in the screen shot are not correct. I tried a reboot to eisy but no improvement. eisy is at 5.8.4. I have another eisy that is working correctly running 5.8.3

This issue is very similar to another thread but my issue does not include a node server, just an Insteon device. See screen shots. Thank you @Javi

Thanks Jim.

Hi @Jimbo.Automates, I see an error in the log: 024-08-22 17:27:21,169 Thread-36 udi_interface ERROR wtServer:l_error: wTagManager:f4b7248a5fb0:Clermont:post: Connection error for https://www.mytaglist.com/ethClient.asmx/RequestImmediatePostback: HTTPSConnectionPool(host='www.mytaglist.com', port=443): Read timed out. (read timeout=60) Not sure what's the issue. The tag does update if the tag is motion triggered for example, but I don't think the 60 sec pole is working. Thank you.

For me, the most recent event occurred right after the portal maintenance. It might have been coincidental, but both of my eisys failed communication with Alexa. They are on different Amazon accounts.

@bmercier, thank you for the explanation that was really helpful. Like @larryllix, this issue still occurs from time to time. Can you comment on these questions? What do you think breaks down when the routines stop working? If a routine is created, does the subscription happen immediately or when the routine is triggered? You said the subscription is permanent, I imagine they can get messed up, does Alexa simply retry to create it? Is the anything in the eisy logs that would indicate subscription problems if they occur? Disable/Enabling the skill I'm guessing breaks the subscriptions. Is there anything else we can try when the routines stop working? Thank you for your support with Alexa!

@larryllix, I've seen that before too. I should have mentioned that I deleted the routines and devices before the disable/enable. Still no luck. I may try Amazon support tomorrow to see it they can see anything from their side.

Not working for me, I've tried multiple times to enable/disable. Also deleting and rediscovering the devices but still not working. Any suggestions? Thank you.

Hi @Goose66, I installed the NS today but was having trouble connecting the NS to my EnvisaLink4. I finally figured out that the configuration for the password seems to be limited to 6 characters. My password was 7. Once I shortened it by 1 character, I was good to go. Just FYI, thanks for creating this NS, I am replacing NodeLink as operation is getting erratic.

Do you use the UD portal? If so go to the Portal and see if the portal can see your isy. If so then your isy is getting an IP address from somewhere. If not then you're probably right about the static IP assignment. Option 1 seems easier to do, just change it to 192.168.1.x long enough to login in to isy and change it to DHCP. Then you can switch it back to 192.168.50.x if you want.

You could assign the parameter (illumination?) to a variable, but I'm not sure how you plan to pass the value to Alexa.

Thanks @bpwwer, those entries are for the Vue that is reporting correctly. I have 2 Vues: 9838 Crenshaw is 293227 115 Frontier is 35060 I could not find an entry for 35060 ST. I thought all of the highlighted(orange color) errors referenced n003. Anyway it doesn't matter since there are no errors that I could see associated with 35060. Thanks Bob for your help.

Thanks @bpwwer, I looked at the PG3 log but I don't see any errors associated with the Status of the '115 Frontier' Vue. I was looking for "ST", is that correct? The is no reference to ST for the 155 Frontier Vue, error or otherwise. I did find the ST entries for my other Vue (9838 Crenshaw) highlighted in blue. I've included the log file in an excel sheet. I highlighted in orange any errors associated with NS 003 (Vue). There is an error associated with each plug I have, but curiously the other errors are related to the 9838 Crenshaw Vue. I highlighted in green any reference to the '115 Frontier' node. Do you see an issue that I'm missing? Thank you very much for your help! PGX Log from boot(1).xlsx

Thanks @Jimbo.Automates, will that fix allow me to create a program similar to the one you listed in your examples?

Hi @bpwwer, I have am running 2 Vues. One of them is not showing the online status, it's blank, see screen shot. The other is fine. Both however are reporting active power values on all channels. Occasionally this Vue(115) seems to go offline. A restart of the NS fixes it but the status is still blank. Log attached from the restart. Thank you. debug.log

My Rainmachine NS is alive and well also. V3.2.1 PGX 3.2.27 eisy 5.8.3

Thanks Jim.

Hi @Jimbo.Automates, In your instructions for this NS you show an example of triggering on a skunk, see attached. I cannot duplicate your program for some reason. If I use STATUS I get this: Squirrel Detect - [ID 0154][Parent 0001] If 'Camect / Feeder Camera / Feeder Camera animal' Squirrel is True Then Resource 'Squirrel Blaster(14)' Set 'Notifications / Notification Controller / UD Mobile' Send Message Content 10 Notification ID (ID=10) If I use CONTROL the closest I can get is this: Squirrel Detect - [ID 0154][Parent 0001] If 'Camect / Feeder Camera / Feeder Camera animal' is switched Squirrel Then Resource 'Squirrel Blaster(14)' Set 'Notifications / Notification Controller / UD Mobile' Send Message Content 10 Notification ID (ID=10) This program triggers twice, False>True and True>False How did you program that? I believe the alerts are received immediately, what does the short/long polls control? Thank you

I use Echo Auto to control home devices while I'm driving. It's also a great way to get updates from your automation system, for example Alexa can say "You left the garage door open"

Thanks @Goose66, sorry I didn't realize there were 2 forums for the Envisalink NS. Yes I have a DSC panel so it's sounds like I'm good to go.

Hi @Goose66 I've been using Nodelink to interface to my alarm panel. I noticed that ioguy's website is gone so I'm thinking it might be time to move on. Does your NS allow for control of the output pins? Based on what I read I don't think so but I wanted to confirm with you. Thank you.

File sent

To enable you need to add a new key. The Key is the name of your network (case sensitive) and the value is ENABLED. I used all caps for the key, it didn't work with upper and lower case.

Thanks @Javi, when I went to run your test, it is now working fine on the favorites page. As far as I know I've made no changes. Thanks, I'll let you know if I see it again.

I’m on 5.8.3 Sent from my iPhone using Tapatalk