Hue Lights — Indigo Plugin

======================================== 2022.32.112 @ 2026-07-09 The "shortBridgeInfo" print (bridge/lights/groups/... summary header + per-bridge lines) is now built into one string (leading \n, each line \n-separated) and written with a single log call, instead of one log entry per line. The rare not-setup/not-paired lines are included in the same block (now level 20).

The full bridge re-read now runs ONLY on a real outage (gap > kEventReplayWindowSecs). Previously it also fired for short gaps where 0 events were replayed (nothing had happened) — unnecessary. Now: gap > window -> level 20 + re-read; replay recovered events (short gap) -> level 10, no re-read; short gap with no events -> level 10, no re-read. So no re-read for the routine hourly recycle.

Shortened the reconnect-table header line: "eventstream reconnects (last N of 100) — M replayed, avg gap Xs". Dropped the long column-explanation parenthetical (the column names are self-explanatory).

Level 20 now fires only when events may actually have been MISSED (not merely recovered). Reasoning: recovered events are counted reliably and are NOT missed; a true miss only happens if the reconnect gap outlasts the bridge's Last-Event-ID replay buffer (then the oldest events age out). So: gap <= the assumed replay window (kEventReplayWindowSecs, default 300s) -> fully recoverable -> level 10; gap > the window -> possible data loss -> level 20 ("gap of Ns EXCEEDED the ~Ws replay window ... MAY HAVE BEEN MISSED"). Honest limitation: from the stream alone a quiet gap and a buffer-overflow gap are indistinguishable, so this is a gap-duration proxy, not a perfect miss detector. For the ~40s hourly recycles it stays at level 10. Also: the re-read is now forced whenever there was no full replay OR the gap exceeded the window.

The "real gap ... recovered N events" line is now level 10 too. The hourly bridge-recycle reconnect is routine and self-healing, so it produces no level-20 output at all now (details remain in the print-stats reconnect table). Still level 20: the first-connect "Successful Connected" (startup) and the generic "Error: ... Reconnecting" for unexpected exceptions.

Reconnect table "last event" column now shows the full YYYY-MM-DD HH:MM:SS timestamp (column widened).

Reconnect table: replaced the raw epoch ev-ids (useless to read) with human-readable columns — "last event" = the bridge time of the last ev-id before the gap (epoch converted to local, dd HH:MM:SS), and "next event" = "+Ns" seconds to the first ev-id after. Dropped the separate ev-gap column (now the "next event" delta).

Reconnect table: dropped the misleading "spurious?" label. recovered==0 only means "no events occurred during the gap", NOT that the restart was unneeded — the connection gap was still real (confirmed by the ev-id epochs jumping tens of seconds). Added an "ev-gap" column = the time hole between the last ev-id before and the first ev-id after (seconds), which shows the real gap even when 0 events were recovered. Summary line now reports total events replayed + average gap, no spurious count.

Quieter reconnect logging. Routine reconnect notices are now level 10 (debug): "Bridge connection closed/unreachable / read timeout ... Reconnecting", "Successful Connected" (on reconnects only — still level 20 on the first connect), "reconnect after Ns gap ... checking replay", and the "no events missed / likely unneeded restart" resolution. Only a REAL gap (events actually recovered) logs at level 20, now as one self-contained line including the gap duration: "bridge X: real gap of Ns — last ev-id ... -> first ev-id ...; N events replayed by bridge". So a spurious reconnect is silent at normal level; a genuine data-gap shows exactly one line.

Single source of truth for config defaults: all plugin-config parameter reads now use kDefaultPluginPrefs["key"] as their fallback instead of hardcoded literals — timeScaleFactor, sendDeviceUpdatesTo, timeScaleFactorAPIV2, showLoginTest (startup + getDebugLevels), the debug* flags, autoCreatedNewDevices, folderNameForNewDevices, and logAnyChanges (now a safe .get). The event thresholds already used kDefaultPluginPrefs + minMaxEventRecovery ranges. (Consistent with removing the default= attributes from PluginConfig.xml — defaults now live only in kDefaultPluginPrefs.) Action / device dialog fields are unchanged; those aren't plugin-config parameters.

Faster reconnect. The eventstream reconnect used a fixed 5-10s sleep, adding ~10s to every gap. Now a drop of a working connection (the common case: the bridge gracefully recycles/close-notifies the SSE connection) reconnects IMMEDIATELY (0s); the delay only escalates (2 -> 5 -> 10s) if the reconnect itself keeps failing (bridge genuinely down). reconnectFailures resets as soon as data flows again. This covers the TLS close-notify case without parsing the alert (requests abstracts it away). Also fixed two bugs introduced in the parameter-driven readEventTimerPrefs edit: a missing ')' on the NumberOfSecondsEventRestart read, and the fallback clamp using 'restart' instead of 'woMsg'. Note: the remaining gap (~25s in the captured case) is the bridge holding the connection open/idle before it closes it — that part is bridge-side and not reducible from here.

Track the last ev-id before a reconnect and the first ev-id received after, to tell a real gap from a spurious restart. Each reconnect log line and the print-stats reconnect table now show both ids, and the table adds a summary ("N real gap, M with NO events missed"). A reconnect that recovers 0 events (recovered==0) means nothing was actually missed — flagged "0 no-gap"; a run of these at a low NumberOfSecondsEventRestart indicates the threshold is too aggressive (spurious restarts, no data lost).

Fix: the v.99 "apply NumberOfSecondsEventRestart immediately" didn't work — validatePrefsConfigUi applies the new value before closedPrefsConfigUi captured the old one, so the change was never detected (it only took effect on a full plugin reload). Now each listener session is stamped with the threshold it was built with ('restartSecs'), and checkIfListenerIsRunning (main loop, every ~10s) restarts the listener when that differs from the current config value. Works regardless of the dialog callback order.

Changing the (main) NumberOfSecondsEventRestart threshold now takes effect immediately. The keepalive is baked into the socket at session creation, so a changed value previously needed a plugin reload (in-thread reconnects reuse the same session). closedPrefsConfigUi now detects a change to that value and restarts the V2 event listeners, so checkIfListenerIsRunning respawns them with a fresh session (new keepalive) within ~10s. The (fallback) NumberOfSecondsEventWoMessage watchdog already applied live.

