tmorse305

Run at Startup may override enable/disable, I'm not sure but it looks like it from your posts. Easy experiment, reboot with run at start up on/off and see if the disabled 2b programs run. Honestly I still think you have a communication problem with your sensors. You shouldn't need a 49 hour wait, the sensors reliably send the heartbeat every 24 hours unless the battery is dying, the heart beat quits before the sensor stops working altogether. Also on reboot IoX has no idea of the status of the sensor until it receives the first heartbeat. That might explain why rerunning the startup routine works, because by then there has been a heartbeat. But if the heartbeats are being missed then it would be hit or miss.

@waffles, What are you restarting when you made this comment? IoX or just running the startup routine again? The need to change the wait to 49 hours suggests a communication problem with the sensors. You have a lot of sensors but if they're all in the same area maybe they're having trouble communicating? Is there a dual band device nearby to handle the transmissions? My 2a and 2b routines are different than yours. My triggers do not include the state of the wet sensor. Geo-VC-2 - [ID 0034][Parent 0032] (this is my 2a) If 'Basement / Geo Leak Detector-Heartbeat' is switched On Or 'Basement / Geo Leak Detector-Heartbeat' is switched Off Then $sLeak_Geo = 1 Wait 25 hours $sLeak_Geo = 2 Else - No Actions - (To add one, press 'Action') Geo-VC-3 - [ID 0035][Parent 0032] (this is my 2b If $sLeak_Geo is 1 And Time is Last Run Time for 'Geo-VC-2' + 26 hours Then Wait 5 seconds $sLeak_Geo = 3 Else - No Actions - (To add one, press 'Action')

@waffles, it looks like you have the wait set to 49 hours at least in the one you posted. Can you show the control 1 and control 2b programs as well? Are you getting notifications about missing heartbeats?

@PB11, If you use Alexa in your automation you could use the Flic buttons to trigger a routine that in turns triggers an IoX program. Link It's a bit round about but could fill the need until the remotes come back. Pricey solution however.

You forgot the '+' sign.

Looks like you're not alone

@Methos000, is your ticket still open? I had a similar issue with my PG3 after an IoX upgrade. Michel suggested 2 ssh commands which resolved the problem. I could give you those but probably better to ask him since my situation was not exactly the same as yours.

Let us know how they resolve it for you.

I think it's time to open a ticket.

When you said earlier that you could reach the Polisy dashboard did you mean via this url: https://<ip address>:3000/dashboard What are you entering for the credentials when the launcher appears? Have you tried both https and http? The standard ports are 8443 and 8080 respectively unless you changed them.

Eventually, but that's not the problem today. Say more about what is happening. Does the launcher appear? Does it populate with the proper credentials for your polisy? If so what happens when you try to launch the AC?

@Davey, Make sure that the Insteon support check is still there. I had it disappear on a reboot for some reason.

@photogeek54, As you can see from my screen shot I don't use Z-wave so the z-wave gurus are going to need to jump in here to help you.

@photogeek54, if you're not going to use Insteon anymore make sure it's disabled or it will hunt for any Insteon devices that are in your system.

Here's your list extracted from the AC. There may be a few 'S' that came through as '5' but it's close enough I suspect. I looked at the reference that was provided and there were some blanks in the sub categories so that approach may not yield as good a result as this one. Insteon Device List.xlsx

Yes if you use the Start Linking in the pull down menu. See screen shot first line of the instructions. I agree with others, it sounds like a noise issue. Is there anyway to plug the new module in the same outlet as the PLM and see if that makes any difference?

I think it's time to open a support ticket with UD for this problem. They can remote access your PC and hopefully see a problem that has eluded all of the questions we've been throwing your way. Please let us know how it goes, it's definitely an interesting problem.

I just deleted my state files to see what would happen. When I restart to AC via the launcher and check the directory, there are no .state files. They only reappear after I close the AC. The launcher file only appears if I modify the launcher by for example adding another ISY. You said in an earlier post that you verified that ISY was running from your phone app. Is that UD Mobile? Is it still working via the app?

@MrBillhad suggested you try the cloud connection a while back. Have you tried that? If it works, the login credentials are for your Portal account not your ISY.

I had this happen once, and this fixed it for me Here are 2 more troubleshooting ideas from the wiki. In the case of the first one, the AC usually appears so that's probably not it.

So is this your current situation? All programs are working correctly Cannot access the Admin Console Portal says ISY is offline If so that sounds like a network connection problem. Can you ping ISY? Maybe try a different network cable

Yes I included it. per the NS configuration instructions: tokenFilePath - Path and Filename were the tokenFile should be generated ( /var/polyglot/node servers/AugustLock/token.txt ) The directory must exist and the user running polyglot must have read/write access. All is well once I deleted the NS it and reinstalled it.

Thanks @bpwwer, I changed the path to the location of my NS, /var/polyglot/pg3/ns/0021b9026044_10/token.txt but it still creating errors on restart, different errors this time. I wonder if its a permission issue on that folder, when I used ssh to look for the token.txt file I got permission denied. Log attached. Update: I deleted the NS and reinstalled and this time it started up with no issue, thanks Bob August_1-11-2023_11412-PM.zip

Hi @automationgeek, I just migrated the August NS from PG3 on polisy to PG3x on eisy. I now see this same error as reported above by @someguy. When I check /var/polyglot/node servers/AugustLock/token.txt, from ssh, the path does not exist. Should I create the path and file manually or has it moved to a new location in PG3x?. Thank you.