Renson healthbox 3.0

@Faecon You can install the renson plugin built by @rmassch which is the easiest solution :slight_smile:

Hi all, a Homey Pro community member has created a Homey Pro plugin which includes the sensor data, perhaps you can contact him to get his code? :slight_smile: RensonĀ® App voor Homey | Homey

Does anyone else have issues with the integration. Since about a week it canā€™t be loaded anymore. Seems to be an authentication error.

Logger: homeassistant.config_entries
Source: config_entries.py:551
First occurred: 06:54:58 (2 occurrences)
Last logged: 06:55:23

Error setting up entry 192.168.1.18 for healthbox
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 551, in async_setup
    result = await component.async_setup_entry(hass, self)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/healthbox/__init__.py", line 41, in async_setup_entry
    await api.async_enable_advanced_api_features()
  File "/usr/local/lib/python3.12/site-packages/pyhealthbox3/healthbox3.py", line 233, in async_enable_advanced_api_features
    raise Healthbox3ApiClientAuthenticationError
pyhealthbox3.healthbox3.Healthbox3ApiClientAuthenticationError

Could it be possible that your key is now no longer valid? I think they are valid for one year.

Early provided keys were valid for 1 year, newly requested keys will be valid for 3 years

2 Likes

@ronandezyn thatā€™s better, thank you. Out of curiosity, why is there a time limit on these keys?

I mean: this HealthBox doesnā€™t need to have Internet access to work. I usually block it, but I need to re-allow it from time to time because it checks the validity of the key (a bit annoying).

Is it not possible to have a key without this time limit and without validity check, so we just have to let it accessing Internet once, then it can stay offline? If the HealthBox needs constant access to Internet, thatā€™s suspicious.

Correct, you donā€™t need internet for standard operation, the validity of keys is purely a security matter while we work on an API platform where we have account management.

@ronandezyn Thank you for the reply! OK, good to know.

When this new API platform will be ready, please make sure the device can work totally offline once the key has been validated. In my case, all requests come from the local network, my key has been validated, and the device is no longer connected to the Internet. In this case, I donā€™t think it is needed to re-validate the key regularly, which requires Internet access, not have the key being marked as invalid after a while.

Exactly, when a key is requested through the platform, this will eliminate any manual process of generating a key and checking for a user account. The idea is that that key will be unlimited in time and would not require you to request a new one

1 Like

@ronandezyn : good news, thank you! If the key is unlimited in time, I hope the device will then check the key validation only once, and it will not require a constant Internet access.

Well that explains, didnā€™t think about checking that at all, but it was mentioned in the original email. :slight_smile: So I assume it would be running again when received a new key. Hopefully I donā€™t forget about it in three years. Should probably already put a reminder in my agenda.

Great work on the integration! Moved into a new place recently and was happy to see I could integrate my already installed health box in home assistant!

I read in this thread that youā€™re working on adding features to interact with the unit (send commands rather than just read out values). How is that going? It would be very nice to be able to control the unit from home assistant, as it would allow for some interesting automations :smiling_face:

1 Like

Not sure if this post is directed to me, but as far as API development goes, the currently used local API is not being developed further but is still maintained and supported. We are focusing on cloud API features and easy end-user onboarding (for now, the cloud API is limited to partners only) expect some exciting changes in late 2025 such as cloud controls, errors, restart, boost, settings, breeze etc. It is worth noting that when calibrated the device acts completely automatically based on demand controlled ventilation

1 Like

Off topic: for those of you who are interested, we have our own wired solution as well: Renson Smart Living: Smart living: improve your living comfort with home automation | Renson

1 Like

Hi,
I use the healthbox HACS intƩgration, and it works very well. But sometime my healthbox stop working correctly (ventilation on room stay activated and it should not). Everything is working again if I reboot the healthbox.
So I would like to automate a reboot everything night.
Is there a local API to reboot the healthbox ? The HACS integration has not this serviceā€¦
Thank you.

Hi, the API does not have a reboot function but this sounds like an issue with your device, may I suggest contacting your (or any) HVAC installer with knowledge of the system, they may be able to resolve your issue or repair your device if necessary.

Hi,
Ok thank you for your reply. I sent a ticket to the support.
Cheers

Any news regarding these details please? Voltage, Power, RPM

It is still not part of the plugin, so no updates there.
Also not sure when this plugin starts to break.
I do have some custom sensors setup for my device that i use to monitor those values.
You can copy this and only change the IP address () of the device. That should work for you as well. You can also update the scan_interval to your liking, though i found some issues when setting it too low that the device was not able to handle that many requests at the same time.

  # Fan details
- name: Ventilation Fan Voltage
  platform: rest
  resource: http://<IP>/v2/device/fan/voltage
  device_class: voltage
  unit_of_measurement: "V"
  scan_interval: 30
- name: Ventilation Fan Power
  platform: rest
  resource: http://<IP>/v2/device/fan/power
  device_class: power
  unit_of_measurement: "W"
  scan_interval: 30
- name: Ventilation Fan RPM
  platform: rest
  resource: http://<IP>/v2/device/fan/rpm
  unit_of_measurement: "RPM"
  scan_interval: 30
- name: Ventilation Fan Flow
  platform: rest
  resource: http://<IP>/v2/device/fan/flow
  unit_of_measurement: "mĀ³s"
  scan_interval: 30
- name: Ventilation Fan Pressure
  platform: rest
  resource: http://<IP>/v2/device/fan/pressure
  device_class: pressure
  unit_of_measurement: "hPa"
  scan_interval: 30

# Global stuff'
- name: Ventilation Air Quality Index
  platform: rest
  resource: http://<IP>/v2/api/data/current/sensor/0/parameter/index/value
  device_class: aqi
  scan_interval: 60
1 Like

Thx!
I added the things i want to my configuration.yaml like this:

# Renson Healthbox
sensor:
  - platform: rest
    resource: http://192.168.1.xx/v2/device/fan/voltage
    name: Renson Healthbox Ventilation Fan Voltage
    device_class: voltage
    unit_of_measurement: "V"
    scan_interval: 30
sensor:
  - platform: rest
    resource: http://192.168.1.xx/v2/device/fan/power
    name: Renson Healthbox Ventilation Fan Power
    device_class: power
    unit_of_measurement: "W"
    scan_interval: 30

But I can only see 1 rest entity:

And to limit the W result to 7.57W instead of 7.573905042348461 W, I need to give the sensor a unique_id?