tmorse305

@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.

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.

Thanks for the clarification!

Hi @bpwwer, The status of the NS in the AC is always True even if I stop the Node Server. I've only waited a short time, does it eventually toggle to False? Some NSs toggle immediately (VUE, Notification for example) Others have the same behavior as WeatherFlow (August, MQTT) Why do they act differently? Thank you.

Fixed with update 0.3.17. Thanks again @Panda88!

Hi @Panda88, I can no longer control my blink camera from IoP. I can change the arm state in the AC and it looks like it makes the change but when I check the Blink app the change did not occur. I tried a restart of the NS but the same result. I did notice some errors were reported after restart at 2022-12-12 15:18:13,843. I'll PM you the log file. Thanks for any help you can provide.

What kind of switches are you talking about? Which switch did you replace? Was the replacement switch new or used? When you replaced the switch did you have to disconnect any other wires to gain access. Maybe a mis-wire on re assembly?

You only want the api key not the whole url. Just the x76XxXX....... part

Do you have the API key configured correctly? It looks odd in the error message above. From Jim's instructions: API Key Enter your API Key for Webhooks by going to Maker Webhooks then click on Settings. This shows a line at the bottom like https://maker.ifttt.com/use/xxxxxx the xxxxxx is your API Key. Copy and paste just that part to the API Key. It looks like you included the https://maker.ifttt.com/use part. Just enter the xxxxxx part. A typical key looks something like this: duC-0KVspL2ctf2jpgPEs1

@ISY4Me, its a program, I am using the Notification NS but of course any notification tool will work. I put the program in a screen shot so you could see the breakdown of the Notification command. ProgramName-NodeST is a customization that is: ${sys.program.#.name}: ${sys.node.#.name}=${sys.node.#.ST}. This program will fire when ever there is a change in the listed NSs so you get notified when they go offline and when they come back online.

Did you check the NS log for any errors? I find that the the connection to ecobee will drop. I don't know if it's the NS or the ecobee server. I get a notification when it drops, usually its back up in a minute but sometimes it takes longer

Thanks @Javi, if anyone else encounters this bug there is a simple workaround. It only occurs when the folder's children count matches folder's siblings count. So just add a folder or widget so the count is not the same.

@Javi, do you mean the backup file? If not where do I find the db file? The problem survives a swipe.

Hi @Javi, I was creating more widgets in a folder when the display started acting strange. I couldn't move up and down the hierarchy correctly. See screenshots. From pic1 I pressed the folder "Equipment Status". In pic 2 you can see the header changed but the contents was still the Favorites screen. I pressed edit and in Pic 3 the screen now displays the Equipment Status folder. I pressed the back arrow and you can see I'm back to the Favorites screen header but the contents is still the folder contents. Suggestions? Thank you!

This problem has been resolved with PG3 3.1.14 and a little ssh magic from @Michel Kohanim. Thank you!!

Thanks @Jimbo.Automates, it's better to keep the flexibility on dynamic IPs. I wasn't sure how much resources it was consuming or how much network traffic it was creating. Maybe I'll just keep it plugged in when not in use.