larryllix

Here is the variable reset program I use to eliminate two of the three lines required to send routine triggers in my Alexa speakers. It could be used for anything but the variable names are significant for my speech routines. To use just set the appropriate variable to $cTrue (=1) I didn't create it into multiple programs. Instead I put them all into one lump and it works just fine. Note: spare variabes spsaces left for future epansion. It happens. Reset sSay variables - [ID 006F][Parent 0002][Run At Startup] If // [Run at Startup] enabled $sSay.motionOutsideDoor is not 0 Or $sSay.occupancyTimerExpiring is not 0 Or $sSay.securityViolated is not 0 Or $sSay.welcomeHome is not 0 Or $sSay.systemArming is not 0 Or $sSay.systemDisarmed is not 0 Or $sSay.goodBye is not 0 Or $sSay.turnOnLights is not 0 Or $sSay.systemArmed is not 0 Or $sz_40 is not 0 Or $sSay.blindLowBatt is not 0 Or $sSay.blindJammed is not 0 Or $sz_43 is not 0 Or $sz_44 is not 0 Or $sz_45 is not 0 Or $sz_46 is not 0 Or $sz_47 is not 0 Or $sz_48 is not 0 Then Wait 10 seconds $sSay.motionOutsideDoor = 0 $sSay.occupancyTimerExpiring = 0 $sSay.securityViolated = 0 $sSay.welcomeHome = 0 $sSay.systemArming = 0 $sSay.systemDisarmed = 0 $sSay.goodBye = 0 $sSay.turnOnLights = 0 $sSay.systemArmed = 0 $sz_40 = 0 $sSay.blindLowBatt = 0 $sSay.blindJammed = 0 $sz_43 = 0 $sz_44 = 0 $sz_45 = 0 $sz_46 = 0 $sz_47 = 0 $sz_48 = 0 Else - No Actions - (To add one, press 'Action')

Nice! KInd of odd the semaphore has to go to Germany and back. LOL Wow!

I have had problems on and off with Alexa routines triggering also. This has happened a few times over the years. Alexa app shows the input points changing , the routines fully working when triggered manually but they just wouldn't trigger. After complaining each time, and Amazon denying any problems, and advising to contact your app writer, it would suddenly start working again, once after about a month.

Strange ,I have not heard anything regarding Alexa+ before. If there is any option I would likely stick with the old Alexa also. AI garbage is why I dumped Google Home boxes, years ago (have about five in the junk box now). Every time I would ask GH to turn something on it would find every device with X in the name and attempt to turn it on at the same time. When I have 8 different colour names included in Bedroom light strip, turning them all on at the same time is impossible. AI doesn't belong in home automation. I don't need somebody else's logic controlling things for me randomly. Guessing on meanings is not wanted in HA, only exact control names. AI guessing can be dangerous in some situations. Alexa used to ask "did you mean?" so I dumped my GH junk and went with Alexa in every room years back.

@bmercier I have not had problems with Alexa so far. However I have not been asked or offered to upgrade my Alexa skills etc..

I have to replace my 6-8 batteries about once per 4-12 months, brand dependent. However I have found when one brand gives bad length of service, other brands also do. My conclusion s mots batteries are made by the same manufacturer. I have been trying to find brands manufactured in Japan. reports show some Panasonic and a few other brands are made in Japan and may last longer. I don't use them with PGx but rather kumoapps code. Does the PG3 NS not allow programmable updates that could save battery power by reducing polling at nights etc..?

Is the program disabled? We cannot see that parameter unless you copy to clipboard and then paste the program into the post. Right click the program title and select "Copy to clipboard"

Both my Polisae came with 32GB SSDs. Now they both have 64GB. One went bad and one has survived but totally spare now. For $26 I wasn't going to return it. I think the partitioning had to be based on an old SD card format , saving some small hidden partition for recovery images etc... Expanding that to 32GB made the remainder seem huge. @Michel Kohanim is reading this and laughing!

If you get supplied with the file poilsy_14.3p3.img then your polisy SSD will be at the current V6.0.x when it boots up. Watch your credentials on the IoX Finder, set time zone, options, etc. and reboot.

Right click on the device in the device tree and select "Restore". There is likely a link missing yet. Devices have a link to the PLM for every function, sometimes 10 or 12 links. They can all work properly except one at times.

Most of the time I have had to manually type in my URLs for my Polisae. They are seldom found by any of the finder apps that have been released. If, and when, the finder app finds your Polisy then you would use the same credentials you use for your ISY Portal login. In my case this was my email address, not "admin". This is in the usual IoX Finder login box with User: and Password: after you click the URL in the Finder. I had a lot of trouble with this. My Polisy was not producing it's UUID, (was 00:00:00:00:00:00) and then nothing would find it. After switching my SSD from one box to another I suspect I may have not plugged in the dual header security module properly. IIRC that would cause this. If you didn't have your Polisy box apart this wouldn't apply to you.

