gzahar

You can just plug that USB module into Polisy. You don't have to mount the board internally.

There’s now a communications speed setting in the Zwave menu.

Update w/interview didn't make a difference. I'm tired of updating my programs every time the ZY address changes, so I'll hold off on remove/include for now (until I hear it will fix something). The X-ray always shows Interview as not done, but here is output from event viewer. Thu 02/02/2023 04:38:55 PM : [ZW-INTERVIEW-37 ] Add interview request for 46 Thu 02/02/2023 04:38:55 PM : [ZW-INTERVIEW-37 ] Interview started for 46 Thu 02/02/2023 04:38:57 PM : [Device 46] Waiting on interview complete (timeout in 392) Thu 02/02/2023 04:38:59 PM : [Device 46] Waiting on interview complete (timeout in 397) Thu 02/02/2023 04:40:29 PM : [Device 46] Waiting on interview complete (timeout in 26) Thu 02/02/2023 04:40:31 PM : [Device 46] Waiting on interview complete (timeout in 0) Thu 02/02/2023 04:40:31 PM : [ZW-INTERVIEW-37 ] Device 46 : Interview Done with some non-conforming features : total=22 successful=20 attempted=22 Thu 02/02/2023 04:40:32 PM : ZWAVE-WORKQ-34 Queue sync device 46 (initialize) Thu 02/02/2023 04:40:32 PM : ZWAVE-WORKQ-34 Start sync device 46 Thu 02/02/2023 04:40:32 PM : [ZWAVE-SYNC 46] Attempting to reuse ISY files/objects for Z-Wave device Thu 02/02/2023 04:40:32 PM : [SYNC-DEVICE 46.0] Set commands are accepted by the controller Thu 02/02/2023 04:40:32 PM : [ZWAVE-SYNC 46] Not multichannel Thu 02/02/2023 04:40:34 PM : [SYNC-DEVICE 46] Initializing associations to ISY Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-35 Queue write device updates for node 46, full=false Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-34 Finished sync device 46 Thu 02/02/2023 04:40:34 PM : ZWAVE-WORKQ-35 Start write device updates for node 46, full=false Thu 02/02/2023 04:40:35 PM : [ZWAVE 46.0] Association Set in group 1 : Controller 46.0, Responder 1 Thu 02/02/2023 04:40:36 PM : ZWAVE-WORKQ-35 Finished write device updates for node 46, full=false

It doesn't seem to have fixed the update issue. Disclaimer: I didn't catch the beeps and pull the power. IoX did reboot and the AC came up showing the new firmware/UI version (w/o needing to clear Java cache either). Possibly some other updates may happen when/after rebooting the whole system or clearing Java.

Is there going to be a separate thread for 5.5.5 or continue using 5.5.4? Also, in the installation notes (not new to 5.5.5) it says: Launch the Admin Console, go to the Configuration tab, click on Update Packages. Warning, this might take a while depending on how current your OS is Once completed (4 beeps + 1), unplug Polisy I thought in the past it was recommended to not just pull power on Polisy (/eisy by extension) but use a shutdown command first. Has this changed?

Copy Folder to Clipboard.

On the configuration page, make sure Insteon support is still selected (did you hit save before rebooting). Restore Modem (PLM) is under the File menu. Try Tools, Diagnostics, PLM Info/Status. Edit: Did you reboot the eisy or just the IoX? Probably need to reboot eisy.

Will do. Pressed a lot of keys today trying to get it to happen again, but no luck. I've written a program to notify me if any key is not in idle for more than 10 secs. So if it happens again, I should be able to find it in the logs.

I have two that are at S0 from migration and one at S2 that I (re)included after migration. I don't use the ones that are at S0 that much (so I didn't notice), but just tested and they do seem to report manual changes correctly (small test sample). The one at S2 needs a query to pick up the manual change in status. Not sure if it is S0/2 related or pre/post migration inclusion. I thought there were some security options when I included the one lock. I may take another look at that.

I was referring to this (in README.md). Timeout that switches key between Pressed and Held can be changed via "Idle Threshold". Will put in debug mode. Thanks.

same here

