Fan values don't work well with Homekit

[electroflame]

Hi there -- thanks for the integration!

This works great overall. However, Homekit's fan control seems to trigger the min/max cap, so rather than a full range of 0-100, you can only set the fan speed in pre-defined steps (it seems like about 4 steps). This is kind of confusing, as you can drag the fan slider and Homekit thinks the value is set, but the Bedjet doesn't actually respond. If you close/reopen the Home app the slider will update with what the Bedjet's actually set to.

Does the plugin just automatically try to cap the value to the nearest pre-defined step?

[asheliahut]

To tell you the truth @electroflame this is a fork that I have been just making work on basically a maintenance purposes and made it a little more user friendly to setup/manage. I don't know how the original code works that well or how the code works with the BedJet. I am open to discussions on it and time to dig in more to make it better, but honestly I never even looked at the original code that deep to know what it does for setting the values.

[electroflame]

@asheliahut Haha, fair enough. I'm not that familiar with Python otherwise I would've taken more than a cursory look.

Basically it seems like the fan values are being clamped by the presets (i.e. Low, Medium, High), even when trying to set a value directly via Homekit. Basically you can't set values in increments of 5% like you can on the remote, as it jumps to values roughly around 33%, 66%, 100%, etc.

It's interesting that the values reported by Homekit are also incorrect (i.e. 66% is reported when the remote is actually set to 75%) so I'm not sure what's going on there.

If I get a little more time I might try and take a closer look and see if I can figure out where things are going wrong -- that is if you don't get to it first.

[asheliahut]

Awesome! I will definitely look into this soon, but not 100% when yet.

[Swop1925]

Hello @asheliahut and @electroflame. I'm checking in on this to see if there's a fix yet. I'm having the exact same issues as reported in the Feb 28 post @electroflame.

I've also noticed that the M1, M2, and M3 (preset/memory buttons) don't show up in HomeKit via HomeKit Bridge.

If there's an easy way to integrate these preset/memory buttons, that may be a nice workaround. Once a "biorhythm" (I hate that name - it's really just a preset) is mapped on to M1, for instance, then you can just run that through HomeKit. Because Biorhythms are set up using the actual BeJet remote, you can be precise on fan speeds, etc.

Anyway, just a thought about one way to address this - getting the M1, M2, and M3 buttons integrated into HomeKit Bridge may be an easy fix rather than figuring out fan speed integration.