larryllix

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.

I can imagine a bunch of webpage HTML being too big for my 3.1GB of user space left on my polisy box. Mind you. You never know these days. Code is not very compact anymore.

Takes a factory reset?

Is there a way to uninstall v6.0.0 and go back to v5.9.x if needed?

My router always started acting up about 44c on top of the case. This seemed quite low but the internal of the CPU would likely be more like 100c inside.

I think we are getting left behind. I asked the same question when the HTML UI started to be released.

Check your router DHCP reservation table for the ISY IP address assigned to it and manually enter it into The ISY finder app.

Just standing things up vertically helps a lot in most cases. (pun noted)

I don't know the purpose of having two account would be but ours asked us about each voice a few years ago. Now it recognises each of our voices just to act personal. I do not see any purpose for it. After many years usi g ten Alexa boxes I thought I would try asdigning devices to room groups as they constantly pestered me to do. For already named devices that is a mistake as a device named 'kitchen lights' and a room named 'kitchen' totally confuses Alexa and I get back that 'kitchen doesn't support that' or 'there is no such device named kitchen' Sent from my SM-S711W using Tapatalk

Who would write an http: driver that isn't backward compatible with the accepted protocol for what 20 years? Very weird for such a new protocol standard.

In view of the tech updates n the PLM, I would get one and keep it as a backup unit. If you cannot re-furb the older one, you have a head start on the replacement timing. I would avoid the RS-232 (serial port) PLM, as new microCPU boxes do not support RS-232 typically. It is a dying/dead interface.

If there is some complete scrambling of the link table, and/or crashed firmware inside the PLM, it may help. However, if the PLM link table is an antique with only 256 link spaces, and you are overloading it (likely these days), then nothing is going to help that PLM except to remove many links (scenes, devices) ie: use for a smaller system?

REST commands use GET, not POST. This may depend on what device you are talking to though.

No. AFAIK the PLM has a simple self management system for links inside. The link overflow is when the attempted amount of links becomes more than the hardware would hold. This was subsequently replaced by about 1024 links of space and then about 2048 more recently, IIRC. I am not sure ISY can tell when the PLM is full making the link storage unsuccessful and we get weird things missing but other parts of the Insteon remote device may work fine. Each Insteon devices uses up about 3-6 links spaces, basic, plus one for every scene it is used in.

Weren't the earlier PLMs limited to about 256 links in their EARROM space? This sounds like the old problems returned.

My bad. I thought the thread was about him replacing the old one.

I don't believe this to be completely correct. Every Insteon device contains a link or many links that only address the current PLM IP address. When you chage that PLM IP address, every device needs to be reprogrammed to the new PLM to be able to communicate back and forth. The comms between any Insteon devices an another Insteon device (including the PLM) is/are scene link(s) for each logical portion of the device. ie: statuses, commands from other and every ISY and device scene it is involved in.

It isn't that bad but when you do this once in a decade and there is not a lot of docs on a recently updated feature (as CPU based tech is these days, especially UDI products). Once you figure out the process on the first one and go with it, it accelerates. IOW: My experience may be biased because I am a sucker for "bleeding edge". UDI has so much more techie labour assistance, these days.

For AC operated devices it is very easy with ISY tools. With battery operated devices it is a PITA. Each one needs to be put into linking mode and done individually. Until they are converted they will stall the process until each one's process gives up repeatedly. With 12 x MS-1s and 5 leak detectors, on batteries it usually took me the whole 8-10 hour day.

A common problem was oxide on the SD card contacts. Try a white pencil eraser to buff the gold contacts on the card and maybe after or instead use a q-tip with rubbing alcohol (99% is best) on it to scrub the gold SD card contacts. Contact cleaner is best if you have it.