Cosmetic: getDebugLevels() collapsed its two duplicate branches (loop + showLoginTest read) into one path — "if useMe is None or empty: useMe = self.pluginPrefs", then a single loop. No behaviour change.

Refactor (continued): the general prefs that were applied in startup + validatePrefsConfigUi + closedPrefsConfigUi (timeScaleFactor, sendDeviceUpdatesTo, searchForStringinFindHueBridge, and the fixed timeScaleFactorAPIV2) are now read/applied by one method applyGeneralPrefs(prefs), called from all three. Removes the duplicated apply blocks and the dead if False: timeScaleFactorAPIV2 reads (the value was already forced to 119). All three sites now apply the same set consistently. No behaviour change for real values.

Refactor: the read+range-clamp of the two eventstream restart thresholds was duplicated in three places (startup, validatePrefsConfigUi, closedPrefsConfigUi). Consolidated into one method readEventTimerPrefs(prefs) that all three call. No behaviour change.

Split the eventstream restart control into two separate expert-section config dropdowns: - (main) NumberOfSecondsEventRestart: 10..130s, default 90 — drives the TCP keepalive (fast restart, fires "Bridge unreachable. Reconnecting"). This is the primary threshold. - (fallback) NumberOfSecondsEventWoMessage: 60..200s, default 180 — drives the no-message watchdog, the backstop for the rare case where TCP stays alive but the bridge stops sending events. Both defaults are in kDefaultPluginPrefs; both are range-clamped on load (legacy values → default). The stream read timeout now sits above whichever of the two is larger (+60s).

1. Full bridge re-read after a gap is now conditional: if the bridge replays the missed events (Last-Event-ID), processing them already makes device states current, so the re-read is skipped. The re-read is only forced when the bridge sends no backlog. Removes the redundant per-hour re-read on bridges that support replay.

2. Restart threshold is now a config dropdown (expert section, bottom of plugin config): "Restart api-V2 event listener after no events for:" with fixed values 10..130s, default 90. Reuses the existing NumberOfSecondsEventWoMessage pref and now drives BOTH the TCP keepalive (idle = threshold-20, +2x10s probes) and the no-message watchdog, so the whole range is effective. Legacy/out-of-range saved values (e.g. 180/240) are clamped to the new default 90 on load.

3. Restart threshold raised to ~90s: eventstream TCP keepalive is now 60s idle + 3x10s probes (was 30s + 3x10s = ~60s). A >=90s silence has <0.01% chance of being normal (observed max gap ~40s), so this never false-triggers and avoids reconnecting into a still-stalled bridge.

4. Reconnect table in print-stats clarified: the count column is now labelled "recovered" (= gap events the bridge replayed), right-aligned; values are a number or "pending" (events not yet resumed). Columns realigned. Note: the separate watchdog backstop (config: NumberOfSecondsEventWoMessage, ~180s) is unchanged; lower it to ~90s in plugin config if you also want the "no message in N secs" path to fire at 90s.

Harden the skipped-event count against a bridge event-id going backwards (e.g. a bridge reboot whose clock resets before NTP re-sync). The backfill test now requires resumeEpoch <= evTs < reconnect-time (previously only the upper bound), so a backward id jump reads as "0 / no replay" instead of counting every live event as skipped. Gap duration, forced re-read, and Last-Event-ID resume were already safe.

Print-stats now includes a rolling eventstream-reconnect history. Each reconnect records timestamp, bridge, gap duration (s), and events skipped/recovered; the list is capped to the last 100 (oldest dropped). Shown at the bottom of the "bytes send /received to/from bridge" (and ...WithReset) menu output.

Report skipped-event count on reconnect. The SSE event id is :, so after a gap-reconnect the plugin counts how many replayed events carry an id-epoch earlier than the reconnect moment (= events that were skipped by the live connection and are now being backfilled). Logs either "recovered N events that were skipped during the gap (bridge replayed them)" or, if the bridge sends no backlog, "bridge did not replay any skipped events; states were made current by the forced re-read". The reconnect line now also prints the gap duration in seconds.

Event-stream gap recovery — after an SSE stall/reconnect, missed events no longer leave device states stale: 1. Last-Event-ID resume: the plugin now remembers the last SSE event id per bridge (persists across listener restarts) and sends it as the Last-Event-ID header on reconnect, so a compliant bridge replays events buffered during the gap. (Buffer depth is bridge-dependent/short; confirm from the log by watching for a burst of events right after "reconnect after gap".) 2. Forced full re-read on reconnect: whenever the listener reconnects with a stored event id (i.e. a gap occurred, not the first-ever connect), it zeroes the getHueConfig / 'all' / 'v2' / checkMissing timers so the next main-loop pass re-reads the whole bridge and brings all device states current — the same reconcile the bridge already does on add/delete events. This guarantees persistent state (on/off, brightness, colour, sensor values) is correct after a gap even if the Last-Event-ID replay buffer has rolled over. Transient events (a button press / motion pulse that already cleared during the gap) are only recoverable via #1, not the re-read. Note: the underlying hourly stalls are a bridge-side issue (bridge stalls its own eventstream ~hourly, stays ping-reachable throughout) — see VERSION_HISTORY .87/.88; this change limits the data impact of each stall.

1. TCP keepalive enabled on the event-stream socket (probe after 30s idle, then every 10s, 3 probes). The SSE connection is inbound-only after the request; NAT tables / power-save / bridge firmware silently drop such connections (~hourly stalls on bridge 1). Keepalive probes maintain the path (usually preventing the stall) and let the OS detect a dead peer in ~1 minute, so recovery happens as a normal reconnect instead of waiting for the watchdog.

2. "listener thread did not stop cleanly" warning downgraded to an informational message — with the v.87 stop mechanism an old reader draining in the background is expected and harmless.

