Techman

@greensuit Yes, there seems to be a problem with the Zmatter card not being able to set parameters and device status not updating. UD is aware of this and is hopefully coming out with a firmware update. @Chris Jahn Any progress on these issues?

@SteveT When you import your Zwave devices into the Zmatter card they will appear in the Polisy as ZY, that's by design per support. They are trying to reproduce the issue with the Multisensor 6. I also noticed that I'm unable to write any configuration changes to the Multisensor 6 My MS6 is also showing Celsius rather than Fahrenheit and I'm unable to change it, so there's definitely a communication issue between the Zmatter card and some Zwave devices. The problem started with the 5.5.0 firmware. Hopefully there will be a firmware update in the near future.

You can try a factory reset on the devices, then a restore device. It's possible that they got corrupted due to your previous issues.

Try the update again, if you're then still having a problem open a support ticket. Let me know what happens.

@Envirogreen It shouldn't take that long to update. Give it a little more time. You can also try removing power from the Polisy. If you're still having issues, then it's probably best to open a support ticket.

@Envirogreen If you do a package update, you'll get version 5.5.0 which has bug fixes. The 1011 means there are pending writes to that device. Right click on the device then click on "write updates" No need to do a restore device. Check to make sure the led on the PLM is lit. Also check your connection between the PLM and Polisy The UPS should have a FilterLinc between it and the powerline as it can interfere with the Insteon powerline signals.

Apparently, it defaulted to ON after I rebooted the Polisy. The Multisensor 6 motion is what triggered it. I don't see an "Assoc only" option.

Chris, I'm now getting a pop up box, when the admin console is open, every time the multisensor 6 motion is triggered. Note: The only device I have installed is the Multisensor 6 for testing purposes prior to a migration.

@Chris Jahn I sent in a couple of support tickets but they bounced back. Not sure if you received them. Here's the contents: 1. Zwave devices are showing up as ZY rather than ZW 2. Polisy 5.5.0 with current package updates, Zmatter board, Multisensor 6 When the motion sensor node is triggered, its status is correctly shown in the level 3 event log and in the Polisy status window. However, neither the level 3 event log nor the Polisy status window shows the motion off status which occurs 4 minutes after motion detection. The sensor motion display was correctly working with the Zmatter board and the previous Polisy firmware

@Ricka2 In Java, you need to clear you Java cache including installed applications Then download the admin console from this link https://isy.universal-devices.com/start.jnlp The ISY firmware and the UI must always be the same version.

I think as they've been changing the name over to Iox they haven't changed the menu items yet. It's the same with 5.5.0

I was able to update to 5.5.0 with no issues. However, when I pressed the "Move to Zmatter Z-Wave button" my polisy locked up. The only solution was to do a factory reset on the Polisy. The Polisy is now up and running but I'm unable to include any Z-wave devices. Prior to the firmware update I was using the Zmatter board with the Multisensor 6 as my test platform, and all was working normally.

@Deane Johnson The blue light is the power led. It's possible that your ISY power supply has failed. If you have another power supply, 12 volts, 2 amps, try replacing your existing supply. Are the leds on the ISY ethernet socket lit

Start by clearing your Java cache, including applications, then download the ISY laucher: https://isy.universal-devices.com/start.jnlp If you're then able to access the admin console report back with the ISY UI and firmware versions

If you want to start from scratch, then you would have to exclude them from the ISY and then include them into the eisy

Here it is.

The ISY994 supports a 32gb SD card. I'm currently using one as are many other forum members. The following is from the link you provided. "The ISY994i takes a MicroSD card. The max size is 32GB. Please look for a card with the newer A1 rating (A2 also works, but will fallback to A1 because the ISY994 does not provide hardware support required for A2). All other process steps below remain the same.]"

Also upgrade your packages in the Polisy if you haven't already done so. Current Polisy firmware is 5.4.5 Current ISY firmware is 5.3.4 After the upgrade(s) be sure to clear your Java cache including applications, then download the ISY launcher

In the Polisy configuration tab, is the Insteon box checked? Are you using the same PLM that you used with the ISY994, if so, you shouldn't need to restore it What is your Polisy firmware and UI?

I'm not familiar with the Bali blinds, but I use Zwave with my Somfy blinds. With Somfy you first have to program then using the Somfy remote setting the open and close positions. Once programmed they only recognize either open or close from the Zwave (ISY or Polisy) controller. Currently, Zwave scenes are somewhat problematic. Try creating a program, include each blind in the program then control the program via a zwave command or insteon command

The Polisy is being replaced with the eisy. The availability is pending. The specs are attached.

If you have the Zooz stick attached, then wait for a few days when the updated firmware is released

@CopyRon The following is from UD. Did you check your bios? --------------------- There have been two reports of Polisy not booting up after installing the ZMatter module. Initial assessments point to not having an updated BIOS/flash, insufficient power from the power supply, and possibly short circuit on the TPM board. As such, please do make sure you update the BIOS before attempting to install the module. Furthermore, please do ensure that Polisy is powered off when installing the module.

It's possible that the remote which has pending writes is causing issues. I would address that next

@bpwwer can probably help once he reads this thread.