current temperature reading incorrectly

[johannesparty]

filing as a new bug because not sure this is the same as the "null" device problem. this was using 1.8.14 from earlier today.

[johannesparty]

homebridge-kumo.log

[fjs21]

I need the log when the plug-in initializes after restart. The root issue is that your device is not correctly being recognized.

Look for

Initializing "%s" of unitType "%s" as generic (unspecified) unit.

The log around that will be very useful.

[johannesparty]

Ok I’ll get it ASAP but probably not for 3-4 hours (can’t do it right now). Thanks!

On Wed, Nov 3, 2021 at 8:36 PM Fraser Sim @.***> wrote:

I need the log when the plug-in initializes after restart. The root issue is that your device is not correctly being recognized.

Look for

Initializing "%s" of unitType "%s" as generic (unspecified) unit.

The log around that will be very useful.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/fjs21/homebridge-kumo/issues/47#issuecomment-960429173, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVKXY3HETVCWNHM7TR2HSHTUKIEWBANCNFSM5HKORVYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

-- Johannes Schmidt @.*** 408-621-0091

[johannesparty]

Ok it looks like that info is in the "homebridge-kumo" file attached to the 2nd comment for this issue.

The relevant line is: [11/3/2021, 8:02:29 PM] [homebridge-kumo] Initializing "Office" of unitType "null" as generic (unspecified) unit.

More info below, but I also noticed the following and wonder if might be a problem...

[11/3/2021, 8:02:29 PM] [homebridge-kumo] { _api_error: 'device_authentication_error' } [11/3/2021, 8:02:29 PM] [homebridge-kumo] Kumo API: bad response from queryDevice_Direct - { _api_error: 'device_authentication_error' } [11/3/2021, 8:02:29 PM] [homebridge-kumo] Failed to connect to device IP (9Z34P008U100021F). <--- this is the correct serial number ... [11/3/2021, 8:02:29 PM] [homebridge-kumo] Disabling directAccess to Kumo devices the "address" in the log files is 192.168.30.228 which is correct. I can "ping" too.

Here is my "config": { "username": "(redacted)", "password": "(redacted)", "directAccess": true, "simpleDuctless": true, "_bridge": { "username": "0E:DB:2D:DC:07:2B", "port": 51020 }, "platform": "Kumo" }

Here are a few events before/after the "unitType "null"" line. The attachment indicated above contains "everything"...

[11/3/2021, 8:02:29 PM] [homebridge-kumo] { id: '2253633959278315', record_time: '2021-11-04T03:02:14.801Z', device_serial: '9Z34P008U100021F', it_status: null, rssi: -48, power: 1, operation_mode: 3, set_temp: null, set_temp_a: null, fan_speed: 3, air_direction: 5, prohibit_local_remote_control: null, room_temp: 22.5, room_temp_beyond: null, room_temp_a: null, out_of_use: null, unusual_figures: 32768, two_figures_code: 'A0', status_display: 0, actual_fan_speed: null, sp_cool: 20, sp_heat: 17, sp_auto: -1, raw_frames: null, run_test: 0, active_thermistor: null, temp_source: null, seconds_since_contact: 14 } [11/3/2021, 8:02:29 PM] [homebridge-kumo] Initializing "Office" of unitType "null" as generic (unspecified) unit. [11/3/2021, 8:02:29 PM] [homebridge-kumo] Office: Found heat and cool settings will use ductless accessory [11/3/2021, 8:02:29 PM] [homebridge-kumo] This plugin threw an error from the characteristic 'Model': characteristic must have a non null value otherwise HomeKit will reject this accessory, ignoring new value. See https://git.io/JtMGR for more info. [11/3/2021, 8:02:29 PM] [homebridge-kumo] Error: at Model.Characteristic.characteristicWarning (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:2074:105) at Model.Characteristic.validateUserInput (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1903:14) at Model.Characteristic.setValue (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Characteristic.ts:1334:20) at AccessoryInformation.Service.setCharacteristic (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/Service.ts:475:35) at new KumoPlatformAccessory_ductless_simple (/usr/lib/node_modules/homebridge-kumo/src/ductless_simple.ts:39:10) at KumoHomebridgePlatform.discoverDevices (/usr/lib/node_modules/homebridge-kumo/src/platform.ts:140:15) at processTicksAndRejections (internal/process/task_queues.js:95:5)

