homebridge-dyson-solarcycle-morph 1.4.1 → 1.4.3

package/CHANGELOG.md

@@ -5,6 +5,66 @@ All notable changes to this project are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.4.3] — 2026-09-22
+
+### Fixed
+
+- **A setting the lamp refuses is no longer reported as applied.** The lamp
+  answers every write to its location with a success status and then, on some
+  lamps, keeps its own value — so coordinates put in the configuration could sit
+  there for months doing nothing while the log claimed on every connection that
+  they had been applied. Measured on a CF06: roughly fifteen writes across a
+  day, every one acknowledged, the factory location still in place afterwards,
+  and the same lamp accepting the coordinates from the MyDyson app minutes
+  later. What the app does differently is not yet known.
+
+  Writes to the location and the time zone are now read back and checked, and a
+  refusal is logged as a refusal. If your lamp is one of these, set the location
+  once in the MyDyson app: daylight tracking needs the lamp to *have* a
+  location, not to have been given one by this plugin, and the Daylight switch
+  works normally once it does.
+
+### Added
+
+- **The log says what the lamp makes of its location.** Once a connection is up:
+
+  ```
+  F0:B1:A7:75:B1:D1 puts today's daylight between 07:09 and 19:22
+  ```
+
+  This is the lamp's own sunrise and sunset, and the only honest answer to
+  whether daylight tracking is really running. The Daylight switch is not: the
+  lamp accepts the mode, acknowledges it, never reports it back off, and then
+  does nothing at all if it has no location to work from — saying so only
+  through a small LED on its own base. A lamp in that state now says so in the
+  log instead.
+
+- **The lamp is told what time zone it is in.** Daylight tracking turns a place
+  into an hour, so the lamp needs the time zone as well as the coordinates, and
+  the MyDyson app writes both on every connection. This plugin only ever wrote
+  the coordinates. The offset and the daylight-saving rules now go in beside
+  them, and only when the lamp disagrees, so a lamp already holding the right
+  values is never written to.
+
+  Both come from the time zone of the machine Homebridge runs on — no setting to
+  fill in, and nothing asked over the network, which matters because these are
+  written while reconnecting, exactly when the network may still be down. A time
+  zone whose clock changes on a pattern this cannot state is left alone rather
+  than guessed at.
+
+## [1.4.2] — 2026-09-22
+
+### Fixed
+
+- **The Daylight, Auto Brightness and Movement switches no longer spring back
+  when the lamp is off.** The lamp takes none of the three while it is not lit:
+  the write goes nowhere, the lamp goes on reporting the mode it was already in,
+  and a moment later the Home app put the switch back where it had been. A
+  switch flipped on an off lamp now stays where it was put, and the mode is
+  written when the lamp comes on — by the Home app, the MyDyson app or the
+  button on its base. Nothing is held over a restart: a plugin starting up takes
+  all three from the lamp. With the lamp on, everything is as it was.
+
 ## [1.4.1] — 2026-09-21
 
 ### Changed

package/README.md

@@ -134,6 +134,15 @@ job — turn Auto Brightness off if you would rather it stayed put.
 turns itself off when you do. That is the lamp's own behaviour, not something
 the plugin decides. Flip the switch back on to resume.
 
+**The three mode switches work while the lamp is off**, though the lamp itself
+will not have them until it is lit — it takes none of the three while it is off.
+So a switch flipped on a dark lamp stays where you put it and is written the
+moment the lamp comes on, whether you switch it on from the Home app, from the
+MyDyson app or at the lamp. Turning Movement on last thing at night therefore
+does what you meant by it. Nothing is kept over a restart: a plugin starting up
+takes all three from the lamp, which is the only thing that knows what it is
+really doing.
+
 **Changes made at the lamp appear in the Home app**, usually straight away.
 
 **Out of range, the lamp shows as *No Response*** rather than the last thing it
@@ -239,6 +248,23 @@ lamp was set up on, and never asks again — so a lamp added through the app
 already knows, and one that has moved house still believes it is at the old
 address.
 