Both my Polisae work fine now but I re-imaged both of my Polisae. I am not sure I needed to do that or buy a larger SSD either. I don't see any SSD crowding or excessive usage of RAM on either. However, I did discover the long way around to login with my email address instead of "admin". I suppose that is what the obscure message to use ISY Portal login meant. In the end I believe that the update attempted to increase the partition size of existing Polisae SSDs and it messed up on most of them, maybe the older units?

I discovered the hard way after destroying two Polisy systems that I had to use my email address instead of admin. Thus the warning to use my ISY Portal security.

I was supplied a completely new image for my drive. It may have contained a larger partition....not sure. Not sure how I would tell. This sounds like the update overran the partition size and crashed the system. This may have been the basis a previous the "memory space" limitation in Polisy systems. Actually SSD partition space.

Open a ticket with UDI. They will be on you in hours usually. Not on Saturdays though.

A support ticket should tell you what you need to do. It is a lot easier than I thought. Open case Snap SSD drive out of clips Slide SSD into USB holder/adapter (UDI will give you link to advert on amazon. ~$10) Plug in adapter to USB port Run Rufus software (free) Select SSD drive Select image UDI supplies Start Put SSD back into slot Close up case Reboot Polisy Run IoX Click update Load your files back in.

Read my guess above.

After updates (not both v6) I have two Polisae crash my SSDs. I suspect that the intensive wear and tear on the SSD devices doing this major update just finishes off the SSD that are already on the edge. Michel made a comment to me that cheap SSDs do not last long and I am guessing "cheap" means the smaller memory drives that possibly have less memory saving algorithm space. In my case, I have ordered another 64GB SSD (larger than the stock 32GB and $27 CAD), I already have a USB/eSATA adapter ($10), and Rufus, the imager software, but I have destroyed my existing image files, so I need support to offer me a later download link yet. The SSD fix is easy and quick, but takes reloading and updating everything. Not necessarily your problem but it can be a fix or a backup for future problems. Best of luck!! Polisy does take a long time to update and reboot. I imagine eISY would be the same thing. Others have reported over 30 minutes for bootup. The update is major.

I have two images of the polisy14.image (not 13). However, one downloaded corruptly (at the time) and the good one, I just overwrote from the imaging software. Michel had sent me the link also but I cannot find any trace of that link now. Any clues?

Two items. I found that Rufus would not format or deal with an SSD larger than 32GB. However I found DiskImager.exe handled it no problem with larger SSD sizes. Where do I find these polisy13 images. I have an apparently bad image and one that I just ruined by loading the old image over top of the polisy13 image. I am currently attempting to start one of my two polisae from scratch again and can't figure out how to get this image on the SSD again. Michel had previously emailed these to me, but I cannot find any trace of the file in my backups or emails or support tickets. (responses all seem to be missing now)

I will be doing that also. I tried that last time but the SSD was pooched and not recoverable. I have ordered another SSD and if I read this right, the larger drives have more RAM and space for the bit gate protection schemes used to slow down memory wear and tear. The SSDs included in the Polisi units were too small and don't last long. This is my second Polisy SSD burn out now. Sent from my SM-S711W using Tapatalk

Every time I rebooted my polisy it got worse. Now it won't even boot up. No SSH or IoX access anymore despite replacing the spare SSD from my spare polisy. I ordered another new SSD to start over again. That is two SSDs tgat destroyed themselves with upgrades this year now. I am about to give up. Sent from my SM-S711W using Tapatalk

Now I just get "You must reboot your system" messages constantly, mixed in with the "Do not reboot your system" Strange that REST inputs to variables and WiFi, PG3 items all seem to function but programs do not trigger or complete. Looks like a re-image SSD is going to happen, again.

My v6.0.0 upgrade destroyed my SSD in my Polisy. With the forum down last night and now my PLM not functioning for some parameters I am really stuck. PLM Restore, attempting to restore devices, factory resetting my PLM and starting over doesn't seem to do a complete repair. A new SSD brought some things back up. I am stuck. My WiFi devices seem to function but Insteon devices are pooched. I paid for a new subscription to ISY Portal because my spare Polisys wouldn't connect and I couldn't discover how to port my subscription over to it. Now I have two subscriptions despite it forcing me to open another Paypal account. This thing is a non-functional mess now and still showing v5.9.1.

Whatever your SouthGate or NorthGate does will trigger evaluation of your program. If anything triggers evaluation the two times with never be true and Else will always get run. Time triggers are always false unless THEY, THEMSELVES trigger the evaluation, even if the time is exactly the same time. Single time triggers cannot be used for logic filters. FIX? Change your NorthGate and SouthGate variabes to INTEGER types so they don't trigger your program, and only your times trigger it.