dbwarner5

yes those are all true.. if you read my post above, you would see that it works just fine locally.. It's when the UDI server gets involved, things dont work. I would not be getting values locally if what you asked was not true

@Javi @DennisC Clarification of this ongoing problem with UDI's portal connections affecting ELK and ZWave status not being reported unless query is run. This has been documented since the end of October in this thread and is as yet unresolved. UDM Local WiFi connection: -Working as expected; Elk reports names for status ie: armed away vs a number ie 1 AC Direct Connection: No issues, works as expected. UDM REMOTE connection: -When NOT on local wifi, UDM does NOT report Z-wave or Elk status in favorites or EIsy devices, unless the dashboard for the device is opened. See screen shot below of my top favorites page. Some items are ELK and others are z-Wave.. all greyed out unless I open the dashboard of each device, with ELK only reporting numbers, no status. New UI: -same issue with elk and zwave not populating status. See screenshots below. AC Through http://my.isy.io...: -same issue with elk and zwave not populating status. See screenshots below Current System versions: IOX 6.0.3.3 UDX 4.2.0 UDM 1.4.9 Libwebsockets 4.3.3 tpm2 tools: 5.6_2 IOX Matte Bridge: 1.3.24 Mosquito 2.0.18 PGX 3.4.6 Elk Plugin: 3.10.15

However, please note that with the update, Elk will report status in names vs numbers but that remote access to UDM is still not populating these statuses of Elk or Z-wave devices unless you "open dashboard" of each device.

@someguy , Javi was referring to a firmware update. 4.03 has been released and has fixed the elk reporting issue, but not UDM working remotely through their server. You can find out more about the firmware update. Update Packages in AC is the way to update, and most people are having success with it, albeit the usual sign in challenges with Java (clearing the cache, re downloading the matching AC etc) UPDATE: oops. typo.. meant 4.20 above.

took me two times but they look like they finally went away! thanks!

So Saturation is gone now in 1.07... I used it in quite a few resources and scenes.. Is there an equivalent setting now? And if so, how do I relate the two? thanks.

For some reason I am getting 5 extra, duplicate nodes which are all empty. I have deleted them once in PGX, but upon a restart of the NS, they showed up again. They are nodes 10-14. I have a MCA-88 with 8 zones. So I should have 9 nodes: 1 for the controller, and 8 more for each zone. From the Russound controller directly: Any ideas? Info log attached. Thanks. Russound_12-11-2025_105059_AM.zip

@Javi just updated to 6.0.3 adn pgx 3.4.6. Status population issue is still prevalent in UDM..... All z-wave devices and all ELK devices will NOT populate status unless Dashboard is opened. However, ELK is reporting actual status now instead of numbers. Also, favorites page is very slow to load and Devices and Scenes page is miserably slow to load. This UDM problem has been ongoing now since mid / late October Is there an actual date that this is going to be fixed? thanks. UPDATE: Arrived home and connected locally. All works as expected with direct connection but as noted above NOT with a remote connection.

ill do the same and see what happens. thanks!

it was designed for one of the original ones.. mines about 2-3 yrs old and it doesnt work with this plug-in...Not sure how old / new the 205 and 705 are. see this post: https://forum.universal-devices.com/topic/41179-roomba-j7-discovery/#findComment-366094

HI.. am wondering if there is any movement on this ? Just played with it again, and works for a few commands and then stops working. Restart of the plug-in resolves it and then it works again for ~5-10 commands and then stops. I had a problem (again) with my Samsung Smartthings / meross link and meross was able to solve it (this time) so I asked if there was anyone that could help you with their API to finish development. No answer..

I reached out to javi a few days ago on a different thread. response was that a new firmware version should be out soon that will fix these issues.

check out my post here.https://forum.universal-devices.com/topic/45900-time-data-format-changed-causing-progams-to-not-work/ This may or may not apply to your question.

This is a known problem and had been going on for a few weeks now. I have not heard a fix is out yet. @Javi any update? Over ½ my favorites still dont populate and elk and iaqualink are still only reporting numbers vs words. thanks.

@Kentinada Further, once you have it in the AC, you can see its address adn then write it on the switch for future reference.

absolutely.. Unfortunately I am not at home so I cant send a picture, but essentially I rigged up on a piece of wood, two alligator clips that go to a mechanical switch which then goes to a normal plug. I can plug this into any outlet, hook my new Insteon switch up via the alligator clips and then when ready, flip the mechanical switch to energies the new Insteon switch. Then I force a reset / default settings to erase anything in the switch and then add it to my Eisy. I usually just use a temp name if it's a replacement switch. Then in the AC, I do a replace switch on the old one and choose the temp name. Once the Eisy is happy, then I de-energize the new Insteon switch, disconnect and install it. Works great and saves a lot of headaches.

Weird right? But that has been my experience since the beginning. So I now just set up the way I know works, and then just chill about it for 24-48 hours and it usually works as expected.

In the programs you can use Find/Replace function which works well Scenes and resources though are a PIA

Have several programs that set variables based on sunrise / sunset times for a specific location. They stopped working. Solution was to go to each reference line in my programs and hit "update" as the format changed from Minute or Hour to Raw. Previously this was "minute" or "hour" and in the program line, it ended with "minute" or "hour". After hitting update the "minute" and "hour" went away. Programs now work again. Original Program: $I_Naples_Sunrise_Hour = 'TimeData / Sunrise and Sunset Naples' Sunrise Hour Today Hour $I_Naples_Sunrise_hour_plus_3 = 'TimeData / Sunrise and Sunset Naples' Sunrise Hour Today Hour $I_Naples_Sunrise_hour_plus_3 += 3 $I_Naples_Sunrise_hour_plus_3 Init To $I_Naples_Sunrise_hour_plus_3 $I_Naples_Sunrise_minute = 'TimeData / Sunrise and Sunset Naples' Sunrise Minute Today minute $I_Naples_Sunrise_minute Init To $I_Naples_Sunrise_minute $I_Naples_Sunrise_Hour Init To $I_Naples_Sunrise_Hour New Program: See above.. the words Hour and Minute are gone once updated.

I am also having similar problems with UDM and the AC. Working with Javi to solve. Here is a summary of what I am seeing: -Nodes are NOT populating in: UDM via my.iso.io, AC thru my.iso.io, New UI -Nodes ARE populating in: AC thru direct connection, Portal/ Select Tool / Isy Web Access I could not get UDM to connect directly to test. Kept getting a SSL error. Nodes not populating include Zwave, Insteon and certain plugins. ELK plugin is also reporting numbers vs status.

I have had that problem as well.. usually it works itself out with 24-48 hours. Currently all of mine are working well, but I do know when I set one up, it can be fluky for a while.

Same. This started a while back, then fixed itself and is now back. I get status of 1's and 0's in UDM and in Pushover notifications.

My disconnects seem to be related to number of commands. try to use the AC and adjust your light 10-20 times and see if you disconnect

let me know via DM if you want me to send you a switch or two to play with.

I have continued to play with it. Seems more "global" issue of the PI vs any particular device, but if I find an anomaly I will denote the type of device. So far: 1) set level in UDM doesnt stay at the level set, reverts to 0 and then stops working. Set level in AC works fine. 2) Controlled lights via the Meross app and the AC and watched for the; light response, AC response and Meross response. I did not involve the physical switch just yet. For a period of time, all was good; app, AC and light all stayed in sync. Then suddenly everything stopped working again. So I think overall it's mostly working. As for the light turning off and then back on, it DOES NOT do this when adjusted via the Meross app or smart things app, which leads me to believe it's something in the PI code. Cheers!