3. Event-listener restart after a stalled stream now takes seconds instead of ~8 minutes:

   • stop_listener closed the streaming response inline from the watchdog thread; closing an SSL socket that the listener thread is blocked reading waits on the SSL lock until the read times out (NumberOfSecondsEventTimeOut = 660s), stalling the whole plugin loop. The close now runs in a small daemon thread.
   • The stream read timeout now tracks the watchdog window (NumberOfSecondsEventWoMessage + 60s, capped at NumberOfSecondsEventTimeOut) so an abandoned reader thread exits soon after being replaced.
   • A replaced (zombie) reader can no longer clear the new listener's response reference or lastMessage, and no longer queues a stop_listener that would tear down the replacement listener.

Code audit: ~40 bug fixes across plugin.py (no new features). Highlights: 1. Save Preset no longer rejects every light device (validation compared the Python builtin "type" against the compatibility list) 2. Recall scene without a group works again (int 0 vs string "0" groupId mismatch); doScene now tolerates int groupIds 3. activateScene picks the API version of the action's own bridge, not the last bridge selected in a config dialog; removed an older dead duplicate of activateScene 4. V2 set-color-temperature now sends the requested brightness and turns the light off at brightness 0 (previously always on:true, brightness discarded) 5. RGB scaling is no longer corrupted after saving plugin prefs (stale "rgbmax" block set rgbIndigoMax to 1.0) 6. White-level slider: hue is converted from degrees to the bridge 0-65535 scale (lights snapped to red before); hueGroup white slider no longer forces saturation to 0 7. Attribute Controller colorGreen toggle-on no longer swaps green into the red channel 8. V1 "off" commands use the noOffRampRate prop instead of noOnRampRate; V2 "off" reads the correctly spelled brightnessLevel state (ramp rate was always forced to 0) 9. Dimmer-switch/button onOffState is no longer inverted (triggers fired backwards) 10. hueOnOffDevice V1 "on": Indigo state updates again (undefined vars aborted the handler after the bridge command) 11. Hue state for bulbs/light strips/LivingColors stored in degrees again (normalizeHue return value was discarded) 12. V2 color/ct-only events no longer reset brightness to 100% (missing "dimming" now keeps the last known level) 13. zgp (Tap / Friends-of-Hue) connectivity events no longer mark connected devices as disconnected (quoting typo) 14. Motion-area device creation fixed (moti905onInfo typo, indigo.devices["name"] literal, getConvenienceAreaMotionInfo returning a bare None); grouped-motion states no longer set to literal key names; contact-sensor tamper state no longer clobbered to None 15. Event stream: health updates no longer leak to the wrong device; per-bridge listener threads no longer share one deviceUpdate dict; listener shutdown race guarded 16. One offline V2 bridge no longer aborts the data refresh for all bridges; child-service exclusion in fillAllDataV2 fixed (stale loop variable) 17. Move-device-to-new-bridge: states are actually transferred now, and the moved device is no longer auto-recreated on the old bridge (ignore list used wrong key and wrong id) 18. Hold-to-brighten/dim worker thread logs errors and keeps running instead of dying silently 19. Expired auto-pairing window stops retrying instead of re-pairing on every poll cycle 20. Many smaller fixes: scene/preset dialog crashes (KeyErrors, Py2 leftover .items()[0], "{}}" format string), color-picker hex builder, sensor status requests skipped when debug logging was on, temperature offset now scaled correctly for Fahrenheit, sensitivityMax gating, duplicate-sensor validation no longer crashes on stale devices, various wrong/misleading log messages

did not recognize "xxx outdoor XXX " fixed in counting number of device types attached.

1. add check if connection to hue bridge is lost through eg reboot. The event listener in api v2 (pro bridge) does not realize if the connection is broken. Now added a timeout you can set to re-establish the connection if no events where send from the bridge to the plugin.

lots of little format issues, misspelled variables, but used only in rare circumstances used "pycharm" and "claude" to do syntax error checking pycharm is much better though.

fixed bug 1048, in autocreateNewDevicesV1 name = "Hue_{}{}{}_{}".format(self.pluginPrefs.get(prefix,kDefaultPluginPrefs[prefix]), hubNumber, theID, nameOnBridge)

2022.29.78 @ 2026-03-13 1. fixed bug for hue contact sensor update 2. fixed bug not creating api v2 devices for groups - there was a debug statement not commented

======================================== 2022.29.77 @ 2026-03-12 1. added option to use default for brightness and ramp rate for recall action 2. fixed several rgb / dimmer functions 3. added enable disable for devices for pro bridge 4. added scenes support for pro bridge 5. added config option to set prefixes for devices names types switch/sensor/light/group eg Hue_light_br#_id#_nameOnBridge (replace light with lampa) 6. added different prefix for switches and sensors (was all sensor) 7. combined many sql updates for a device into a single call 8. reduced CPU usage, with > 80 lights, 15+ sensors 40+ switches on pro bridge: 0.1% .. 2% cpu on MAC-M1 (state updates depending on sensor, switch, light event frequency, no update: 0.1% CPU) on my previous setup with 4 old bridges it was 5%-15% and response time to sensor events was 2-3 secs, now < 0.5 secs. 9. added option in config to enabled / disable a bridge. this will only disable communication with the bridge. Useful if you have disconnected a bridge and would like to stop error messages 10. added a device for each bridge. it will contain bridge values in the device states (30+) This device is not editable, the states are just for info. 11. The pro bridge does not supply rgb (xy) color update events for groups (zones, rooms), only brightness level. the issue is likely that a mix of different lamp types makes it difficult to actually calculate the proper color values (rgb + dimm only + color temp lamp types ) work around: Added a http api v1 "get" for all data for the hue group, WHEN a brightness level change event is received. That should cover most situations. 12. fixed indigo device icon. if a device is turned off, but brightness level is not 0 the icon stayed "ON". Now it reflecting state is off/on

======================================== 2022.28.76 @ 2026-02-25 1. added option to use default for brightness and ramp rate for recall action

