btreinders

After upgrade packages and reinstall of all plugins I still got the Ecobee midnight failed and reconnected notifications. @DennisC I have not received any other failed/disconnected and then immediate reconnects for wifi device plugins since though so hopeful it fixed those. Time will tell I guess. Thank you! @Jimbo.Automates I will try to pm you the logs again but for some reason it never finishes the upload on a pm. It won't let me here so assuming the same for a pm. Just says uploading and never finishes. It's only 4.7 mb.

I was unable to delete it once I rebooted the Polisy. But then I still could not reinstall it so I rebooted again, once to be able to delete it and once to see if I could then install it. Nothing worked. Restored a backup and all is up and running again. Had to go into the AC and save all programs that had plugin devices from slot 21 though. They were all yellow for status. I will now use the reinstall all plugins just in case the restore does not install them.

Yes, it is on the system tab. I had already started installing them one by one from the purchases page and not my plugin in slot 21 will not reinstall and I can't delete it either. If I have to install in another slot it will mess up all my programs. Wish these upgrades always went smoothly. I guess I'll restore PG3x and try the reinstall all option.

Thank you! I'll give it a shot. Do you have to reinstall all plugins one by one? Or can you just keep going or even use the reinstall all plugins option?

I was also working with him on this issue. I have many plugins that randomly send these, seems to be ones with wifi devices. It was just Ecobee that was every single day at midnight. Do we know when the fix he made for you @Jimbo.Automates will be available for everyone? It is very annoying to get these notifications all the time when nothing is really wrong.

Is it normal for the Ecobee plugin to send out a notification to the mobile app at midnight every night that it's status is failed and then immediately send one out for connected? Maybe it is PG3x that does that but either way I get those two messages every night at midnight for some reason. Thank you.

@ACastiglione I am seeing this exact same thing now. Did you figure it out?

Thanks, I don't think any of those are factors here. I can watch in the app when I manually set a state variable in the AC and it detects the motion in the Alexa app. I created new routines using that motion and they do not get triggered. If I manually run the routines they work. Guess I'll try to contract Amazon. I really only use them as notification speakers now anyway so it's not that annoying and I use the ELK M1 for notifications as well but it is much more restrictive obliviously.

I see about a year ago this happened and to me it is happening again. I can see that the device sees the motion in the Alexa app but the routine will not trigger because of it. I have even tried reconnecting the V3 app and recreating the routine. Still nothing. Anyone else having this issue?

I can confirm that this morning the sunrise and sunset values are correct. One issue I did have was I thought I outsmart it and change to eastern time yesterday. That did not work out well, it put a a system busy pop up and would never go away. Had to reboot to get it to eastern and then again to get it back to central time.

On the latest version for sure and just pulled power for a minute and then booted it back up. No joy. Still has both one hour off. Has them both an hour early.

My Polisy has sunrise and sunset off by an hour this morning as well.

@bmercier The core time stamp is 11:31 PM on the 18th. I have attached the Kasa log file from that time. Nothing stands out to me but it might to you. Kasa Core Dump Log.txt

@bmercier The large one had a python3.9.core file in it that was 465 MB for the Kasa NS.

@Geddy I am running 14 "Plugins" as they are called now. That is a good point, it could be log files for sure making them inconsistent. I have been playing around with those. We'll see if @bmercier or @bpwwer might be able to confirm that but to go from 1.9 to 22MB from the morning to the afternoon the same day seems very odd.

I did that years ago on the ISY and kept it on the Polisy. And to be fair, on my Windows PC that runs 24/7 for camera DVR and Home Assistant Pi as well.

I assume the normal upgrade process is to be used for these unless otherwise stated? Upgrade packages from the AC instead of the reinstall all node servers option in PG3x? Thank you.

Is anyone else seeing very inconsistent backup files sizes? I was getting around 1.9Mb in early Sept. Then it switched to around 28Mb for a few backups and now with 3.2.10 it is around 14Mb. I even see a while back that I could take one backup and it was in the 1.9 Mb size and then immediately take another and it would be in the 20s. See image

In case anyone else gets a corrupted Polisy SSD here is the procedure from UDI for restoring the SSD. I had mine get corrupted upgrading to IoX 5.7.0. You need a mSATA to USB adapter, something like this. Download image: Download https://udx.s3.us-west-2.amazonaws.com/os_images/polisy.131.img (it is about 3.5G in size) Unix: dd if=/dev/zero of= bs=1M conv=sync status=progress (this clears the contents) dd if=polisy.131.img of= bs=1M conv=sync status=progress Windows: Connect the SSD to the adapter and plug into your computer (USB) (you have to remove a small security board first to get the SSD out of the Polisy) Download Rufus from https://github.com/pbatard/rufus/releases/download/v3.20/rufus-3.20p.exe and start it Click on Show advanced driver properties and make sure List USB Hard Drives is checked The Device should show you something like EFISYS (Disk xxx) (32GB) From Boot selection, choose Disk or ISO image (Please select) and then click on the Select button which allows you to pick polisy.13.img that you downloaded previously Click on the Start button Final Step: Once done, unplug, take the SSD card and plug it back into polisy Don't forget to plug the security board back in as well. Once booted up, go to Admin Console | Configuration tab | and click on the Update Packages button. Wait for 4 beeps + 1 at the end At this point you should be able to restore your IoX backup (hopefully you have a recent one) I also had to do a restore PLM for some reason. I had all kinds of communication errors with Insteon for some reason. Zwave for the Zmatter USB was fine. I don't use Zigbee from the USB dongle yet. I had forgotten to do the PG3 to PG3x step before I restored my last PG3x backup which caused me issues so don't forget to go to PG3x if you were on that version when you took a backup.

If you are really on PG3x somehow then the username is now the same as the AC.

@johnnytYou wouldn't want to post that image somewhere would you?

UDI should at least post the SSD image somewhere with instructions on how to re-image it for people not afraid to do it. Not having water leak detection right now worries me. At least with Home Assistant I do have some functionality but yes the Polisy and eISY need to be able as a user to fix when they go down. This wasn't even my fault. I did an update packages and this is what I got.

My Polisy is still down hard and I am freaking out. So dependent on this automation now! Ticket opened, @Michel Kohanimresponded a few times on Friday and nothing since. I am assuming I need an image of the SSD installed which I am sure I can do if I just had one. Hopefully they respond today.

Huh, well I am not smart I should have made those energy values init values when they change! Doh!

I lost my monthly energy usage data stored in state variables when I did a restore so I guess I don't understand why you think that data is backed up.