dbwarner5

@TheA2Z Before you do the below, Conduct a regular backup Export a text copy of all programs: Go to programs and right click My Programs and select Copy Folder to Clipboard. Open text editor and paste, save. Migration of Elk: If you have the Elk module on the ISY994 you will need to install the ELK Node Server to restore ELK functionality. The node server version will have different node addresses and some slightly different naming. Programs that used the ELK have to be reconfigured for the new ELK nodes. After rebooting the ISY post migration and the ELK NS install, the programs that need attention will be highlighted in yellow as they show up on the programs/summary page. Refer to Program text file if backed up earlier for rebuilding. At that point it is just a matter of restoring the new ELK nodes back into the programs. Speak and query aren't available on version PG2 but will be added to PG3 in the future.

@TriLife The ones that are "unmanaged" are probably the ones that still reside on PG2 adn it looks like they didnt transfer. The simplest way to do this manually is to: -Go to PG2 and open each Config tab for each NS and screenshot the info you will need to reproduce on the PG3 -Make note of which slot they are in. -Delete the node servers from PG2. Wait for the system to completely clear them. -Open PG3 and install them into the same slot that they were in, entering in the config info from PG2. Patience is key to these steps as it make a take a little while for the slot to become available again.By doing it in this manner, you should preserve your programming in the Admin Console / IoX. To be sure, open the AC and go to the programs summary tab and click on the column for Activity to sort it and look for any YELLOW programs saying something like out of memory etc. Those programs may need tweaks.

Could be that. last night at 3:06, about 20 random lights turned on last night! Wife was not happy..lol I am going to open a ticket today.

Spoke too soon. Odd behavior again today. Zwave dongle suddenly quit working. Large amounts of 170001 and 140005 errors in ISY error log. Will open a ticket tomorrow thanks.

I don think 5.5 is ready for prime time yet, that is why I also have not upgraded. Once all the package and zwave stuff gets sorted out, I'll make the upgrade. In the meantime though, there should be no reason that things dont continue as they were, with the board simply installed and waiting to be activated, based on early comments from Michele. But clearly something must happen / be going on that does cause a problem, that for me seemed to finally get reconciled with about 10-12 unplugs.

@brians I dont think he is implying that the board should be working without updgrading to 5.5 Instead, he is experiencing what I experienced after installing the ZMatter board with zooz 700 stick. No changes to firmware / software. Running 5.4.5 w/o any problems for many weeks, then 1-2 days after installing the ZMatter board, doing nothing else, I started having problems. They lasted about 48 hours. Have not had any problems since my last unplugging. see my posts here with Michel's comment at the end. Thanks.

Dont you love having to troll the boards to squash rumors?? lol.. keep up the great work...

However, since I am using an intel Macbook pro that is still well into its first half life ( and expensive!), I cant run the UD mobile on my Mac, since it only works on M1 Macs. Wont replace my Mac just for this reason so will need to continue to use the AC....dont need anything new to it, but that it just still works!

Thanks Michel. During this time, I was always able to ssh into the polisy without any problems, where I did check which NS were running, and they all appeared to be running, So as you said, for some reason maybe one of them got stuck in some reporting / request loop.

you need 5.5 for the Zmatter module to work with zwave, but read all the posts about the manual intervention and challenges people are having first.

Agree, newer doors mostly need a coded signal to trigger. It's no longer as easy as attaching two wires. Very frustrating. I got around this because I had an extra "car opener" remote so I opened it and soldered wires to it to create the "coded momentary close" that is needed as if the button was pushed. My elk output relays, close the circuit as directed by IoX via automation, Alexa, Remote Link, cold temperature (heated garage), etc. A wired open/ closed door sensor, separate from above, reports to Elk the status of the door allowing "smart interactions" --> "Alexa shut the garage doors", IoX decides which of three doors need closing, blinks garage lights, sets a chime off as warning, shuts the proper door(s), and retries twice if needed and then reports back its results via elk announcements to a russound whole house sound system .... Once you figure out the work around for the garage door interface, they IoX is amazing as usual to do anything you want. Plenty here can help. Another option is to get a MyQ hub / sensor on sale at amazon for $20! if it will work with your doors, and then get the Polyglot for myQ https://smile.amazon.com/Smart-Garage-Opener-Chamberlain-myQ-G0401/dp/B08GD3D9YJ/ref=sxin_15_pa_sp_search_thematic_sspa?content-id=amzn1.sym.d5d2dbeb-b217-4d41-ad6b-bc4af55d7521%3Aamzn1.sym.d5d2dbeb-b217-4d41-ad6b-bc4af55d7521&cv_ct_cx=myq&keywords=myq&pd_rd_i=B08GD3D9YJ&pd_rd_r=66a04fc1-524c-4fef-b25b-34acf6ec5e9a&pd_rd_w=pYfJ2&pd_rd_wg=v7mgA&pf_rd_p=d5d2dbeb-b217-4d41-ad6b-bc4af55d7521&pf_rd_r=FYFHA1T0REEQGXHQ6BHQ&qid=1671388606&sr=1-1-a73d1c8c-2fd2-4f19-aa41-2df022bcb241-spons&spLa=ZW5jcnlwdGVkUXVhbGlmaWVyPUEyQ1pPVkwwMDU2N0o4JmVuY3J5cHRlZElkPUEwMTQzNDEzUVlCUkZTMTJEUlYzJmVuY3J5cHRlZEFkSWQ9QTA0NTU5NjgzSEVQU0sxQlU5SVJBJndpZGdldE5hbWU9c3Bfc2VhcmNoX3RoZW1hdGljJmFjdGlvbj1jbGlja1JlZGlyZWN0JmRvTm90TG9nQ2xpY2s9dHJ1ZQ&th=1

