I have an initial attempt at a fix here: Support target temperature for htr_mod devices by graham33 · Pull Request #57 · graham33/hass-smartbox · GitHub
If anyone is able to test it, and/or comment on the question in Haverland API with radiators, read-only temperature, and cannot set heat/auto modes · Issue #49 · graham33/hass-smartbox · GitHub, that would be great. I’ll try to fix the power issue next.
I’ve released a new beta version which addresses some of the problems for htr_mod devices.
Hopefully you should be able to get and set the target temperature and turn it on and off correctly. Thanks @jmcucurella for testing!
Next up will be supporting power properly (Some radiators don't support the 'power' attribute · Issue #51 · graham33/hass-smartbox · GitHub) and various presets and modes (comfort/eco/ice presets and self_learn and presence modes), see Support htr_mod presets · Issue #60 · graham33/hass-smartbox · GitHub.
State “active” false or true is not updated on HA.
Are you referring to Some radiators don't support the 'power' attribute · Issue #51 · graham33/hass-smartbox · GitHub, or do you mean that the heater doesn’t somehow show whether it’s in Idle or Heat mode (that’s the other place the active attribute is used), or something else?
I have a fix for the power attribute issue for htr_mod nodes: Don't create power sensors for htr_mod nodes by graham33 · Pull Request #62 · graham33/hass-smartbox · GitHub. It just doesn’t create any power sensors for those nodes, since I don’t think they expose any way of measuring the power usage. If someone knows a way to do it I’m happy to look into it.
Hi. Sorry for the delay in answering. Here you have the steps I followed to extract the token:
Login at the corresponding website (in my case the brand of my radiator is Haverland: i2control.haverland.com) and navigate to the page with the smartbox information.
In Chrome: right-click anywhere on the page, select Inspect to open the developer tool (How to Inspect Element in Chrome | BrowserStack)
Click on the “Network” tab, select “All” button.
Select “Token” on the left panel, and the HTTP headers will be displayed on the right panel. The token appears next to “authorization” header.
Hope it works!!
I’ve made some further progress: Release v1.1.0-beta.3 · graham33/hass-smartbox · GitHub
This should support presets for htr_mod heaters, and it also setting the preset mode for all heater types. I’d be grateful if someone could give it a try.
I’ve made many tests and all is working ok, incluiding “state” updating
That’s great! Thanks very much for testing. I’m gradually working on a couple more features, so I’ll do one or two more beta releases before a production 1.1.0 release.
Another release yesterday: Release v1.1.0-beta.4 · graham33/hass-smartbox · GitHub
This should hopefully resolve outstanding issues with acm type radiators.
i am getting this in:
File “/usr/local/lib/python3.10/site-packages/requests/models.py”, line 1021, in raise_for_status
raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api-haverland.helki.com/client/token
how many character is the token?
Hi there.
Our landlord is talking about replacing our old storage heaters with Haverland rads. The electrician suggested the Simply model which has app control, but from what I’ve read that only uses Bluetooth, and so probably won’t work with Home Assistant.
Which ones should I encourage the landlord to get to work with this integration? The smart box device doesn’t appear to be a thing anymore. But the Ultrad radiators seem to have their own WiFi connectivity. Would Ultrad be the right ones? Are the RCTT Connect ones supported?
Final question; is there local control? Or do these radiators rely on a working internet connection?
Edit: I just read the Ultrad brochure PDF and saw that these use the Smart Box device. Does anyone know whether the Simply or RCTT models work?
I believe, from previous posts here and discussions on Github, people who have Haverland Ultrad and Smartwave Wi-x radiators have them working in Home Assistant with the smartbox custom component. I don’t have direct experience myself though (I have Climastar heaters).
I’m just implementing support for switches for window mode, true radiant/adaptive start control and possibly boost. I’d be helpful if people could send me the output of smartbox setup for their devices, particularly if you have an acm or htr_mod type device. Hopefully I’ll release a new version in the next couple of days.
Also, FYI, the way the power sensors currently work seems to be very inaccurate (it assumes the full power is being used any time the heater is active, but it only gets updates quite infrequently). If anyone has any ideas on how to measure this in a better way I’d be interested to hear them.
The Haverland SIMPLY only uses Bluetooth , primarily to upload and download programming. This radiator also has a manual mode setting so that the radiator can be controlled manually using the on unit dial. The Ultrad range and the soon to be launched Geo-Dry, use the Haverland App and Smartbox. . The RCTT Connect (RCTTC) range uses a direct to wi-fi communication. It uses the same Haverland app but not via the Smartbox. It will only connect to wi-fi at 2.4Ghz not 5Ghz so some router settings might need changing if a “blended” network such as comes with a Vodafone router. I suggest pointing your landlord in the direction of either the Ultrad or the Geo-Dry. Good Luck.
Working with RCTT Connect!
Using same configuration with device_id of the radiator
FYI, I finally spent some time looking into the power sensor issue, and noticed that there is a ‘duty’ field that (I’m guessing) represents the duty cycle of the radiator as a percentage, possibly since the last update. If I calculate power usage that way on historical data, it tracks the usage shown in the app pretty closely.
I plan to reimplement the power sensor using the above scheme soon, and then finally release a 2.0 version of the integration. I’d be keen for people to test it when I have a beta version ready.
Hope it’s ok to ask a question from a non-developer but keen learner trying to make the right decisions.
Will the Haverland RCTT work with Home Assistant ok and no Hub required? I see @carlituxman has this working I’m wondering if it’s still ok of if others have it working ok?
I doubt I can set this up myself but i might be able to get a dev friend to help me (unless anyone would be willing to do a wee contract for me here?!)
I’m looking to replace radiators in 3 self catering cabins and get the radiators online. I’d like to add Shelly Window detectors so I can have a way to shut down the heating when folk inevitably leave windows open or doors when sat on balcony. I know they have window detection but the rointe’s i have (not wifi) promise they have this but it most definitely has never worked on any testing I have done.
I’m also guarded about using hubs (ULTRARAD or other haverland ranges). Does direct to WiFi lessen the risk of loosing support in future years if it’s possible to connect to Home Assistant? (Thanks to the great work of the developers here who can do this)
Hope it’s ok to ask here, apologies in advance for beginner questions, hugely grateful for any thoughts/experience with the haverlands.
I don’t have any experience myself with Haverlands. I know that various people have reported successfully using the integration with different Haverland models like ECO-RAD, ULTRAD and Wi-x.
I don’t think a direct to WiFi radiator would help lessen the risk of obsolescence, since this integration is still interacting with a third-party cloud service, unless those radiators have some local control features the others do not (it’d be interesting to know if that’s the case).
@carlituxman it’d be interesting to see the output of smartbox nodes, smartbox setup and smartbox status for your radiators to see if they report anything differently.
