larryllix

Make sure you announce the PLM if you have one. People will be interested!! Sent from my SM-G781W using Tapatalk

The z in the name is so these sort to the last position order when looking for a variable in programming.

Nothing like self documenting code/variable names.

Make sure to set init-to to the same value so it never goes away. Also I found a bug that the last integer variable value gets cleared upon reboot. IIRC this was on ISY v5.3.4 so not likely fixed yet. I installed a dummy extra variable and it stopped disappearing. Sent from my SM-G781W using Tapatalk

I have inherited a 300 Zwave board. it has the LED and not sure if I want to break into Zwave yet but would like to test some things. IIRC it was v5.0.16c ? Do you remember the highest V5 version that can support it?

Gotta' love the way web pages constantly change their style. Just when you get familiar with something it changes locations again. Now feature buttons at the bottom of the pages where browsers sometimes can't even display them?

I have just started to try ISY on polisy. My LAN just became stable after a few years of fighting with three defective routers, so I have delayed trying to port ISY over to polisy until now. I didn't think it would get more complicated than this.

Not likely for hours Only the upgrade itself has been run. Here is what happening. I just noticed it complaining of a package not found. [admin@polisy ~]$ sudo pkg update Password: Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 107 KiB 110.0kB/s 00:01 Processing entries: 100% udi repository update completed. 399 packages processed. All repositories are up to date. [admin@polisy ~]$ sudo pkg upgrade Updating FreeBSD-base repository catalogue... pkg: https://pkg.isy.io/FreeBSD-base/FreeBSD:13:amd64/latest/packagesite.pkg: Not Found FreeBSD-base repository is up to date. Updating udi repository catalogue... udi repository is up to date. All repositories are up to date. 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 pkg: Cannot get an advisory lock on a database, it is locked by another process [admin@polisy ~]$

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.