sjenkins

I don’t think there is any reason we can’t get there. I have had a fully booked week so since receiving my G6 entry I haven’t tackled the issue yet. My thought is we will have a doorbell device with the appropriate nodes we can trigger or status off. Everything the api offers will be passed through to the node.

I have the same situation with Eisy on my IoT Vlan. Just took a look at my zone firewall settings. Without seeing yours , I really just have that vlan able to get to external and gateway. I have a UDM pro max gateway. Nice, thanks for the update. Give yourself a solve for that one !

Yes, agree we need that one. I believe its on their list.

I hear your frustration, I have been on this journey for the last few months. It truly is in the nineties here, we can debate where. Functionally the 98% is accurate, the polish makes up the other percentage. I have deleted admin from my launch bar and haven’t used it for weeks. I use easy-ui daily. As said above you can sort by any column, the number box does prefer the pulldown but if you click in the box and type it does work. Network stuff does work but needs some polishing. Have not experienced the legal character thing. There are lots of design decisions in this thing which are like new clothes replacing favourite old ones. You did the right thing by trying out what you use and listing them here. I would personally have dropped the dramatic title but understand the frustration. I think as Michel and Javi have on the roadmap we are going to take to the end of year for near replacement & then first quarter to smooth it all out. The nice thing is they are also giving us new features in parallel due to the new platform. Glass half full here.

Agree try the refresh, then the hard refresh, then wipe browser memory for that page. Sometimes a logout and login, close and open browser, finally an eisy restart. Have had final success at each step in certain situations of this in the last few months of dynamic profiles learning as I implement it with my users.

Got production caught up to dynamic JSON profiles as well as fixing a Ratgo depreciated label issue. Let me know of any feedback. I have seen in other plugins (Tahoma) that with the jump to the JSON profile migrated plugins from the old PG3 to the new Eisy-ui needed an Eisy reboot to remove a profile error. When installed straight from Eisy-ui it seemed to be fine. YMMV. 3.2.3 \ DONE VirtualGarage Ratgdo: ESPHome REST URLs use entity display names (e.g. /light/Light) instead of deprecated object_id paths; SSE state events accept new id format ahead of ESPHome 2026.7 3.2.2 \ DONE dynamic JSON profiles (Phase 1): updateJsonProfile instead of static profile/ zip for eisy-ui sync ; requires IoX 6.0.6+, PG3x 3.4.5+, udi_interface 3.4.5+; install.sh renames profile/ to profile.static on EISY; profile/ XML remains source for data/base_profile.json; bump profile_version in server.json when JSON base changes 3.2.1 \ DONE fix config overwrite: stop re-injecting example devfile and sample devices on every parameter loal DONE remove example customParams from server.json so Polyglot updates do not reset user configuration DONE clear "Waiting on valid configuration" notice when discovery fails

Dynamic profiles are new and the way UD is suggesting as the way forward. They help with making sure Eisy-ui is always up to date but they add complexity to the programs. So this is my second run at them. Working well at home but need some feedback. If you get an error, try an Eisy reboot, if still an issue then send me logs please. ## 0.0.29 - Fix eisy-ui dynamic profile on migrate: add empty links.ctl / links.rsp on every nodedef and linkdefs: [] in data/base_profile.json so eisy-ui updateprofile validation passes (fixes “Profiles loaded but nodedefs missing” after PG3→eisy-ui migration); bump profile_version to 2

Thanks @Javi for the explanation, understand you need to prioritise development just wanted it on the observed list To @Techman ’s point, I am on osx with Safari, I’ll try with a couple other browsers and see if there are differences and bring back. Maybe it’s a browser quirk.

I am on Staging 1.3.11_1 but this has been there for a few versions. JUST in the Program section (not Nodes, Integers, State, etc) about every 3-5 sections the screen has a blue line flash under the program heading. If you have activated search, it will clear the search. Both visually irritating, but mades search a race for time or unusable. hope this helps.

@MReeves hi Mark, Do you have a gen2 and gen3 gateway? I am assuming that is how the hybrid on the app is working. If you do run two instances of the plugin, one pointing to the gen2 gateway and the other to the gen3 gateway. The app as it is decides which one to be based on the gateway it is talking to. If there is something about the hybrid I am missing let me know.

so this is back office but what it does for eisy-ui is make updates to the node list happen immediately, instead of getting stuck when you add/remove nodes or install a new version of the plugin in the same slot. It works pretty slick and is the modern way to handle profiles as we move away from the admin to eisy-ui. My only worry is you can see below you have to be decently up to date on your controller, which is not the case for everyone out there. Interested in feedback here. You can install this either from the old non-production store or it shows up as a beta trial (1-year trial) if you install from the new eisy-ui plugins(beta). 3.2.2 \ DONE dynamic JSON profiles (Phase 1): updateJsonProfile instead of static profile/ zip for eisy-ui sync; requires IoX 6.0.6+, PG3x 3.4.5+, udi_interface 3.4.5+; install.sh renames profile/ to profile.static/ on EISY; profile/ XML remains source for data/base_profile.json; bump profile_version in server.json when JSON base changes

I've been running this for a few days and seems ok. This is back office except it should mean that eisy-ui picks up on profile changes immediately. My plan is to run this across all my plugins, its the current modern way to do profiles. The OGP bit is a bug fix where some users were seeing extra nodes named OGP. Let me know how it goes. ## 0.0.28 - Dynamic JSON profiles: push profile via updateJsonProfile() instead of static profile/ zip — improves eisy-ui sync; requires IoX 6.0.6+, PG3x 3.4.5+, udi_interface 3.4.5+; install.sh renames profile/ to profile.static/ on the EISY so PG3 does not race static upload; profile/ XML remains in the repo as source for data/base_profile.json; bump profile_version in server.json when the JSON base changes - Per-device nodedef on Discover: new shade nodes pick shadertsid, shadenotiltid, shadeonlyprimid, or shadeid from TaHoma capabilities — existing nodes are unchanged until the user runs Discover and a new node is created (removed nodes rediscovered, or manual delete + Discover) - OGP skip hardened: skip all ogp:// devices and ProtocolGateway uiClass (not only ogp:Bridge controllableName) — fixes duplicate OGP nodes when the gateway returns partial records or multiple OGP entries; run Discover to remove stale OGP nodes

You may want to open a ticket with UD

Minor cleanup and a notice upon connection success. ## 1.5.5 - Temporary Polyglot success notice after connect and discovery (clears after 30 s), matching Ta$

sorry for the delay, painting day today. @Techman , I saw your DM as well , what was the other server you tried? and, of course, have you tried a reboot? I just tested and am able to install from both stores, and am able to install on top of beta -> production -> beta looks like a local issue to you.