+> **Not every lamp accepts them.** One CF06 measured on 2026-09-22 acknowledged
+> both coordinates and stored neither — roughly fifteen attempts across a day,
+> every one reported as successful by the lamp itself, and the factory location
+> still in place afterwards. The same lamp took them from the MyDyson app
+> minutes later. Nobody has yet worked out what the app does differently. The
+> plugin now reads the values back after writing and says plainly in the log
+> when they did not stick:
+>
+> ```
+> F0:B1:A7:75:B1:D1 would not take the latitude: it acknowledges the write and
+> keeps its own value. Set it in the MyDyson app instead — see the README.
+> ```
+>
+> If you see that, set the location once in the MyDyson app. It sticks, and
+> daylight tracking works from then on — including through the plugin, which
+> needs the lamp to *have* a location but not to have been the one to give it.
+
 The two fields exist to set the coordinates without the app, and to correct them
 afterwards. Leave them empty and the plugin does not touch what the lamp holds —
 it still reads them on connecting and puts them in the debug log, which is the
@@ -264,6 +290,31 @@ connection goes out through a VPN. Nothing is sent to either service: they read
 the public address the request arrives from, which is what every site this
 machine contacts already sees. Check what it filled in before saving.
 
+### And what time it is there
+
+Coordinates alone are not enough: the lamp turns them into a sunrise using a
+clock, and it keeps neither reliably. **Take the lamp off the mains and it comes
+back holding Dyson's own coordinates in Wiltshire**, and its offset from UTC has
+been seen an hour out with nobody having written it. A lamp in that state blinks
+a few times when daylight tracking is switched on and then drops out of it —
+from the Home app and from the button on its base alike, because nothing is
+wrong with the command.
+
+So the plugin puts the time zone in beside the coordinates, on every connection,
+and only when the lamp disagrees:
+
+```
+UTC offset of F0:B1:A7:75:B1:D1 set to 2 (was 1)
+```
+
+**There is nothing to configure.** Both the offset and the daylight-saving rules
+come from the time zone of the machine Homebridge runs on, which already knows
+them exactly and knows them without asking the network — worth having, since
+these go in while reconnecting, which after a power cut is the moment the
+network is least likely to be up. A time zone whose clock changes on a pattern
+the lamp has no way of being told is left alone rather than guessed at; the
+common European and British rules are exact.
+
 ### Age adjustment
 
 The lamp can trim the brightness of its **Study and Relax modes** to suit the

package/dist/dyson/lamp.d.ts

