Techman

After the update did you clear your java cache and its applications, and then download the ISY Launcher?

Take a look at these threads:

Increasing the hold time should correct the program not running.

You're correct. Are you using Momentary or Latching in your I/O Linc to trigger your program? If you're using momentary then the Momentary hold time may be too short to trigger the program. Another possibility is that the wires going into the I/O Linc are not making a good contact, try tightening the screws.

Being that the processor and memory in the Polisy is much faster than the ISY, try increasing your wait times and/or adding waits to see if that makes a difference.

Take a look at this thread Don't use auto discover when you link it. Try putting in its address.

Yes, but being that's it's RF only you should have a dual band device close by to insure that the signal gets onto the powerline. I don't think you can do a ISY migration to the 24487A which means that you will have to build you system from scratch so I would focus on trying to clear up the PLM issue first.

Your link count is too low for the number of devices, especially if you have keypads with numerous nodes. It's possible that your restore file had issues. Did you do an ISY backup before you migrated over to the Polisy Try removing power from the PLM and Polisy, then power up the PLM wait about 30 seconds then power up the Polisy.

Your PLM link count sounds low. How many devices do you have? A low link count could mean a failing PLM or the restore / restore file has issues. Run the link count again as it can vary depending on the Polisys activity. You can also try running a diagnostic | compare link count between a device and the Polisy to see if there's a link mismatch.

Aeotec sells one: Bypass to stop low-power lighting from flickering (aeotec.com) All their tech specs are posted along with the product description

Chris, I just heard back from Aeotec, apparently, it's a misprint in their manual. They only support 1,2, or 4. However, when I query parameter number 41 which has a parameter size of 4 I get a value of 1311232 when it should be a default value of 20. I guess it's a bug in their firmware.

Hi Chris, Aeotec uses a parameter byte of 3 in about 3 of its configurations. I noticed that both the ISY with firmware 5.3.4 and Polisy are missing this value. I also noticed that you have an option 1,2, or 4 bytes (unsigned), when would that come into play? Thanks for following up.

It appears to be a firmware bug. What hardware are you running? What's your firmware and UI version

@Michel Kohanim The Polisy only allows for a parameter size of 1, 2 or 4. I need a parameter size of 3 for the Aeotec Multisensor 6

There's a bug in the program. It shows custom location and I'm unable to change it. Rebooting doesn't correct it. Sunrise and sunset are still off by 1 hour, but time is correct. I have all the latest package updates for the Polisy.

It appears that the Polisy Sunrise and Sunset parameters didn't adjust for daylight savings time

The Zwave dongle in the ISY has an effective range of about 20 feet. You'll need either a repeater or additional Zwave devices, which will repeat the RF signal, in order to have an effective Zwave mesh network. Insteon is no different, it is also a mesh network which requires devices to repeat its signal Zwave is a RF only protocol and cannot be converted to Insteon. A good Zwave repeater such as the Aeotec repeater will repeat and amplify the Zwave signal and would probably solve your problem

At this point in time no one really knows. We've gotten mixed messages from Smarthome as to the future status of their inventory

The $80 price is from a 3rd party reseller, Aeotec usually sells them on Amazon for about $62

The Aeotec Zwave Multisensor 6 works flawlessly with the ISY and has great tech support from Aeotec. They are scheduled to release the Multisensor 7 but are delayed due to parts shortages. Their link is below. MultiSensor 6 Z-Wave motion, light, temperature sensor (aeotec.com)

If you click on the TPM button it will ask you to create a strong password. You can either move forward with enabling TPM or cancel, your choice.

Updated via SSH Polisy is now back to normal I was also able to update the pending (4) packages via the Polisy IP address

The bugs are being addressed, see the link below.

I verified, via ssh, that the 5.4.0 update was successful but I'm unable to reboot polisy from the admin console or by logging in via it's address. Still no beeping from the Polisy and I now have a solid left led and a flashing middle led. When I log in via its IP address it shows 4 packages available for update but now the update command doesn't work

Pushing the reset button 6 times cleared the flashing led issue. Previously I was also getting an error message when I tried to access the admin console via the cloud, that issue is also cleared up. I still am not getting any audio beeps when I reboot the Pol;isy I also just noticed that when I try to reboot the Polisy from the admin console nothing happens.