matterbridge-daikin-local 0.10.0 → 0.11.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -4,6 +4,14 @@ All notable changes to this project will be documented in this file.
4
4
 
5
5
  The format is based on [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).
6
6
 
7
+ ## [0.11.0] - 2026-10-24
8
+
9
+ ### Changed
10
+
11
+ - [devices]: **Breaking:** devices stored by an earlier version change their identity in Matter at the first start, and the Matter apps take them for new devices: put them back in their rooms once. The name of a device in Matterbridge is made of the MAC address of its adapter, such as `Daikin A4:08:EA:CC:91:D4`, and the name given in the setup page is the label of the device, which the Matter apps show. Matterbridge derives the identity of a device from its name, so a new name no longer builds the device again: it is written to the label of each endpoint that is a device of its own, and the apps keep the device with its room and its automations.
12
+ - [devices]: A change of how a device appears in Matter, a reading its unit gives for the first time and a unit that accepts other settings than when it was set up no longer build the device again at once. The device keeps its endpoints, and is built again with its new options at the next restart of Matterbridge, which Matterbridge and the setup page ask for. Taking the endpoints of a device away and registering them again while Matterbridge runs made Apple Home take the device for a new one, with its room and its automations lost; across a restart the endpoint numbers are kept.
13
+ - [devices]: An endpoint that is brought back after it was taken away, such as the fan of its own turned off and on again, gets a new endpoint id, and with it a new endpoint number instead of the one it had: Apple Home could not change the settings of a device that came back under its old number. The air conditioner and the endpoints that stay keep theirs.
14
+
7
15
  ## [0.10.0] - 2026-10-20
8
16
 
9
17
  ### Added