@Envirogreen what system are you at now? I had several problems with a recent ZMatter board adn 5.4.5. Unplugging the Polisy repetitively over a full day, finally seems to have stopped the problems. see thread here for any commonalities?

Update. Have been running the last few days w/o problems. Not sure what happened or if it has "cured" itself. Am guessing now that my original PLM was just fine.

I have had a lot of strange problems as well, same situation.. see my post / thread here..

Assume that the zwave migration issues though have NOT been solved?

That's why it's always important to include your programs in your posts so that the core issue can be identified quickly for you.. good luck! And By the way , if you need a state variable for a different program as a trigger, assume your switched the above variable to I_RainDelay, you can always add a line $RainDelay= I_RainDelay in the THEN portion. Lastly to protect yourself from power outages, I always include a line after a variable gets adjusted, to init (set the value upon restart) to itself as shown in this simple program below: Then $Dark_Mode = 1 $Dark_Mode Init To $Dark_Mode Set 'KP GR D DarkMode' On Cheers.

You may need to restart just pg3..or log into pg3, stop the NS.. wait a few minutes, restart it and then open AC and it should be ok

My only solution was to uplug it, let it sit for a minute or so and plug it back in and wait.. Still happening. Strange. The only thing that has changed is that I installed the ZMatter board. so there must be something going on. Am hoping that the migration for zwave gets figured out and I can upgrade to 5.5 and it may eliminate my problem Will be opening a ticket at some time, but know they are working super hard on the 5.5 issues right now.

After 3-5 more attempts to connect, there the AC finder, no longer finds the IoX, and the web access is returning errors as well.--> error, Loading: /config/ Was able to SSH into the polisy and send sudo service isy restart... IoX restarted, but when I go in via the AC, it isn't talking to any Insteon device, (much like it all started, so I thought the PLM was bad, probably was fine) Will have to figure out how to restart the whole polisy, probably via unplugging.. ugh.. UD mobile is partially loading, also has many nodes unknown. Portal web access loads but is all wrong. any help would be appreciated or I will open a ticket tommorow, but know Michel and the team are busy with the 5.5 roll out.

Update: Happened again--> disconnected from AC panel, reload gets stuck on Starting Subscriptions. Went to the portal and opened the web access page. IoX is running just fine there. Cleared Java cache, redownloaded the Java start.. started the AC again. No luck. Stuck on the same spot. No access via AC. Latest error log from IoX ISY Error Log.v5.4.5__Thu 2022.12.15 05.51.14 PM.txt

Spoke too soon.. Was connected via the AC for about 90 minutes, working on all my battery devices after the PLM change, and then got disconnected, now cant get past the Subscriptions starting screen when logging in. Attached is my error log if anyone has any ideas? Seems like it runs fine unless I spend too long in the AC.. then I have to reboot. Irritating at the least..:( ISY Error Log.v5.4.5__Thu 2022.12.15 04.36.52 PM.txt

Understand.. Have modified the program as follows and will leave it disabled. Made the command to run the IF of this program. Works as a toggle perfectly Alert Start /Stop LD - [ID 0043][Parent 001C][Not Enabled] If 'KP Hall to Master.A: Alert' Status is Off Then Set 'Keypad Alert' On Wait 1 second Set 'Keypad Alert' On Run Program 'Alert Button2' (Then Path) Else Set 'Keypad Alert' Off Wait 1 second Set 'Keypad Alert' Off Run Program 'Alert Button Off' (Then Path) Also By the way, I finally spend the time to really understand UD Mobile. You have done an OUTSTANDING job with it. While it's a bit overwhelming at first, once you get the hang of the amazing capabilities, you can really do just about anything. Also like that I can lock out edits and hide things like resources for on my wife's phone so she really on can see the favorites which are all color coded green for "good", red for "bad".....(two battery devices not reporting due to writes needed from a PLM change, but will be green as well.) Thanks for all your work!! Cheers.

Yesterday, awoke to find my IoX not responsive. Opening the AC, it was not communicating with any device. Checked PLM, said it was offline. Assuming the PLM had died, I replaced it with a backup that I had and did a restore PLM. Writing the updates took quite a while, battery devices writes were disabled. Took 2 or 3 attempts to get through it all. Throughout the whole day, I had trouble connecting to the polisy via AC: would get stuck on subscription services, or not connect at all. Portal would connect and could operate, but UD mobile and AC would not. A reboot would solve it, temporarily for 1-2 hours and then I would loose connections again. Did one last reboot at 430 yesterday and lo and behold, its been almost 24 hours and all is working as expected. Very very strange. So am now wondering if the original PLM really did go bad or not. Just throwing this out there. No further action needed at this point.

Asking for a friend.. he is on an earlier version of 5.xx, and does NOT have the Matter board installed in his Polisy with zoozs dongle attached. If he upgrades his versions, will it jump all the way to 5.5 or will it only go to 5.4? I was planning on upgrading him to 5.4, but am worried that if I upgrade him, he will go to 5.5 and suffer this initial transition issues, which I want to avoid as he is a newbie to this world. thanks

Agree, but I would rather not deal with bad migrations adn failures over a 6 week period if instead I wait another 2 weeks for a more seamless transition. Based on your history / posts of going to IoP, I think you would agree