======================================== 2022.28.75 @ 2026-02-24 1. added support for pro bridge for scene recall (active a scene on the bridge) 2. several smaller performance improvements 3. cleaned up code. 4. reconfigured RGB to XY color schema for pro bridges.

bug fixes for new device triggers, move devices to new bridge, security contact device

2022.27.74 @ 2026-02-15 1. added stats for # of packages send / received 2. cleanup frequency for different http requests. It is now per type and per bridge pro bridge as compared to old bridge type has about 1/5 the packages (incl events) and ~ 1/3 # of bytes. with 2 bridges, one old and one pro and ~ 80 physical devices the average load on a MAC M1 is -0.5-6% averaging ~ 2.5% and response time to devices changes on the pro bridge is < 0.5 seconds 3. added support for security contact. only works with pro bridge looks like phillips is not adding api v1 support for newer models api v1 does not send any info for that device on old bridge as well as new bridge 4. removed unnecessary items from device edit. it is now very simple. Disabled "create new device" for std Hue devices, beside "hue attribute controller" all std devices are automatically created by the plugin. 5. added a print option to show the network traffic used (menu "print hue config .."" at bottom)

1. added menu to ignore/ disable hue device creation in indigo. Normally the plugin will auto create a missing device in indigo. This option will prevent this for selected hue devices (light, sensor, groups)

1. removed a debug statement
2. reversed a json.loads statement. apparently older python versions a fickle with single quote signes: json.loads("{'a':1}") errors - not in the current indigo version though
3. fixed a bug: deleting a device and auto re-creating it caused an error. - it kept the old info in temporary dicts.

removed some api v2 debug statements

1. fixed bug in print config, # of users and # of scence were flipped
2. added event data will update "enabled", "health" for motion area devices
3. added events for groups. Now rooms cenes get updated dynamically for hue pro bridges
4. reduced indigo dev state updates. In my setup cpu usage down from 3-10% to 0.5-5%

fixed bug introduced in 2022.23.64

1. added assign modelid if not found in defs to similar device eg if RDM005 not defined, try to look in product name to find know device that matches
2. added support for hue motion area events: with the new pro bridge you can use the lamps in the room to detect movements if you have setup a motionarea zone then the plugin will create the corresponding device and will set onOffState to True=on / False=off if motion is detected / expired.
3. added eventNumber to motion devices (lso ond ones), +=1 if state goes from off to on

1. added new smart button version: RDM005 = hueSmartButton
2. clarified selections of hue bridge api and pro versions

1. added new smart button version: RDM005 = hueSmartButton
2. clarified selections of hue bridge api and pro versions

1. added various functions to support migration to pro bridge - added menu to move individual devices or all from old to new bridge - added option to print possible moves of devices to check consistency etc.

1. added option to enter serial number from the bulb (and sensor) into indigo device edit. This info is then available in reports ie print lights. In case you have to re-learn a light to a hue hub you can get that info from here. BUT you need to maintain that info manually. There is no known way to get the serial number from the hub.
2. added >>>> the hub does not answer ping <<<< to log when the network is not working properly

various updates

fixed ACTION for preset

fixed menue to exclude sensors in scenes and presets, or give warning msg

1. fixed add hue bridge manually
2. fixed find hue bridge automatically, the tag used changed from Philips Hue to Hue Bridge. that is due to software changes on the bridge you now can change that string in config.

Added option to REPLACE a (eg broken) hue light in indigo - ie keep the indigo ID (and trigger etc) and link it to the new Hue device

In indigo device edit Lights you now have 3 options: 1. normal edit, no change 2. replace the hue device an indigo device is linked to - add new hue device to hue bridge, then edit the old indigo device and select "replace device, select new Hue device" 3. copy other indigo device (eg already created indigo device for new replaced hue device, but you would like to keep triggers etc in place that use THIS indigo device id) - edit old Indigo device and select option: "replace device, copy other Indigo device to this device" after save delete the indigo device that was copied from.

this should make it much easier to replace a broken light as compared to the previos plugin version: 2022.16.52

2022.16.52 @ 2023-09-27 Added option to REPLACE a ( eg broken) lamp in indigo - ie keep the indigo ID (and trigger etc) and link it to the new Hue device steps: 1. add the new lamp to the hue bridge 2. add the new device to indigo (best is the auto create menue option) 3. disable Comm enabled for both new and old device in indigo (uncheck the check box in the column Comm Enabled) 4. edit the OLD device (w the indigo id you want to keep) 5. check "Replace a device (not the normal option)" in device edit 6. select bridge and confirm 7. select the new Hue lamp in the selection menu. You will see the names of the lamps on the hue bridge not the indigo names 8. save 9. delete the NEW indigo device, otherwise you now have 2 indigo device that point to the same hue device 10. re-enable Comm for the OLD device (click on the check box in the column Comm Enabled)

