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

Once I get PG3 access I'll give 0.0.28 a try