package/README.md CHANGED
@@ -20,7 +20,7 @@ It is a [Matterbridge](https://matterbridge.io) plugin built on [daikin-local-co
20
20
  - **It works with adapters that ask for their KEY.** Some classic adapters only answer an app they have registered, and some have a child lock code. The setup page asks for each where it is needed, and the plugin does the rest. It is the only Matterbridge plugin that connects to these adapters: see the [comparison](#compared-with-other-daikin-plugins).
21
21
  - **It keeps working when an adapter gets a new IP address.** The plugin finds the adapter again and updates the address by itself, so an adapter on the same network as Matterbridge needs no fixed address on your router. Each air conditioner has the name you give it in the setup page, which a new name of its adapter does not change. The other local plugins know an adapter by the address you enter and by its name: see [How devices are stored](#how-devices-are-stored).
22
22
  - **It says when a unit stops answering.** After two reads in a row fail, your Matter app shows the air conditioner as unreachable, and it comes back by itself on the first read that works. A unit that is off when Matterbridge starts is still added, from what the plugin stored. None of the other Daikin plugins reports a unit as unreachable.
23
- - **Nothing needs a restart.** Add, change, reconnect and remove air conditioners while Matterbridge keeps running.
23
+ - **Almost nothing needs a restart.** Add, rename, reconnect and remove air conditioners while Matterbridge keeps running. A change of how one appears in Matter applies at the next restart, which the setup page and Matterbridge ask for, so that the Matter apps keep it with its room.
24
24
  - **It is more than a thermostat.** Besides power, mode and temperature you get the fan speed, the swing, the dry and fan modes, and Powerful, Econo and Streamer. The humidity appears by itself on a unit that gives it, and the outdoor temperature on a sensor you turn on.
25
25
  - **It fits the Matter app you use.** Matter apps differ in what they show, so you choose how each control appears: the fan speed as steps, as a percentage or on a fan of its own, and a switch for each thing your app has no control for. Presets for Apple Home and Google Home give you a starting point: see [Presets](#presets).
26
26
  - **It offers only what your unit can do.** The plugin asks each unit which modes, fan speeds, swing and temperature limits it has, builds its controls from the answer, and checks again after every start.
@@ -56,7 +56,7 @@ Open the plugin frontend from the plugin's row on the Matterbridge home page. It
56
56
  - the **child lock code**, the 4-digit code set under Child lock in the Daikin app the adapter was set up with, for an adapter that has one.
57
57
  3. **Options.** The name the air conditioner gets in Matter, starting from the name of its adapter, and how the fan speed, the swing and the extra switches appear in Matter, from what the unit can do. Start from a [preset](#presets) or choose each one yourself.
58
58
 
59
- Afterwards the same page lists your air conditioners with their status. From there you can add more, change the options of one, reconnect one that stopped answering, or remove one. None of this needs a Matterbridge restart. Matterbridge's own list of devices shows an air conditioner added or removed here once you reload its page.
59
+ Afterwards the same page lists your air conditioners with their status. From there you can add more, change the options of one, reconnect one that stopped answering, or remove one. Adding, renaming, reconnecting and removing need no Matterbridge restart; a change of how one appears in Matter takes effect at the next restart, which the page and Matterbridge ask for. Matterbridge's own list of devices shows an air conditioner added or removed here once you reload its page, named after the MAC address of its adapter, such as `Daikin A4:08:EA:CC:91:D4`: the name you give it is what the Matter apps show.
60
60
 
61
61
  <table>
62
62
  <tr>
@@ -158,7 +158,7 @@ The room temperature and the humidity are always on the air conditioner. You cho
158
158
  | Humidity | On the air conditioner, beside the room temperature. You can add a humidity sensor of its own, named `<name> Humidity`, for Matter apps that show no humidity on an air conditioner. It shows the same humidity, which stays on the air conditioner for the apps that do |
159
159
  | Outdoor temperature | None, unless you turn on a temperature sensor named `<name> Outdoor Temperature`. It is a device of its own, never on the air conditioner or a part of it, so that you can put it in another room, such as outside. It is off by default because a Matter app puts a new device in a room of its choosing, which may show the outdoor temperature as its own until you move the sensor |
160
160
 
161
- - **No adapter says which readings its unit has**, so the plugin goes by what the unit reads. The humidity and the outdoor temperature get their place in Matter the first time the unit gives them: at once for a unit that gave them during setup, and otherwise the air conditioner is built again in Matter when the reading first comes. An outdoor temperature with its sensor turned off builds nothing.
161
+ - **No adapter says which readings its unit has**, so the plugin goes by what the unit reads. The humidity and the outdoor temperature get their place in Matter the first time the unit gives them: at once for a unit that gave them during setup, and otherwise at the next restart of Matterbridge after the reading first comes, which the setup page and Matterbridge ask for. An outdoor temperature with its sensor turned off needs nothing.
162
162
  - **A reading keeps its place from then on.** Some units give no outdoor temperature while they are idle, and a sensor that came and went would be a device that comes and goes in your Matter apps.
163
163
  - **A reading the unit does not give right now shows no value**, instead of the last one it gave. This holds for all three, the room temperature included.
164
164
  - **Apple Home is reported to show a humidity only on a sensor of its own**, and not on an air conditioner: see the [Home Assistant Matter Hub notes](https://riddix.github.io/home-assistant-matter-hub/devices/temperature-humidity-sensor). The Apple Home preset adds that sensor for that reason. It has not been tested with this plugin.
@@ -295,7 +295,7 @@ flowchart TD
295
295
 
296
296
  Matter names a device, not its parts, so what a part is called is up to the Matter app. One that reads the tags can show `Vertical Swing`, one that does not shows numbered outlets to rename yourself, and one that shows no parts at all shows the air conditioner alone. This has not been tested in each Matter app: try it in yours, and turn it off if the parts do not show as you want.
297
297
 
298
- Changing the choice builds the air conditioner again in Matter. The switches, the mode selects, the fan and the humidity sensor are removed and added in their new place, so a Matter app takes them for new devices: they lose the rooms, the names and the automations they had there.
298
+ Changing the choice applies at the next restart of Matterbridge. The air conditioner keeps its room, but the switches, the mode selects, the fan and the humidity sensor are removed and added in their new place, so a Matter app takes them for new devices: they lose the rooms, the names and the automations they had there.
299
299
 
300
300
  ## Compared with other Daikin plugins
301
301
 
@@ -303,27 +303,27 @@ Three other Matterbridge plugins expose Daikin units. Which one fits depends fir
303
303
 
304
304
  This plugin is the only one of the four that finds the adapters itself, that speaks to classic, DSIOT (BRP084) and Airbase (BRP15B61) adapters, and that connects to an adapter which wants its KEY or a child lock code. It is also the only local one that follows an adapter to a new address, and the only one of the four that reports a unit which stops answering as unreachable. The others have strengths of their own: matterbridge-daikin-device controls the humidity, the ventilation and an air purifier, and matterbridge-daikin-onecta is the one for a unit that only the Onecta cloud reaches.
305
305
 
306
- | | matterbridge-daikin-local (this plugin) | [matterbridge-daikin-ac](https://github.com/andrasg/matterbridge-daikin-ac) | [matterbridge-daikin-device](https://github.com/lltcggie/matterbridge-daikin-device) | [matterbridge-daikin-onecta](https://github.com/mehmetc/matterbridge-daikin-onecta) |
307
- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
308
- | Connection | Local network, no cloud | Local network, no cloud | Local network, no cloud | Daikin Onecta cloud: needs internet, a Daikin Developer Portal app and a sign-in in a browser |
309
- | Units | Those with a classic (BRP069, BRP072), DSIOT (BRP084) or Airbase (BRP15B61) adapter, from the DAIKIN Mobile Controller, Daikin Airbase and ONECTA apps | Those with a classic adapter that answers over plain HTTP, which [daikin-controller](https://github.com/Apollon77/daikin-controller) talks to. Not Onecta units | Those with a DSIOT adapter that is a room air conditioner or an air purifier: it turns down any other. Tested on the AN22ZRS air conditioner and the ACK70Z air purifier | Units in the Onecta app: air conditioners and heat pumps |
310
- | Built on | [daikin-local-control](https://github.com/cheziyi/daikin-local-control), a library by the same author that works on its own | [daikin-controller](https://github.com/Apollon77/daikin-controller) | Its own DSIOT code | [daikin-controller-cloud](https://github.com/Apollon77/daikin-controller-cloud) |
311
- | Adding a unit | A search of the network and a guided setup page, or by address. No restart | IP addresses in the plugin settings, then a restart | IP addresses in the plugin settings, then a restart | Every unit of the account, with a white list and a black list |
312
- | KEY and child lock code | Asked for in the setup page, by the adapters that need them | Not supported: it cannot connect to an adapter that wants its KEY or a child lock code | Not supported: it cannot connect to an adapter with a child lock code. DSIOT adapters have no KEY | Neither applies: it signs in to the Daikin cloud |
313
- | New address or name | Found again by the MAC address of its adapter, so no fixed address is needed. Its name is the one you give it, which a new name of the adapter does not change | The address is changed in the settings. A new name makes a new device in Matter, which is known by its name | The address is changed in the settings, then a restart. A new name makes a new device in Matter, which is known by its name | Neither applies: each unit is known by its cloud ID |
314
- | A unit that stops answering | Shown as unreachable after two failed reads. One that is off at the start is still added, from what was stored | Not shown. One that does not answer within 90 seconds of the start is left out until the next restart | Not shown. One that does not answer at the start is left out until the next restart | Not shown, even while the cloud reports the unit offline |
315
- | Thermostat modes | Off, Cool, Heat, Auto, Dry and Fan only, and an optional switch for each mode, a mode select, or the modes the unit lacks running others | Off, Cool, Heat, Auto, Dry and Fan only | Off, Cool, Heat, Auto, Dry and Fan only, and a mode select that also has humidify | Off, Cool, Heat, Auto, Dry and Fan only |
316
- | Controls | Built from the modes, fan speeds, swing and temperature limits each unit reports | The same for every unit, with fixed temperature limits | Built for its two tested models | Modes and temperature limits from the cloud |
317
- | Fan speed | Steps, a percentage or not shown, on the air conditioner or on a fan of its own, and an optional switch for the auto speed | No | Low, Medium, High and Auto, a percentage, or a mode select | A fan device |
318
- | Swing | The rocking of the fan control, a switch for each axis, a mode select, or not shown with the mode you fix | No | The airflow direction of each axis, through a mode select | No |
319
- | Powerful, Econo and Streamer | An optional switch for each | No | No | A switch for Powerful |
320
- | Humidity | On the air conditioner, and on a sensor of its own if you add one, when the unit gives it | No | Target humidity and ventilation as fans, and a humidity sensor | A humidity sensor, on units that report it |
321
- | Outdoor temperature | A sensor you turn on, when the unit gives it | No | On the air conditioner and on a sensor | A sensor you can turn off |
322
- | Other devices | None | None | The ACK70Z air purifier, with its humidifier, its water tank and its air quality sensors. An optional switch that raises or lowers the setpoint by 0.5 °C | None |
323
- | How often a unit is read | Every 5 seconds, or what you set from 2 to 3600 | Every 3 seconds, or what you set from 2 | Every 6 seconds. No setting | Every 10 minutes by day and 30 by night, or what you set from 5. Daikin allows 200 calls a day |
324
- | Node.js | 22.19 or later, 24 and 26 | 24 and 26 | 20, 22 and 24 | 20.19 or later, 22.13 or later, 24 and 26 |
325
- | Documentation | English | English | Japanese | English |
326
- | License | Apache-2.0 | MIT | Apache-2.0 | Apache-2.0 |
306
+ | | matterbridge-daikin-local (this plugin) | [matterbridge-daikin-ac](https://github.com/andrasg/matterbridge-daikin-ac) | [matterbridge-daikin-device](https://github.com/lltcggie/matterbridge-daikin-device) | [matterbridge-daikin-onecta](https://github.com/mehmetc/matterbridge-daikin-onecta) |
307
+ | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- |
308
+ | Connection | Local network, no cloud | Local network, no cloud | Local network, no cloud | Daikin Onecta cloud: needs internet, a Daikin Developer Portal app and a sign-in in a browser |
309
+ | Units | Those with a classic (BRP069, BRP072), DSIOT (BRP084) or Airbase (BRP15B61) adapter, from the DAIKIN Mobile Controller, Daikin Airbase and ONECTA apps | Those with a classic adapter that answers over plain HTTP, which [daikin-controller](https://github.com/Apollon77/daikin-controller) talks to. Not Onecta units | Those with a DSIOT adapter that is a room air conditioner or an air purifier: it turns down any other. Tested on the AN22ZRS air conditioner and the ACK70Z air purifier | Units in the Onecta app: air conditioners and heat pumps |
310
+ | Built on | [daikin-local-control](https://github.com/cheziyi/daikin-local-control), a library by the same author that works on its own | [daikin-controller](https://github.com/Apollon77/daikin-controller) | Its own DSIOT code | [daikin-controller-cloud](https://github.com/Apollon77/daikin-controller-cloud) |
311
+ | Adding a unit | A search of the network and a guided setup page, or by address. No restart | IP addresses in the plugin settings, then a restart | IP addresses in the plugin settings, then a restart | Every unit of the account, with a white list and a black list |
312
+ | KEY and child lock code | Asked for in the setup page, by the adapters that need them | Not supported: it cannot connect to an adapter that wants its KEY or a child lock code | Not supported: it cannot connect to an adapter with a child lock code. DSIOT adapters have no KEY | Neither applies: it signs in to the Daikin cloud |
313
+ | New address or name | Found again by the MAC address of its adapter, so no fixed address is needed. Its name is the one you give it, which a new name of the adapter does not change, and which the Matter apps take without losing the device | The address is changed in the settings. A new name makes a new device in Matter, which is known by its name | The address is changed in the settings, then a restart. A new name makes a new device in Matter, which is known by its name | Neither applies: each unit is known by its cloud ID |
314
+ | A unit that stops answering | Shown as unreachable after two failed reads. One that is off at the start is still added, from what was stored | Not shown. One that does not answer within 90 seconds of the start is left out until the next restart | Not shown. One that does not answer at the start is left out until the next restart | Not shown, even while the cloud reports the unit offline |
315
+ | Thermostat modes | Off, Cool, Heat, Auto, Dry and Fan only, and an optional switch for each mode, a mode select, or the modes the unit lacks running others | Off, Cool, Heat, Auto, Dry and Fan only | Off, Cool, Heat, Auto, Dry and Fan only, and a mode select that also has humidify | Off, Cool, Heat, Auto, Dry and Fan only |
316
+ | Controls | Built from the modes, fan speeds, swing and temperature limits each unit reports | The same for every unit, with fixed temperature limits | Built for its two tested models | Modes and temperature limits from the cloud |
317
+ | Fan speed | Steps, a percentage or not shown, on the air conditioner or on a fan of its own, and an optional switch for the auto speed | No | Low, Medium, High and Auto, a percentage, or a mode select | A fan device |
318
+ | Swing | The rocking of the fan control, a switch for each axis, a mode select, or not shown with the mode you fix | No | The airflow direction of each axis, through a mode select | No |
319
+ | Powerful, Econo and Streamer | An optional switch for each | No | No | A switch for Powerful |
320
+ | Humidity | On the air conditioner, and on a sensor of its own if you add one, when the unit gives it | No | Target humidity and ventilation as fans, and a humidity sensor | A humidity sensor, on units that report it |
321
+ | Outdoor temperature | A sensor you turn on, when the unit gives it | No | On the air conditioner and on a sensor | A sensor you can turn off |
322
+ | Other devices | None | None | The ACK70Z air purifier, with its humidifier, its water tank and its air quality sensors. An optional switch that raises or lowers the setpoint by 0.5 °C | None |
323
+ | How often a unit is read | Every 5 seconds, or what you set from 2 to 3600 | Every 3 seconds, or what you set from 2 | Every 6 seconds. No setting | Every 10 minutes by day and 30 by night, or what you set from 5. Daikin allows 200 calls a day |
324
+ | Node.js | 22.19 or later, 24 and 26 | 24 and 26 | 20, 22 and 24 | 20.19 or later, 22.13 or later, 24 and 26 |
325
+ | Documentation | English | English | Japanese | English |
326
+ | License | Apache-2.0 | MIT | Apache-2.0 | Apache-2.0 |
327
327
 
328
328
  The table is read from the README, the settings and the source of matterbridge-daikin-ac 2.0.0 and the daikin-controller library it uses, matterbridge-daikin-device 1.0.2 and matterbridge-daikin-onecta 0.1.1, in October 2026. None of the three was run for it.
329
329
 
@@ -332,13 +332,13 @@ The table is read from the README, the settings and the source of matterbridge-d
332
332
  The plugin knows each air conditioner by the **MAC address of its adapter**, so neither a new IP address nor a new name makes it lose track of one. The MAC address is also the serial number the air conditioner has in Matter. A switch, a mode select, a fan or a sensor that is a device of its own has that serial number with a dash and a letter after it, such as `A4:08:EA:CC:91:D4-V` for the vertical swing switch:
333
333
 
334
334
  - **The address is kept up to date.** The plugin searches the network when it starts, every 5 minutes, and at once when a device stops answering. An adapter that answers from a new address has it updated.
335
- - **Each device has the name you give it in the setup page**, which starts as the name its adapter announces, followed by a number when another device has that name already, such as `Bedroom 2`. A new name of the adapter does not change it. No two devices share a name, because the name is what Matter shows and what its switches and sensors are named after.
336
- - **A new name builds the device again in Matter**, with the same serial number. A Matter app may take it for a new device, and ask you again for its room and its automations.
335
+ - **Each device has the name you give it in the setup page**, which starts as the name its adapter announces, followed by a number when another device has that name already, such as `Bedroom 2`. A new name of the adapter does not change it. No two devices share a name, because the name is what the Matter apps show and what its switches and sensors are named after.
336
+ - **A new name changes nothing else in Matter.** The device keeps its identity: in Matterbridge's own list of devices it is named after the MAC address, such as `Daikin A4:08:EA:CC:91:D4`, and the name you give it is the label the Matter apps show, which a new name replaces in place. The apps keep its room and its automations, and one that let you rename it there keeps the name you chose.
337
337
  - **An adapter added by address is followed like any other** when a search can reach it: the plugin reads its MAC address at the address you enter. An adapter on another subnet or VLAN, which no search reaches, keeps the address you entered, so give it a fixed one on your router.
338
338
  - **An adapter that has no name** is named by you in the setup page.
339
339
  - **An adapter that reports no MAC address cannot be added**, because the plugin would have nothing to follow it by.
340
340
 
341
- What each unit can do is read when it is added, and checked again after each start of the plugin and each time you open its options in the setup page. If it changed, for example after an update of the unit's firmware or of this plugin, the air conditioner is built again in Matter and a setting the unit no longer takes is reset.
341
+ What each unit can do is read when it is added, and checked again after each start of the plugin and each time you open its options in the setup page. If it changed, for example after an update of the unit's firmware or of this plugin, a setting the unit no longer takes is reset, and the air conditioner is built again in Matter at the next restart of Matterbridge, which the setup page and Matterbridge ask for.
342
342
 
343
343
  The devices are stored in the plugin configuration, which Matterbridge keeps in `matterbridge-daikin-local.config.json`, with the child lock code as plain text. They are added, changed and removed in the setup page only: the Matterbridge config editor does not list them.
344
344
 
@@ -358,7 +358,8 @@ A stored device that this version of the plugin cannot read, for example one sto
358
358
  - **Requests to one adapter go one at a time.** The reads and the commands of a device wait for each other, and different devices are read at the same time. A check from the setup page uses a connection of its own, so it can overlap with a read.
359
359
  - **A command is built from the last poll** instead of reading the unit again first, when that poll is no older than the poll interval, or than 30 seconds when the interval is longer. In that window, a change made on the unit's own remote control since the last poll is undone by the command. Set a shorter poll interval to narrow it.
360
360
  - **A device is reported as unreachable** after two reads in a row fail, and as reachable again on the first read that works.
361
- - **Changing how the fan, the swing, any switch or any sensor appears** rebuilds the air conditioner in Matter. Some Matter apps take a moment to show the change, or need the accessory page reopened.
361
+ - **What the Matter apps keep follows one rule: whatever stays keeps its room and its automations, and whatever was removed comes back as new.** A restart, a new name, a new address and a change of options keep the air conditioner and every switch or sensor that stays. A switch or a sensor that an option change adds is new, in the default room. One that is removed is gone, and turned on again later it is new as well, never the one the apps knew. A removed air conditioner added again is new too, with all its switches and sensors.
362
+ - **Changing how the fan, the swing, any switch or any sensor appears** takes effect at the next restart of Matterbridge, which the setup page and Matterbridge ask for. Until then the air conditioner keeps its current controls.
362
363
  - **The settings and the setup page do not overlap.** The Terminal ID and the poll interval are set in the plugin's settings in Matterbridge, and the air conditioners in the setup page. A save of the settings never changes the air conditioners.
363
364
  - **The setup page is as open as Matterbridge itself.** Anyone who can reach the Matterbridge frontend can use it. It never returns a stored child lock code.
364
365
  - **A ducted unit on an Airbase adapter** gets the controls of any other unit: power, mode, target temperature, fan speed and swing. Its zones, its fan auto and its airside are not in Matter. A unit with zones reports no auto fan speed and no swing, so it gets neither, and an Airbase adapter asks for no KEY and no child lock code.