@@ -118,6 +118,8 @@ export declare class DysonMorphLamp extends EventEmitter {
     private daylightReported;
     private readonly reconciles;
     private readonly settling;
+    /** Mode changes made while the lamp was off, waiting for it to light. */
+    private readonly pending;
     /** Whether the running scan is one we started and must clean up. */
     private discoveryIsOurs;
     /** So the "try power-cycling" hint is given once, not on every attempt. */
@@ -151,15 +153,6 @@ export declare class DysonMorphLamp extends EventEmitter {
     setPower(on: boolean): Promise<void>;
     /** @param percent HomeKit brightness, 0-100 %. */
     setBrightness(percent: number): Promise<void>;
-    /**
-     * Turn daylight tracking on or off.
-     *
-     * Goes out on the attribute channel, which is the one part of this lamp that
-     * acknowledges a write. Not reconciled all the same: the lamp announces the
-     * mode itself whenever it changes, from here, from the app, from the button
-     * on its base, or because setting a value by hand ended the tracking, so the
-     * report is a better answer than anything read back would be.
-     */
     /** Turn the lamp's own brightness trimming on or off. */
     setAutoBrightness(on: boolean): Promise<void>;
     /** Turn movement-triggered lighting on or off. */
@@ -172,6 +165,7 @@ export declare class DysonMorphLamp extends EventEmitter {
      * within a moment if the write did not land.
      */
     private setFlag;
+    private writeFlag;
     /**
      * Put the lamp into a preset, or take it out of the one it is in.
      *
@@ -179,7 +173,38 @@ export declare class DysonMorphLamp extends EventEmitter {
      * itself and says so, and writing both would race that.
      */
     setPreset(preset: Preset | 'none'): Promise<void>;
+    /**
+     * Turn daylight tracking on or off.
+     *
+     * Goes out on the attribute channel, which is the one part of this lamp that
+     * acknowledges a write. Not reconciled all the same: the lamp announces the
+     * mode itself whenever it changes, from here, from the app, from the button
+     * on its base, or because setting a value by hand ended the tracking, so the
+     * report is a better answer than anything read back would be.
+     */
     setDaylight(on: boolean): Promise<void>;
+    private writeDaylight;
+    /**
+     * Keep a mode change back while the lamp is off, rather than losing it.
+     *
+     * An off lamp discards these three silently and goes on reporting the old
+     * value, so writing one now would achieve nothing except a switch that
+     * springs back in the Home app a moment after it was flipped. The switch is
+     * left showing what was asked for — {@link patchState} has already published
+     * it — and the value is written when the lamp lights.
+     *
+     * @returns whether the change was held, in which case nothing is written.
+     */
+    private holdUntilLit;
+    /**
+     * Write the modes that were held back while the lamp was off.
+     *
+     * Called whenever the lamp lights, whoever lit it — HomeKit, the MyDyson app
+     * or the button on its base — and once more on connecting, for the lamp that
+     * was switched on while the link was down.
+     */
+    private flushPending;
+    private applyMode;
     setColorTemperature(kelvin: number): Promise<void>;
     private writeUint16;
     /**
@@ -291,8 +316,39 @@ export declare class DysonMorphLamp extends EventEmitter {
      * Read first, write only on a difference: these are settings rather than
      * controls, and rewriting them every connection would be churn on a channel
      * shared with the mode switches.
+     *
+     * **Some lamps will not take them at all.** Measured on a CF06 on 2026-09-22:
+     * both coordinates acknowledged with status `00`, neither stored, not even
+     * for the rest of the session, across roughly fifteen attempts in a day. The
+     * same lamp took the coordinates from the MyDyson app minutes later. Until
+     * somebody works out what the app does differently, the write is attempted,
+     * checked, and reported honestly when it fails — see {@link writeAndVerify}.
      */
     private syncLocation;
+    /**
+     * Put the host's time zone in the lamp, so it can turn a place into an hour.
+     *
+     * Sunrise needs a position *and* a clock. The MyDyson app writes the offset
+     * and the daylight-saving rules on every connection (`nd0/e.java`), taking
+     * both from the phone; this takes them from the host, which knows them
+     * exactly and knows them without asking the network — worth having, because
+     * these go out while reconnecting.
+     *
+     * Written only when the lamp disagrees, so a lamp that already holds the
+     * right values is never touched and the log stays quiet. Some lamps refuse
+     * the offset outright and say otherwise; see {@link writeAndVerify}.
+     */
+    private syncClock;
+    /**
+     * Say what the lamp makes of its location, for the log.
+     *
+     * These two are the only honest answer to "is daylight tracking actually
+     * running?". The mode attribute is no answer at all — the lamp takes the
+     * write, acknowledges it, never reports it back off, and then does nothing if
+     * it has no location to work from, saying so only through a small LED on its
+     * base. Sunrise and sunset are what it has actually computed.
+     */
+    private reportDaylightHours;
     /**
      * Put the configured age adjustment in the lamp.
      *
@@ -334,6 +390,24 @@ export declare class DysonMorphLamp extends EventEmitter {
     private writeAttribute;
     /** Ask the lamp for one coordinate, in degrees. */
     private readCoordinate;
+    /**
+     * Write an attribute and check the lamp actually took it.
+     *
+     * The acknowledgement is not proof for the settings behind daylight tracking.
+     * `0x2003`, `0x2004` and `0x2005` are all answered with status `00` and then,
+     * on some lamps, simply not stored — measured on a CF06 on 2026-09-22 by
+     * reading them back in the same session, immediately after the write. A
+     * plugin that believed the reply reported success for months while the lamp
+     * sat on the factory location.
+     *
+     * Tried once, not repeated. Repetition is the answer to most of this lamp's
+     * refusals, but not this one: five attempts in a row were refused just as
+     * uniformly as one, and each costs a write and a read on a link that would
+     * rather be left alone.
+     *
+     * @returns whether the lamp ended up holding the wanted value.
+     */
+    private writeAndVerify;
     private refreshState;
     /** Read what the lamp currently reports. Values it will not give up are absent. */
     private readState;