larryllix

Thanks but it didn't change the errors reported. In addition: pkg: Cannot get an advisory lock on a database. It is locked by another process

When running the line sudo pkg upgrade I get a bunch of these errors. process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock process with pid 1877 still holds the lock Do I need to shut down ISY process first or how do I get my polisy to upgrade? pid 1877 is found as pkg upgrade owned by root

Need to contact UDI. They can be very generous with deals for people.

That will depend on how computer adept you are IMHO. PolISY is coming along quite well but there may be a lot of challenges. However, it sounds like a good plan but may drag for some time yet. You could consider contacting UDI and ask about a rebuild ISY and/or rebuilding your own PLM. One poster claimed he bought a USB PLM and swapped the board successfully. Later it could be swapped back for your polisy. EDIT: I see just after I typed this Michel responded.

If I had to hazard a guess I would say the serial PLM will never be manufactured again. Look at Insteon's track record and what the guessers are telling us, here. By the time the serial PLM is ready to be manufactured again, there will not be any market left for them. We are constantly being told by the guessers that Insteon is trimming products from their lines that do not sell. Why use stock space fr years on products that do not sell? HCL

LOL! All good suggestions and nice catch about the State vs Integer variable type. @eyostDefinitely use the 's' prefix. It will save you a lot of agro later when you wonder WTF did I do here? More self-documenting with your code writing. I was leaving the 'c' prefix for later, based on newbie post count and comments about variable familiarity.

- hope SH makes a replacement serial PLM (appears not likely) - get a USB PLM and swap the boards - get replacement capacitors and repair your own damaged PLM / find a PLM repair shop - get a polisy and use a USB PLM with it (future) - dump Insteon products and go with ISY Zwave, WiFi, and other protocols - dump ISY and go with another HA controller - dump ISY and become semi-HA, remote controller user.

Yup! The main thing in programming is usually self-documenting code. That means, for variables, to gve them descriptive names that reading it later you know exactly what the value means. Typically and usually you would use a non-zero value (usually 1) for True, and a 0 value for False. You can manipulate the value later manually, or automatically from some device. I use the vacation setting from my ecobee thermostats with a syncing program. Logic = When the value changes in the stat, change the value in the variable. You could use a triple tap, or some other sequence, from a simple SwitchLinc wall switch. I use a sequence like that for my home security to enable/disable it. That can be explained later if desired. Just ask. You may want to set the init_to value to the same value in programs that set it. That way ISY will boot up with the last value you assigned it.

That is correct. The init_to value is the value that gets stuffed into the variable value as ISY boots up, before any variables get used in programs. Init_to value is not testable or otherwise usable.

OK. wild shot but...since the PLM port uses the same RJ-31 connector, you sure those aren't mixed up?

Did you try another Ethernet cable? The USB PLM should be good for your polisy box if you ever move over when the time comes.

Geeeez. That is an awesome video.

Don't quote me but IIRC the O wire controls the direction of the valves for cooling or heating. You may need to reverse the logic polarity of the contact open/close. Sent from my SM-G781W using Tapatalk

What real thermostat was running the heat pump before? Did you mark down the wire colours and connected terminal markings before you removed it?

Is there a way to tell how big the link database is inside any PLM?

Did you try replacing your Ethernet cable to your ISY? It is possible you have a broken or intermittent conductor.

Look for programs that constantly hit on Ethernet comms without enough break. Your ISY is likely complaining it is too busy to empty the Ethernet cache either going in or out. Look for flashing program icons and busy events scrolling by constantly. Check your program summary and sort programs by last executed, watching for constantly updating times.

AS per @Techman's post above. You run it from it's own app icon, not java console.

Second the ISY v5.3.4. It fixed a lot of small quirks.

I would do it in a flash but then I use many of the advanced features to use during programming and other features. It has been years and years since I used v4 so I am not sure what all the advancements are but decimal values are great. Maybe another user more familiar with the upgrades can chime in here. There may be some hassle to fix up a few program lines and scenes (usually highlighted in yellow) but once done it is permanent and never needs to be done again.

IIRC Michel posted a software switch that had to be enabled to use a PLM with pol/ISY, recently (about a week ago) . It seems pol/ISY installs with the PLM disabled so people can get it going without a PLM.

I am not sure what exactly is loaded down to google but it knew my whole setup when I tried to dump it. IIRC at the time I was trying to get GH to operate my devices, and after months of working fine it just wouldn't work any more. After a few months of trying everything it started to work again after giving up on GH. This happened again after several months of working and the same thing happened again. While nothing with GH worked, I tried to dissolve my account, including my google main account, as well as all my email accounts with them. When I reconnected the ISY Portal account back with GH all the devices were still there. Don't know how or why but after other AI attempts from GH to operate every device in my house I finally dumped GH and just supported my Alexa devices that didn't try to second guess my HA setup.

Mechanical thermostats on window shakers have thermal time delays built into the stats to protect themselves, usually. Not a foolproof method but it works 99.99% of the time if controlled from the knob. You want remote switching though. Run at Startup does not require program triggers to be enabled although things may have changed so testing would be the best. Not easy to test and requires rebooting your ISY unfortunately. I temporarily disable programs but it's usage should be done with care as a power interruption can leave programs locked out permanently until they are manually enabled again. Here is one technique I use to assure programs are enabled at startup. Program If [Run at startup enabled] some device is Switched On <----- switched constructs are always False unless device triggers this line Then do whatever you usually do Else enable program (self) run (then) program(self) <---- if Then run is desired

If you are trying to control a window shaker style A/C, they usually have a time delay built into the thermostat. If you are trying to control a central A/C unit you need a proper thermostat to avoid this fast cycling. You are playing with an expensive piece of equipment and a compressor starting backwards due to a mistake i programming, controls, or bad comms, can cost you a lot of money and agravation. Get a proper thermostat and control it with programs.

It appears the restore does work now, as reported in this same thread.