Mitsubishi Comfort

Problem The fan-only switch (since 1.4.0), the dry switch (1.5.0), the humidity characteristic, and the filter indicator were all added to the accessory after it was published to the bridge, from async streaming callbacks, but the plugin never called `api.updatePlatformAccessories([accessory])`. They existed in memory and the HAP cache but never reached the Home app. Fix Centralized re-publish in `accessory.ts:publishStructureChange()`, called at every runtime add/remove site (fan/dry switches, humidity characteristic, filter service). Verification Reproduced and fixed on a live 5-zone …

Excerpt saved from GitHub on 2026-10-22.

I have 4 - MSZGL06NA, 1 - 12NA, and 1 - 8NA2 Also I noticed that the temp I set inside the Apple Home app is always one higher than was was actually set on the comfort app. Yes, this is an issue because the Kumo API uses Celsius and the Mitsubishi app and Apple Home round the temperatures to Fahrenheit in different ways. I will see what I can do more on this

Excerpt saved from GitHub on 2026-10-22.

First off thank you to the developer for getting this plugin online. Below is a log of what is happening. Now, some things work like turning on and off my ductless splits. However, when changing temperature it falls back to the original temp. For example, after turning on the split it has a temp of heating to 65 degrees F. When I change that to 70 degrees, in about 5 seconds it changes back to 65 however that is what shows on HomeKit. If I look in the comfort app itself it says it's set to 69 degrees. In further looking at this, there seems to be a delay as to what HomeKit thinks the temp is. …

Excerpt saved from GitHub on 2026-10-22.