made the default value of option "auto create new devices": OFF. This has no impact on existing installations, only when you (re) install the hue plugin the option will be set to OFF initially you can set it ON/OFF in config at any time. The tool tip / help in config reads: >> with this option checked the plugin will create a new indigo device as soon as a new light/sensor/group is created on a hue bridge. With the option OFF you can manually create new devices (add indigo device ... Or you can use the menu item 'Add New Devices on Hue Bridge to Indigo' That will add all new devices that are on the hue bridge(s) in indigo<<

The change to OFF has been requested by Jay, as it conflicts with indigo standards.

added state lastBatteryReplaced that states shows the date-time stamp when the battery level went from anything to 100% the first time it runs it checks if the state is empty and when the battery level is 100% hen it takes that date-time. otherwise it stays empty until the battery goes to 100%. that miht take some years depening on the battery life of the switch/ sensor.

fixed brightness level when using attribute devices to change eg hue value

1. added device debug for hue attribute changes
2. added created state for attribute controller device

1. made http connect to bridge serial, ie put in a wait unitl last connect is finished this is to avoid time out when connecting to bridge by sevral threads at the same time. now they will happen after each other. if the wait is too long (3.5 secs) a warning gets printed to the log then you might want to reduce the frequency of ppolling the bridges in config.

======================================== 2022.14.47 @ 2023-07-09

1. added menu option to help facilitate moving a device to a new bridge now besides light also sensors can be moved made the labels and sequence clearer (new vs old devs)

2. reduced the number of potential bridges to 5 from 9. One more that can be used in a house for future options this makes the selection menues shorter This is just cosmetics

added menu option to help facilitate moving a device to a new bridge now besides light also sensors can be moved

added menu option to help facilitate moving a device to a new bridge

fixed some issues in print hue config data, for special cases

1. fixed lights not selectable in track specific light
2. added set dev state of orphans (devices on indigo but not on hue bridge) to "delete" instead of "disconnected" or "online"
3. added option to not show the logging test print at startup, you can set it in plugin config in debug section

fixed groups did not get updated

now NEW Hue lights, sensors, and groups will be automatically created in indigo (once every 3 minutes) That option can be switched off in config.

So from now on: no need to manually ever create a new light/sensor/group. At most 3 minutes after you add a new light bulb etc to your Hue system through your phone that light bulb ... will appear automatically as an indigo device. The name will be like: Hue_type_Bridge#_Id#_name-One-Hue-System eg: Hue_group_0_2_Wintergarten Hue_light_1_11_Library spot 3 Hue_sensor_2_14_Dining wall on off 2

The folder name can be set in config.

• added help when adding new devices manually. if your selection of avalible light si empty, it will print something like: ++++++ Hue Lights !!! no correntsponding light found, please check your selections !!! your selection was: Bridge# 1, indigo devType:"hueLightStrips"="Light Strips" maps to hue-type:"Extended color light" available on the Bridge#:1 are: name:"Guest leo spot 3", GW#:1, id:30, hue-type:"Color temperature light" equivalent to indigoDev-type:"['hueAmbiance']"

  Hue Lights ======================== mapping of devtypes ===================== ------hue dev type------- -----indigo devType------ --------------------indigo dev type Name--------------------- Extended color light hueBulb Color/Ambiance and compatible Extended color light hueLightStrips Light Strips Color light hueLivingColorsBloom Color Lights (Aura, Bloom, StoryLight, LivingColors, etc.) Dimmable light hueLivingWhites LivingWhites (Hue Lux, generic dimmable device, etc.) Color temperature light hueAmbiance Ambiance Lights (color temperature) On/Off hueOnOffDevice On/Off Device (Hue Smart Plug, etc.) ======================= mapping of devtypes END ===================== ++++++ to the logfile.

The device type mappings between indigo and hue bridge are historical, and not simple to remember.

!!! =========================================== !!! I strongly suggest not to add hue devices manually to indigo, but you should use the menu item: "Add New Devices on Hue Bridge to Indigo..."

that will auto add all new devices found on any hue bridge to indigo in the proper form and device type !!! =========================================== !!!

• fixed error: line 858, in validateRGBWhiteOnOffetc
• streamlined hue group edit, made selection clearer

added some more context when connection to hub bridge not is working

• fixed adding hue bridges, fixed a major issue

• added print option to print plugin prefs to logfile, for debugging purposes
• added more logging info when connection to bridge is failing
• fixed, during initialization: if conection to one bridge failed, all subsequent bridges were ignored

• beautifications in logging and menus

• added one more check when adding a new bridge fixing error: plugin.py", line 2686, in selHubNumberGWPair

• fixed continuous logging for some sensors, even when nothing changed.

• fixed continuous logging for some sensors, even when nothing changed.

2022.12.34 @ 2022-07-29

• CHANGED # of state updates (online = false) for devices that are pysically w/o power from once every 5 secs to just once

• FIXED: "line 7336, in parseOneHueSensorData if logChanges: self.indiLOG.log(20, "... was a bad ")" in format statement

• ADDED menu option: "Delete Devices on Bridge..."" this will remove a hue devices from the bridge, not from Indigo

• ADDED menu option: "Start Seach for new Devices on Bridge..." this will start the scan process on the bridge to look for new devices. the bridge will scan for 40 secs for new devices. This will not add devices to indigo, use menu "Add New Hue Devices in Indigo..." it will do about the same as the iphone hue app.

• ADDED support for Hue Rotary Wall Switch (4 Tap Switches w rotary ring) the most usefull dimmer in the Hue portfolio - In my opinion using types = ZLLRelativeRotary and ZLLswitch modelId = RDM002 it will create 2 indigo devices: hueRotaryWallSwitches (ZLLswitch) for the 4 buttons hueRotaryWallRing (ZLLRelativeRotary) for the ring to dimm lights on the hue bridge it is also 2 virtual devices

• ADDED action & menu to dis(en)-able sensor devices (temp, motion, switches) this can be useful when you want to disable certain sensors at night or when you are out or at home this is done by setting element "config":{"on":true/false} on the bridge for the selected device you can see which sensors are on/off with report in menu/print hue config../sensors

• ADDED menu option to rename devices on bridge you can change individual devices with free text or all and change the name on the bridge to the indigo device name !! max number of characters is 32 for names on bridge !! there is an option to drop the "Hue_bridge_id_"nameOnBridge prefix of indigo names on the bridge for devices generated using plugin/menu/Add new devices

• ADDED option "Where to log device value changes" received from hue bridge either (1) in regular indigo log and plugin.log or (2) ONLY in plugin.log file in indigo log direcotry with this option you can declutter your normal indigo logfile from regular messsages reminder: ALL log messages are ALWAYS in the plugin.log file

• ADDED option to print detailed tracking info for ONE specific Sensor or light to logfile this is useful to track the detailed behavior and logic in the plugin for ONE specific device when eg buttons are pressed

• There are now various options to log device changes in plugin config
  • on for all devices
  • off for all
  • set in each device individually
  • log in indigo log and plugin.log or only in plugin.log file
  • set the default for each new device created

• CHANGED state lastupdated is now local time, not UTC eg 2022-07-12 12:33:45 in stead of 2022-07-12T06:33:45 for USA east cost time zone that state is not the last time when an indigo state was updated, but when a new EVENT time stamp arrived

• FIXED bug for "wall switch" devices status was not properly updated REMARK: The defined logic is not 100% correct. There are several modes (set on the bridge), ie when set to on/off on bridge the indigo state on/off only stays up for a few seconds. It should stay up as long as the button is pressed. This is also the case for all other switch sensors. This will only be corrected going from simple polling every 2 secs to async listening, BUT that is a major structural change for the plugin this will take some time

• CHANGED: added debug statement for 'hubNumber' error

added debug statement for 'hubNumber' error

fixed * on/off state and bright ness not properly updating for dimmable lamps * fixed on/offstate for all lamps made it consitent * fixed # of decimal point for RGB, White level, Color Temperature in indigo dev status display

======================================== 2022.11.29 @ 2022-06-22 New functions: * added state "created". It shows date-time stamp of when device was created, or if it is empty put current stamp in, ie for old devices, as we don't know when they were created. this is only useful for new devices created after this release

• added config option for default logging level(print received value updates to indigo log) for individual devices when they get auto created through "menu/create new devices...", which scannes all bridges and adds missing devices to indigo.

Improvements: * hue bridge adoption now semi-automatic in background in config after bridgeNumber and ip number confirmed it will try to pair/link to bridge and will show positive result in a popup window you still need to press the philips button on top of the bridge This way the plugin trys to link to the bridge every 5 seconds. It should succeeed as soon as you go to the bridge and press the button there. In case that process fails there is still the execute pair button in the config menu, which starts the paring process after you press the execute pair button

*streamlined device updates: instead of 10+ individual state updates, now it checks if there is a change in state value and then combines updates to a list. That should reduce server load from updates significantly

Fixes: * fixed some issues in print hue config menu

• lots of little clean-up of typos etc

*extended expiration time for confirming bridge # to 120 secs (from 15 secs) that should deal with message bridge confirm popup error message Also now after successfull delete / change IP# and (re-)pair bridge the config menu goes back to first step: "Select action for the bridge"

fix bug: is not a dimmer device restructured config menu to make it easier to understand for manaing bridges in config flow is now - select action (add(pair) / modify(IP) / delete) - select select bridge # - then set new Ip# .. - confirm with success / failure popup messages ==> should be easy to understand now

changed error logging to std python error logging added code to check if devices are "orphaned" ie have no bridge or a non existing bridge associated * *** this version requires python3 ie only runs uder indigo 2022.1 and later ***

bug fix: auto create hue devices did not set rgb white etc properties correctly bug fix: save preset error minor menu text changes in device light and group edit: - only current device is shown - if not created yet (=new dev) only NOT used hue devices (ie no indigo dev) are shown additions to menu print hue info ie print hue dev but no corresponding indigo dev and visa versa, some more formatted info for other print xxx menu options made MANY more things table driven, not hard coded in plugin, ie supports-xx xx= batterylevel rgb, white, onoff, sensorvalue, is dimmerdevice etc. all is set in file supportedDevices.py *added functionality to scan network for hue bridges. this done in the backgroud every 5 minutes (using /usr/bin/dns-sd functionality ) the list of network scan found bridges is available in config when you want to add a new bridge in config you can ask to have the scan run immediately. if you already know the ipnumber of your bridge this is not needed, but the ip # field is filled out automatically

• *** this version now requires python3 ie only runs uder indigo 2022.1 and later *** it might still work under py2 (earlier than indigo 2022.1) You need to change api version to 2.0 from 3.0 in info.plist, but no support for that

several bug fixes config menu was rewritten, should make it much easier to setup / modify bridge settings etc reduces error messages if wrong parameters are set etc. logging/debug toggle in menu and detailed logging selection in config some language clarification in menus * *** still runs under indigo 2022.1 and earlier *** * *** if no other MAJOR bugs found, this should be the last version that uns under Python2 ***

This will be the last release of the plugin for Indigo 2021.2 and earlier. It will also work on Indigo 2022.1, but most likely will not after that. The next version will be using the new 3.0 (Python 3) API introduced in 2022.1.

• Fixed a bug where pre-version 1.8 Hue bridge preferences weren't migrated correctly to the new 1.8 version.
• Fixed a bug that caused the plugin to crash when using the XYY color setting action.
• Added option to switch logging on/off for events and light changes such as "Hue Lights received 'dimmer dining' ON button press with short release" and "Updated 'dining room ceiling' on to 11".
• Fixed an error in doColorTemperature where not all arguments were converted during string formatting.
• Fixed "This Hue connected device is already being controlled by..." error.
• Fixed "unicode" object has no attribute "formate".[/list]

Special thanks to forum user kw123 for providing code fixing support.

• Added support for all light types without the need to update the plugin for every new model of light.
• Added support for multiple Hue bridges.
• Added Plugins menu option to print device details to the log

Special thanks to forum user kw123 for providing the code to support these new features.

• Added support for another GLEDOPTO light strip controller
• Added support for another Osram garden light pole.
• Added support for another Hue color/ambiance bulb.
• Added support for another Hue outdoor wall color light.
• Added support for 2 new Hue color spot lights.
• Added support for 2 new Hue dimmable lights.

• Added support for the Ikea FLOALT panel WS 60x60 color temperature LED panel.
• Added support for 3 new Hue outdoor lights.
• Added support for a new Hue color lamp.

• Added support for 2 new Hue outdoor Lily spotlights.

• Added support for a 3A Smart Home DE on/off light switch.
• Added support for another Hue White Candle bulb.
• Added support for an eWeLink on/off plug.
• Added support for an innr color/color temperature candle bulb.

• Fixed a syntax error bug in version 1.7.60 that caused the plugin to crash during loading.

• Added support for 2 new Hue white/color lights.
• Added support for 2 new Hue ambiance lights.
• Added support for the Innr SP 220 plug.

• Added support for a new Hue Still Ceiling light.
• Added support for 2 new Hue color pendant lights.
• Added support for a new Hue dimmable light.

• Added support for the Lightway/Megos E27 806 lumen bulb.

• Fixed a bug that would cause continuous Indigo error messages if a motion sensor was disabled on the Hue bridge.
• Added support for a new Hue ambiance candle bulb.
• Added support for a Hue Aurelle panel.

• Added support for another Hue Signe floor light model.
• Added support for an IKEA TRADFRI wall plug.
• Added support for an innr A19 dimmable bulb.

• Added support for another Hue Ambiance GU10 bulb model.

• Fixed another bug that would cause an error if a light strip only supported color temperature.

• Added compatibility with another Hue Amarant light.

• Fixed a bug that would cause an error if a light strip only supported color temperature.

• Added support for the Hue Argenta color spot bulb.
• Added support for an innr A19 color/color temperature bulb.

• Fixed a bug that would cause a state key error to appear in the Indigo log with Hue Wall Switch Module devices.

• Added support for a new TRADFRI dimmable bulb.
• Added support for an eWeLight full color/color temperature bulb.
• Added support for the Hue Wall Switch module.
• Added support for a new Hue ambiance downlight.
• Added option to disable ON and OFF ramp rates (transition times) in lighting device configuration dialogs to help improve compatibility with non-Hue lights.
• Fixed a bug that would cause the wrong color to be sent to a Hue Group when using the RGB picker in the Indigo UI.

• Added support for another GLEDOPTO color and color temperature light.

• Added support for the Hue Single color table light.
• Added support for a new Hue Dimmer Switch.
• Added support for the Osram Smart + LED GU5.3 reflector.
• Added support for 2m and 5m Hue Outdoor Lightstrips.
• Added support for the Hue Amarant Wall Washer light.
• Added support for the Hue white candle dimmable bulb.

• Fixed a bug that would cause an error when recalling a Hue scene if the scene creator had been deleted via the Hue web site (2nd attempt).
• Fixed saving and recalling Presets to be compatible with Hue Group devices as both source and target for Preset data.

• Added support for another Lidl Silvercrest On/Off Plug version.
• Added support for another Hue outdoor wall floodlight.
• Added support for another Hue Ambiance GU10 bulb.
• Fixed a bug that would cause an error when recalling a Hue scene if the scene creator had been deleted via the Hue web site.

• Added support for a new Hue color downlight (BR30)
• Added support for a new GLEDOPTO color/color temperature light.

• Added support for a new Hue Ambiance downlight.
• Added support for a new Hue white dimmable light.
• Added support for another GLEDOPTO color/color temperature light strip.
• Added support for another GLEDOPTO color/color temperature bulb.
• Added support for another Hue Smart Plug (Australia version).

• Added support for a new GLEDOPTO light.
• Added support for an Ikea FLOALT 30x30 color temperature light panel
• Added support for the Hue Gradient Lightstrip.
• Added support for the Lidl smart plug.
• Added support for the Lidl LivarnoLux Led color temperature bulb

• Fixed support for a Hue white and color GU10 bulb.

• Added support for a new Hue white and color GU10 bulb.

• Added support for a new Hue Play model.
• Added support for 2 new GLEDOPTO lights.
• Added support for the Hue Lily XL outdoor light.
• Added support for new Hue White (dimming only) lights.
• Fixed a bug with ambiance (color temperature only) lights that would cause an error if the White Level in the Indigo client was changed.

• Added support for a new Hue LED filament bulb variant.
• Added support for a new Hue Centura color downlight.
• Added support for a new Hue Ambiance downlight.

• Fixed a bug that would cause an error when attempting to select a Hue scene in the Recall Hue Scene dialog if the scene parameters on the Hue bridge don't include a corresponding scene creator (owner).
• Added support for a new dimming-only Hue white lamp.

• Fixed a bug that caused a plugin error when recalling a Hue scene.

• Added support for the Quotra-Vision RGB + warm/cool white light strip.
• Added support for version 4 of the Hue LightStrips Plus.
• Added support for the Innr SP 224 on/off plug.
• Added support for the IKEA TRADFRI E26 WW 806lm dimmable light.

• Fixed a bug that prevented the Set RGBW Levels Indigo action from working correctly.
• Fixed a bug that prevented device states from being updated for the original Hue LightStrip on newer Hue bridge firmware.

• Fixed support for the Adore Hue Ambiance Wall light.
• Added support for another Hue White Ambiance bulb.

• Added support for another Hue filament dimmable bulb.
• Added support for the Adore Hue Ambiance Wall light.
• Improved the native Indigo RGB and color temperature control implementation.

• Fixed a bug that would display an error in the Hue Device menu of the Save Preset and Recall Preset plugin menu dialog.

• Added support for another Philips white/color bulb.
• Added support for more Hue outdoor and floor lamps.

• Added support for another Philips dimmable light.
• Fixed a bug that displayed "True" or "False" as the on state for the Hue Smart Plug instead of "on" or "off".
• Fixed a bug that would display an error saying the device doesn't support color temperature when attempting to create a Set Color Temperature action for a Hue Group device.
• Fixed a bug that would always set the temperature scale to Celsius when creating a new Hue Motion Sensor device even if you selected Fahrenheit as the scale.

• Added support for the Innr Flex Color 4 meter RGBW LED Strip.
• Fixed a bug that prevented control of color channels in some GLEDOPTO LED controllers.
• Fixed a bug that prevented the selection of Hue Groups in the Hue Attribute Controller device configuration window.

• Fixed a bug that would cause the plugin to crash when updating light strip devices that have no color capabilities.

• Added support for the Müller-Licht (Aldi) ZBT color temperature light.
• Added support for GLEDOPTO color light strip drivers.
• Added support for Niko ZigBee switches.
• Added support for the TRADFRI 10 watt LED driver. Moved the already supported TRADFRI 30 watt LED driver into the Light Strips device model.
• Fixed a bug that would allow you to select a sensor or switch device as the target for a Hue Attribute Controller even though those devices can't be controlled.
• Fixed light device menus in various device configuration windows so Hue light devices are listed in alphabetical order.
• Fixed the group device menu in the Hue Group configuration window so the Hue Groups are listed in numerical group order rather than alphanumeric order.

• Added support for the Osram PAR-16 SMART+ Spot GU10 Multicolor 350lm light.
• Added support for a Hue color wall light and Hue filament bulb.

• Added support for the Hue Smart Button.
• Added a separate "Stop Brightening and Dimming" action to the available device actions.

• Fixed a bug that would cause the plugin to crash when validating device configurations whose Hue device had non-ASCII compatible Unicode characters in the device name on the Hue bridge.

• Added support for a new Hue white ambiance bulb (European model).
• Added support for another IKEA color temperature E26 bulb.

• Added support for another Hue Smart Plug model variant.
• Added support for a Hue white dimmable BR30 light.
• Added support for an IKEA TRADFRI E12 and GU10 dimmable light.

• Added support for a new Hue color B22 bulb.
• Added support for a new Hue white bulb.

• Added support for the Hue GU10 version 2 bulb.
• Added support for an IKEA dimmable 600 lumen E14 color bulb.

• Added support for an IKEA dimmable 1000 lumen E27 color temperature bulb.
• Added support for an IKEA dimmable 600 lumen E14 color temperature bulb.
• Added support for an IKEA dimmable 600 lumen E27 color LED bulb.

• Added support for a new Philips A19 dimmable light.

• Added support for a new Hue LED spiral filament ST64 bulb.
• Added support for the on/off OSRAM Smart+ Plug.
• Fixed plugin log issue that caused plugin log files to grow very large.
• Fixed the Innr On/Off Plug-in module so it appears in the On/Off Devices. If you already have the module set up with Hue Lights in Indigo, you MUST edit the device in Indigo and redefine it, otherwise it won't work after updating to version 1.7.16.

• Added support for a new Hue Ambiance E26 bulb.
• Added support for a new Hue LED filament G93 globe bulb.
• Added support for the UK variant of the Hue Smart Plug.

• Added support for the Hue LED filament ST19 Edison bulb and Hue LED filament G25 globe bulb.

• Added support for 2 new Hue dimming only GU10 lights.

• Added support for an Ikea dimmable 806 lumen E27 and dimmable 400 lumen E14 light.

• Added support for the Hue White PAR38 Outdoor light.
• Added support for another Hue White Ambiance BR30 bulb.
• Added support for another Feibit Inc. LED strip controller, branded as the 3A NUE ZigBee RGBW Light.

• Fixed a bug with the Hue Smart Plug where current on/off state would not update.
• Fixed a bug where using the Indigo's built-in Toggle On/Off action failed with dimmable Hue devices.
• Added support for a new version of Hue color lamp.

• Fixed a bug with Hue Group devices that prevented the Set Brightness with Ramp Rate action from working correctly.

• Fixed a bug that would cause the Hue Smart Plug device states to never update.

• Added support for the Hue Outdoor Lucca light.
• Added support for the Hue Smart Plug as a new On/Off device type.

• Fixed bug that would cause errors if a motion sensor was disabled in the Hue bridge. The plugin will now show a "disabled" error state for sensors that are turned off on the Hue bridge.

Added support for the Hue White PAR-38 flood light.

• Shortened sensor update interval to 1 second instead of 2 seconds.
• Shortened lights and groups update interval to 5 seconds instead of 10.
• Added support for the Innr RS-228T GU10 color temperature light.

• Added support for the Hue Signe Floor light.
• Added button hold states for the Run Less Wire switch device. Note that this feature is still experimental.
• Fixed issue where Run Less Wire switch button ON states may not be saved.

• Fixed a bug with Run Less Wire switch support that would not allow you to select a Run Less Wire switch device in the device selection dialog.
• Fixed a bug with Run Less Wire switch support that returned numerous errors when the plugin attempted to update the online state of the switch which has no online state.
• Fixed a bug with Run Less Wire switch support that would not update switch states during initial plugin load.

• Added support for the Run Less Wire switch.
• Fixed a bug that would prevent Hue Tap switches from appearing in the device selection list.

• Added support for the Hue Tap and Hue Dimmer Switches.
• Changed all references to the "Hue hub" to "Hue bridge".

• Added support for Hue Outdoor Motion Sensor.
• Added support for another GLEDOPTO color LED light strip controller.

• Added support for the Innr RB-185C color and color temperature light.
• Fixed a bug with the Hue Motion Sensor's Celsius temperature calculation that could cause constant "received ... sensor update" messages in the Indigo Event Log.

• Added support for a GLEDOPTO dimmable LED controller.

• Added support for another Hue Ambiance Ceiling light variant.

• Added support for the IKEA dimmable 980 lumen E27 color temperature bulb.

• Added support for the Feibit Inc. LED strip controller.

• Added support for the GLEDOPTO color/color temperature light strip.
• Added support for the Hue Play color/color temperature light.
• Fixed bug with existing support for GLEDOPTO generic ZigBee color temperature only light strip. It was previously part of the full color device group. It's now part of the Ambiance device group. This will require users to re-define the device in Indigo.

• Added support for the IKEA dimmable 600 lumen E26 color LED bulb.
• Fixed a bug (hopefully) that prevented Indigo from displaying color temperature sliders in the UI for Ambiance type Hue devices.

• Added support for the Dredesn Elektronik FLS-CT lp LED color temperature light.
• Added support for a Generic ZigBee WW/CW light strip.

• Added support for the ShenZhen Homa white and color LED light strip controller.

• Added support for the Osram PAR-16 GU10 Lightify light color light, Osram On/Off Plug and a second Hue outdoor LightStrips.

• Added support for the Hue LightStrips Outdoor.

Fixed a bug in the sensor device update function that could cause errors when updating motion sensor status in some situations.

Added support for the Hue outdoor lily spotlight and Hue outdoor pedestal light.

Added support for the Hue calla pathway bollard light.

• Added support for the Osram Gardenpole Mini RGBW light.

• Added support for the Innr SP 120 On/Off Plugin module.
• Added support for the IKEA 30x90 color temperature LED panel.

• Added support for the IKEA 30 Watt dimmable LED transformer.

• Added support for all the latest Philips Hue light models listed in Hue API.

Requires Indigo 7.0 or later.