MrBill

Blinking error light likely means your microSD card went tits up. Try to reseat it, and/or check if the file system is readable by removing it and using a usb adapter on your computer. If isn’t replace it, reload firmware, and restore your last backup, in that order. there’s a wiki article, but I’m having issues getting the link at the moment.

Or if it’s the 3 dots… there’s exactly one font size, I believe 14, that causes that, change the font size.

Change the “Time” Is drop-down to “From” I think that’s what your asking about.

I doubt anyone except @Michel Kohanim can answer, you might want to open a ticket for a speedier connection to him.. let us know the outcome!

what does the admin console show as the node address at the top? Does that match?

It appears you added n001. when you shouldn't have. Try just ${sys.node.141766_11.CPW} I think the node server author should have included n001_ in the node name but didn't, meaning two different node servers could possibly generate this same node name.

Polyglot3 is the future. At the moment both Polyglot 2 and 3 are available for use on Polisy. Installing new tho, you should use Polyglot 3. https://<IP.ADDR.OF.POLISY> will land you in the Polyglot 2 interface, perhaps what you are referring to generically as "polisy". https://<IP.ADDR.OF.POLISY>:3000 will land you in Polyglot 3 interface. of course in either of those examples <IP.ADDR.OF.POLISY> is a place holder, you need the actual IP address of your polisy on your local network, you can't literally type <IP.ADDR.OF.POLISY> (it might be obvious to some, but I didn't use to include this disclaimer and someone said "It doesn't work").

Are you running any node servers on Polisy? The ISY's credentials should be stored in the PG2 and PG3 menu, so that Polisy can log into the ISY as a user. In PG2, Settings > Polyglot settings. Should have the stored credentials of the ISY. In PG3, it's in the "ISY's" menu, edit current ISY, and the store the cedentials to the ISY there.

@larryllix I wondered in the other thread, but didn't ask... what does the TIME portion of that program actually DO and why is it NEEDED? I can't imagine the real world need? Is this a holdover from version 4 when some functionality needed to be added via programs? Well it can't really be that either.. .it uses repeat which i think came in with V5.

I wondered that too. I gave up trying to figure out why OPs original was behaving and just re-wrote it. Only thing is Kasa are Node server driven and i think it takes awhile for the node status to update sometimes, probably more when the queue is flooded.

AWS has many Servers. Wherever Alexa and her services are will show up on that page. Your portal accounts service probably only shows up on the dashboard if logged in as UD.

A cloud service that barely breaks even at less that ~$1/month to cover the cost of the Amazon Server it runs on. It's a cloud service, they break sometimes.

This was a server side failure, and there are no steps end-users can take to prevent it in the future. It could have been a myriad of things, some of which UD has no control over because the portal is running on AWS, meaning it might be purely an AWS issue.

I just edited refresh your page if you already have it on the screen.

This should do what you want to do.... Schedule tree - [ID 00C8][Parent 00EF] If From 7:00:00 PM to 03:00:00 AM (next day) Then Enable Program Alternate Christmas Tree $s.Christmas = 1 Else Disable Program Alternate Christmas Tree $s.Christmas = -1 Set 'Kasa Controller / Color Christmas tree lights' Off Set 'Kasa Controller / White Christmas tree lights' Off Alternate Christmas Tree - [ID 00C2][Parent 00EF] If $s.Christmas is 1 Then Set 'Kasa Controller / White Christmas tree lights' On Set 'Kasa Controller / Color Christmas tree lights' Off Wait 15 Min $s.Christmas = 0 Else Set 'Kasa Controller / Color Christmas tree lights' On Set 'Kasa Controller / White Christmas tree lights' Off Wait 15 Min $s.Christmas = 1 Disclaimer: I didn't test it, If you have problems I'll set it up here and see where it goes wrong.

You probaly updated the firmware on the TP-Link devices. That makes them incompatible with 3rd party products. Complain to Tp-link.

There is a product named eisy that replaces Polisy, new hardware, same OS and software as Polisy.

I gave you the answer, so did @bpwwer PG2 on Pi is dead. It won’t update. Stop complaining about it. Either make up your mind to 1) stay with the platform and update your hardware. 2) run it just like it is now without updating/upgrading anything or 3) find something else that better meets your needs.

PG2 running on a raspberry pi has been past END of Life for a few years now. More recently PG2 on Polisy has been deprecated because it has a replacement PG3. Polisy is also out of stock and has been since last May. Due to supply chain issues it’s being replaced as eisy… basically similar to Polisy, but different hardware running the same OS and software.

Forgot to mention that you get free product support for life. As @asbril points out just open a ticket. Sure support won’t set up and program your system for you for free, but other than that you get pretty much unlimited support, just open a ticket.

Don’t forget to mention the portal subscription at less than $1/month is the single best home automation value on the entire internet.

I didn't use it in Win10 either... never even been on that java tab to do anything...

I use windows 11 and don't (and never have) make use of the "Exception Site List"

This is a reboot: Tue 2022/11/15 04:57:46 PM System -5 Start did you manually do that or did randomly occur? Unfortunately it's not uncommon to see a bunch of nasty errors like UDQ: Queue Full in the minutes after a restart. The rather cryptic but sometimes useful error code listing can be found here. The concerning error that stands off the page to me is: Mon 2022/11/14 03:00:45 AM System -170001 UDQ: Queue(s) Full, message ignored which is not following in the minutes after a restart. that like means that your ISY is too busy doing something it shouldn't be doing. Possibly a run away program. You might find this via the program summary tab, sorting by activity column. We aren't interested in "Idle" Is there anything "running" that's probably not sitting in a "wait"? if so, those would be a good place to start. Do you have any problems with your internet connection? is it stable and "always on' or does it cut out sometimes? In general, that might be too small of a snipet of the Error log to check. You might also send the full error log to Michel support@universal-devices.com for his comments.

Check your ISY error log for clues to what’s happening. Is this a 994 or IoP running on Polisy? Error log is on the tools menu in the admin console. what version is the ISY running? there’s no direct way to schedule a restart for the ISY, but that would be a bandaid rather than the solution to the problem. for whatever it’s worth, I don’t have this problem. I’ve gone 6 months without have to reboot the ISY.