Skip to content
View in the app

A better way to browse. Learn more.

Universal Devices Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Hue 1.1.1: status fixes, stream recovery, timeouts

Featured Replies

A Hue node server fork for PG3x/eISY, built on xKing's original, is up to 1.1.1. This version fixes missing status, stalled event streams and bridge requests that could hang forever. 💡

Also implemented: light power, brightness, fades, color/temperature where supported, group control, room/zone scene recall, motion/light-level/temperature/button nodes, and multiple bridges. These are source capabilities, not all newly tested features.

Source: github.com/superflytnt/udi-hue-pg3
Latest release: v1.1.1

What this version fixes

  • Query answers again: it re-reports cached driver values for the affected node types instead of doing nothing.

  • A one-hour read timeout bounds silent or stalled event streams. If the stream thread dies, the next poll restarts it and refreshes device states to recover what was missed.

  • Connection and read timeouts on bridge requests, so no request can wait indefinitely.

  • Optional heartbeat monitoring: set the heartbeat_url custom parameter to any heartbeat/cron-monitor URL to catch missed plugin polls even while PG3 looks online (pings on poll callbacks, at most once per 60 seconds).

Also included: diagnostic logging for private groups, entertainment configurations and older groups. Review logs before sharing, since they can contain bridge resource names. The intermittent eISY HTTP 404 remains open.

Tested: stream timeout and restart observed, and on/off control through eISY on two lights with live bridge feedback.

If your Hue status has been going stale, give it a spin and post your results here.

Edited by kaplansa

  • 2 weeks later...

I have a more complicated Hue implementation that I've used Network Resources to control, but the number of NRs is quite large and harder to manage in the new eisy-ui interface (but overall I like eisy-ui :- ). I tried the production 'Hue' Plugin, but it doesn't support (or seem to support) grouped_lights or scenes (plus exhibits some odd behavior from the lights at times).

This new 1.1.1 version sounds like it may support grouped lights and Hue scene recall. I'm willing to test it out, but am not familiar with setting up a local node server (plugin), I've only installed existing plugins from the Store.

I looked through the linked PG3 instructions but wondered if I should be installing directly in eisy-ui (vs PG3 and migrating). Perhaps @Javi could recommend an approach? New instructions for that? Any other tips on getting started?

UPDATE: Digging a bit deeper into the 'forking' process, I think this might be a bit complicated for me at this point, but I would be willing to test a Store non-production plugin.

Edited by CNelson03

On 11/16/2026 at 9:46 AM, CNelson03 said:

I have a more complicated Hue implementation that I've used Network Resources to control, but the number of NRs is quite large and harder to manage in the new eisy-ui interface (but overall I like eisy-ui :- ). I tried the production 'Hue' Plugin, but it doesn't support (or seem to support) grouped_lights or scenes (plus exhibits some odd behavior from the lights at times).

This new 1.1.1 version sounds like it may support grouped lights and Hue scene recall. I'm willing to test it out, but am not familiar with setting up a local node server (plugin), I've only installed existing plugins from the Store.

I looked through the linked PG3 instructions but wondered if I should be installing directly in eisy-ui (vs PG3 and migrating). Perhaps @Javi could recommend an approach? New instructions for that? Any other tips on getting started?

UPDATE: Digging a bit deeper into the 'forking' process, I think this might be a bit complicated for me at this point, but I would be willing to test a Store non-production plugin.



Likely a few weeks out but this should solve the issue: https://youtu.be/z7QSEYBzEHk?t=1162

20 hours ago, Javi said:

Likely a few weeks out but this should solve the issue: https://youtu.be/z7QSEYBzEHk?t=1162

Thanks @Javi , I'll check out the grouping of lights when it is available. However, I'm not sure that it will address scene recall. Hue Gradient Lightstrips can display shifting color patterns (e.g., fade from one color to the next across the length of the strip). These light effects can be grouped across multiple lights and saved in the Hue Bridge. From there, a Hue API v2 'Recall' command can easily play the 'scene'.

I currently have a Network Resource execute the scene Recall command and that works fine except you end up with quite a few Network Resources (using UD variables does help with things like setting different brightness levels).

It sounds like the new Hue 1.1.1 plugin will also be able to execute these recalls providing an alternative method. But unless there are plans to phase out Network Resources (hopefully not), either method should work.

1 hour ago, CNelson03 said:

Thanks @Javi , I'll check out the grouping of lights when it is available. However, I'm not sure that it will address scene recall. Hue Gradient Lightstrips can display shifting color patterns (e.g., fade from one color to the next across the length of the strip). These light effects can be grouped across multiple lights and saved in the Hue Bridge. From there, a Hue API v2 'Recall' command can easily play the 'scene'.

I currently have a Network Resource execute the scene Recall command and that works fine except you end up with quite a few Network Resources (using UD variables does help with things like setting different brightness levels).

It sounds like the new Hue 1.1.1 plugin will also be able to execute these recalls providing an alternative method. But unless there are plans to phase out Network Resources (hopefully not), either method should work.

Network Resources are not going away but should be consider legacy, while it works there are too many edge cases. So this is not a solution it is a work around.

Depending on the impelentation, the process is different, if integrating through a plugin the plugin needs to implement. If implementing through Native Zigbee, it should have these commands (assuming they are exposed). If not exposed to zigbee then plugin is the only method.

There is a fix for Scenes and Hue Bulb NodeDefs in review which should fix Native Scenes for Hue color. This is firmware so lilkey next IoX bump.

2 hours ago, Javi said:

Network Resources are not going away but should be consider legacy, while it works there are too many edge cases. So this is not a solution it is a work around.

So far my attempts at using the 'Hue' plugin have caused more 'edge cases' than the Network Resources (quirky bugs especially when trying to control a 'group' of lights with individual light commands) and using a 'Wait' command slows things down too much due to the 1 second minimum wait time.

Hopefully the new light grouping capability (in the Hue plugin or UD) will resolve. I'll plan on testing both when available.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.