[11/3/2021, 8:02:29 PM] [homebridge-kumo] Kumo response: [ true, null, [ [ { active_thermistor: null, actual_fan_speed: null, air_direction: 5, device_serial: '9Z34P008U100021F', fan_speed: 3, id: '2253633959278315', it_status: null, operation_mode: 3, out_of_use: null, power: 1, prohibit_local_remote_control: null, raw_frames: null, record_time: '2021-11-04T03:02:14.801Z', room_temp: 22.5, room_temp_a: null, room_temp_beyond: null, rssi: -48, run_test: 0, seconds_since_contact: 15, set_temp: null, set_temp_a: null, sp_auto: -1, sp_cool: 20, sp_heat: 17, status_display: 0, temp_source: null, two_figures_code: 'A0', unusual_figures: 32768 } ], [] ] ]

[fjs21]

So I'm trying to understand your log with the startup yesterday around 1:46pm - it looks like you are running homebridge-kumo on a child bridge. You have a single unit named "Office". Your unitType is null.

The first restart starts around 1:46pm using v.1.8.10. The only error occurs with the attempted null assignment of the Model Characteristic. There were no other errors but it looked to be polling the device every ten minutes (which it does for recording the temperature history in Eve).

You restarted again around 8 pm using v.1.8.10. A time out occurred on the initial connection to Kumo. This is an intermittent error. In v1.8.14, the plugin will keep trying to connect every 10 seconds until it succeeds. Because the initial connection failed, the api then threw a device authentication error at 8:02:29. This caused the plugin to revert to Kumo Cloud (vs. directAccess). At which point, you got an appropriate response from the Kumo cloud. This is normal behavior as a fallback in case directAccess fails which it can if the IP address changes or in your case the authentication via directAccess was not established.

Then at 8:02:29. the ductless_simple accessory was initiated causing the same error with respect to Model Characteristic. At which point, the log ends.

So on the basis of this, there is one remaining error associated with the model name. I should have fixed this in the next version. v1.8.15.

[johannesparty]

homebridge-kumo.log

Now I'm not entirely sure what to think; the Kumo<->HomeKit mapping may just be very confusing.

In HomeKit, I have five tiles:

Power, "Off" <--- weird Thermostat, "32F, Cooling to 67" <--- not 32F here, but cooling to 67 ok Fan, "Off" <--- not at all Heater/Cooler, "73F, Cooling to 68" <--- about right, but doesn't show fan If I show as a "single tile", it is even less useful. The summary area at top shows "32-73, Cooling" with blue arrow pointing down.

In fact, AC is running, set to 68, Current Temp 73, Fan Medium. (I don't worry about 67 vs 68 ... probably just rounding differently from C to F).

In Kumo App, I have

68F, Now 73 with snowflake" Mode: Cool Fan Speed: Medium (this all is correct)

In Homebridge, I have Power: Off Thermostat: 32F Off Fan: Off Heater/Cooler: 73.4, 68, looks like On (brighter background) Dehumidifier: Off <-- seems to be extra/broken one ... can't hit gear icon or anything... Dehumidifier: Off <-- gear shows misc. info, model as "unknown using ductless_simple"

I have attached screenshots.

I could almost just hide everything but the Heater/Cooler one, but I would like to be able to control fan too.

Thanks!

[fjs21]

Ok. This is easier to fix. You need to remove the cached accessories. Use the homebridge UI to remove all of the accessories associate with Kumo. Then restart. It will add back just the ones that are current.

You can control the fan speed in the heater cooler in the home app. Press and hold and then scroll down. You should see fan speed and an on/off slider for oscillation control.