Nice App! There are many options to set as status information on the device tile, what is missing however is the ventilator speed in % (NL: Ventilatorsnelheid) . The ventilator setting in % (NL: Ventilator Instelpunt) is available but that value deviates from the actual ventilator speed. (Example: to set ventilator to 30%, the ventilator speed setting must be set at 33%). There is only a flowcard to set the ventilator speed, but there is no matching status value that shows that setting. I now have to add 3 to the setting value (33%) to have the Ventilation setting of 30%
>> Please add “Ventilatorsnelheid” in % to the available status fields.
I control my two Itho units over MQTT, and was actually about to build my
own Homey app for it because I didn’t know this one already existed. Exactly what I wanted; a local, no MQTT app. Nice work.
Now the issue: as soon as I enable API authentication on the module, both devices switch to “Device unavailable” and I can’t read or control them anymore. Disable API authentication and everything works fine.
Credentials are definitely correct, calling the module directly with wrong/no auth
returns “AUTHENTICATION FAILED” (HTTP 200), so the module itself is reachable, it’s just
the app’s login getting rejected. I entered the username correctly in the app, but while troubleshooting with Claude it turned out the stored username shows up as " admin" with leading spaces, so something in how the app stores or sends the credentials looks off.
Worked around it for now by disabling API authentication, but would rather keep it on.
Can test a fix or share logs if useful.
Is it occurring on both mobile and web app when entering & saving credentials?
Tested with both mobile & web app:
Pro 2026 v13.4.0 App v1.2.3 Module firmware v3.0.0 r2
After enabling API authentication @ itho module:
@ Homey: Changing “API requires authentication” from NO to YES (I hadn’t entered credentials ever before) works fine:
@ObelixNL I Just noticed the new update and couldn’t wait to try out the new Boost button for my WPU.
However, I now see error A01-16, which I understand is an expected side effect of using manual_control.
Will the app automatically clear this error once the boost has finished, or would I need to create a Flow to reset it? If a Flow is needed, is there a way to detect when the WPU has returned to automatic mode?
The app doesn’t clear A01-16 itself. It only sends the manual_control command; the alarm is raised and released by the WPU.
To detect when the WPU is back in automatic mode, use the trigger “Manual operation changed” with active = false. You can also watch the “Manual control (sec)” countdown reaching 0.
The manual mode ends on its own after the “Max manual operation time (min)” setting. You can also end it earlier with the “Set boost mode → Off” action.
Please tell me whether A01-16 disappears after that. If it doesn’t, I can look into adding a reset.
I have created 1.3.1 default after 600 seconds the boost button resets to default. You can change the 600 seconds in the device settings. And an other action card with durration setting.