Yes, pressing the keys again reset them back to idle. I had a button stay in pressed state this morning. Here are the lines from the log: 2023-01-31 10:35:57,756 Thread-4 udi_interface.interface INFO interface:addNode: Adding node IR Button A(irbutton_104) [None] 2023-01-31 10:35:58,527 MQTT udi_interface.interface INFO interface:_message: Successfully set irbutton_104 :: ST to 0 UOM 25 2023-01-31 10:35:58,622 MQTT udi_interface.interface INFO interface:_message: Successfully set irbutton_104 :: ST to 1 UOM 25 You can see the last line left it in state '1' (pressed). This was not a new button/node, so not sure why it had 'Adding node IR Button'. Also noticed there are new installation instructions. I am still setup using the reset_flirc.sh process. I don't think that has anything to do with it, but I will update my ssh installation (ns was already at 0.1.8) Lastly, in your config instructions, I think you meant to say 'Press Threshold' in the last line (not Idle again).

I'm not sure how or when it happened, but I noticed a number of keys showing up in pressed state. This persisted through a reboot of the Node Server. You might consider initializing all keys to idle on startup, unless there is some negative impact to that.

If you have devices using the rest interface (or other node servers), then you would have to update the port setting on all those devices/servers. I have half a dozen Shelly devices that I had to change the port settings on to talk to Polisy vs ISY (but since I chose to make the IP address of my Polisy different than the ISY, it was not a step I could have avoided anyway). With 2 to 4 setting updates per device, I had close to 20 changes easily. But in the whole process of migrating, it was definitely one of the quickest/easiest things I had to do.

I do not know how to change it, but I am pretty sure they wanted it locked (probably not in a binary) to reduce support issues. PG2 uses/used the 80/443 ports (http redirects to https) and setting IoX (the ISY running on your eisy) to those ports, would conflict with that. I know they deprecated PG2, but I think it is still there and running. You could try opening the IP address of your eisy in a browser to see if Polyglot responds to the 80/443 ports.

Here is a Flirc config file that has the 40 ISY994 IR codes mapped to keyboard keys. Sorry for the scattered key map, but I had a few keys mapped based on their usage in my system. ISY my_flirc_config.fcfgISY IR Flirc key map.txt

When I first open the program tab I see the same thing (wrong/old title or entry #). But after opening the customization tab and then going back to programs tab it shows correctly (until I close the AC and reopen). As far as I can tell, when the programs run, they use the correct notification. Also, I did open a help ticket on this. Haven't noticed this regarding variables, but really haven't looked (or changed/added many variables since migration). After you opened the variable tabs, have you gone back to the program to see if they display correctly?

For some reason the node server doesn't like anything mapped to keys 0-9. Easy to work around by mapping to other keys (e.g. F1-F10). So possibly doesn't need to be fixed, just documented not to use them. Other than that, it works great for me. Thanks for developing! I've been working with the 40 default ISY IR codes. Once I get the last 5 added to flirc and tested, I'll provide the flirc config file and keyboard mappings so others won't have to go through the trouble of that step (if you're converting from using ISY IR).

S0 was leftover from Zwave migration. S2 was after I excluded and re-added one. (I will eventually remove & add back the 2 still at S0 when I have the time)

Yes. Tried on both a lock included with S0 and another with S2. Lock firmware is 0.11.0 Polisy is 5.5.4. Zmatter - Beta

That may be problematic for dimmers. Wouldn't going from 50% to 70% trigger the program?

Yes, around 16. Some being more active than others. Not saying it is slower than 994, just expected it to be noticeably faster.

One might argue that a minute is rather long for that amount of data. My backup was almost 7 minutes (with same Java parameters) on Polisy and almost 400KB in size. (Local AC with no wifi in in the picture) Maybe there is (Zip?) compression going on that takes time or just a low priority in retrieving files from Polisy so that it is not bogged down by the more important tasks it needs to do. Having said that, I don't normally need to make backups often, so it is bearable. But I agree it seems slower than I would like!

5.3.4 is latest firmware for ISY994. You can not update to 5.5.x. Those are only available for Polisy/Eisy.

I'm seeing the same thing. Most functions seem to work except motion stays on and temp is in C.