Javi

While I have no timelines my guess is when a new eisy-ui app is released most users will migrate as it will be familiar/similar to the eisy-ui desktop. At some point it would move into maintenance only, just meaning no new features, bug fixes and required app store updates/certs/etc updates. Some of the newer implantations in eisy-ui, like any Protocol Page (Insteon/Zwave/etc), already have both desktop and mobile implementations and size correctly on any screen size, some of the older screens need to be reworked for this requirement, including favorites. The issue with UDM is it supports much of the legacy hardware/firmware and most data is hosted from within the app (due to limited memory on ISY994), So it is very difficult to implement new features without breaking for legacy users. Due to the same memory limitations in ISY994, UDM required a separate app backup and synchronization both huge pain points. All of this is solved in eisy-ui and any mobile wrapper.

UD Mobile needs to be updated for the new upgrade lookups it is still using the legacy method of checking the online store which is not longer updated due to the new eisy-ui implementation. Its, on our todo list but we have a higher priority on eisy-ui, and a mobile version of the same due to end of Admin Console. We don't want mac users to be left without a way to access all AC features if they upgrade to a MacOS version which no longer supports Rosetta (need to run Admin Console). So we are likely a 6+ weeks out for any UD Mobile updates.

Being as it works, the issue is just feedback. Due to the future migration PG3 to eisy-ui Plugins, I'm not sure if we would investigate the issue on PG3 (as it could be one of the limitations we hope to solve with eisy-ui plugins). If the Elk plugin works on Plugins (Beta) we can investigate the response issue.

This was in reference to out-of-policy Polisy firmware upgrade path to get Policy users to the current firmware. Most of our newsletters contain a discount code, the last is now expired. We will likely be publishing a news letter soon.

While I'm usually a fan of "if it's not broken don't fix it", I think you will likely run into issues at some point next year. Event if you maintain an old computer and don't update anything there are things that could break behind the scenes like certificates for software. Could you get around that, maybe, will we be able to help at that point, not likely. We currently offer an 'ex gratia' upgrade path for Polisy which may not exist in the future. Also at some point eisy's software will not longer be compatible with Polisy, there may be no mechanism to upgrade at that point. https://forum.universal-devices.com/topic/47042-eisy-ui-is-getting-there-heres-where-we-stand/

The issue is there are 3 commands in less than a 1/3rd of second?

It sounds like ISY (likely SD Card) is dying or there is a power supply issue. Networking is working but failing to supply endpoints. ipAddress/desc is unauthenticated and should work if you know the ipAddress, this is where finder gets the version. If this is failing to load then ISY is having issues.

Does this only happen when multiple commands are issued in a short period, less than 1 second apart? This seems too fast for a human, is there are program that triggers another command to the same nodeserver at the same time. 2026-10-06 08:26:58.082 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_28/cmd/DON .... 2026-10-06 08:26:58.153 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON ... 2026-10-06 08:26:58.234 [pg3] info: API call: GET /ns/00:21:b9:02:63:5d_14/nodes/n014_output_17/cmd/DON

The last things to try are restore device and/or a brief power gap (pull tab out for ~10 seconds) does not correct the issue, then it could be failing. Very odd that it works on reset.

Mesh and Long Range can coexist, mesh is required for native links. From my understanding the only difference between 700 LR and 800 LR is distance.

Current Beta, Option will be shown when adding a new device via smart start QR Code.

I have been writing the same multiple times a day for 15+ years. Are you sure it is not a communication issue at the time of write? Does it work if done manually?

I've added links to Q&A about Polisy to https://forum.universal-devices.com/topic/47042-eisy-ui-is-getting-there-heres-where-we-stand/

It is likely eisy-ui fails to propagate the error to the user. Will likely show the same error response in the browser's developer tools. Unfortunately I don't have a good test case on when or why this happens, so will need help identifying the cause. If anyone checks the PG3 or Plugins log it may show an error which we can isolate.

If Mobilinc can connect isy is working. I think you need to be more specific about "can't log in to the admin console". Can't find IP Address? Credentials not accepted? Something else?