2024.9: Sections go BIG

Blog
226

does the recorder still hang due to the daily purge?

227

It never has for most of us.

228

I do have an actual job! - After much wrangling, removing the integration and configuration, re-adding and faffing I managed to get the full log. So I hope you stop moaning on about it. But this will just prove my point that nobody is maintaining the Hive integration. Posted on the original issue report - but nobody on there asked for more information or acknowledged they are looking at it at all, despite others reporting it…… for your enjoyment…

Logger: homeassistant.components.websocket_api.http.connection
Source: components/websocket_api/commands.py:245
integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 15:48:29 (2 occurrences)
Last logged: 15:50:24

[140426593200464] Unexpected exception

Traceback (most recent call last):

File “/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py”, line 245, in handle_call_service

response = await hass.services.async_call(

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

File “/usr/src/homeassistant/homeassistant/core.py”, line 2761, in async_call

response_data = await coro

^^^^^^^^^^

File “/usr/src/homeassistant/homeassistant/core.py”, line 2804, in _execute_service

return await target(service_call)

^^^^^^^^^^^^^^^^^^^^^^^^^^

File “/usr/src/homeassistant/homeassistant/helpers/service.py”, line 978, in entity_service_call

raise HomeAssistantError(

homeassistant.exceptions.HomeAssistantError: Entity water_heater.hall_thermostat does not support this service.

229

Still no sign of a response to this

with logging turned up on hive

What is it about you that you won’t respond when other users who are just trying to help? I wonder why I bother sometimes.

You may need to trawl through the changes that have been made to the hive integrations in the last couple of weeks or so. You wil undoubtedly have seen this in your searches.

A lot of changes in the hive integration on 18 Sept 2024. It may have something to do with it?

230

I already posted on the issue thread that I suspect that is the problem. If you’re simply going to complain then don’t bother. It is NOT my job, my responsibility or anything I’ll do because I won’t get paid, to trawl through the changes. I do enough of this in my day job for which I do get paid. As I said and keep saying - this is the problem with OSS that has accessible or visible control.

231

That error originates outside HA. Do you use NodeRed? Something from outside HA is using an action that’s pointed at your water heater provided by hive. The water heater does not support the action being called, therefore you get that error. The only way to fix that is to fix the websocket call. I.e. Fix whatever is making the action.

232

No one gets paid. No one pays. I personally don’t give a flying thingy if your hive integration works. I have wasted quite a lot of time trying to get in a position where I can help you, but you are resistant to advice. So how about you go and use a product that you pay for, and can justify being “that guy” if it doesn’t work, because you chose the wrong place to be “that guy”. So, begone, you have exhausted my supply of thingies to give.

6 Likes
233

You have a strange way asking for help and you seem to miss that you are getting it from people who do this for free, in their free time.
Even though you have an actual job, you seem to find the time though to keep dragging for not replying to the questions that might help you but still stay in the conversation…

In your head this might be the normal way, I’m quite sure that there are A LOT of other opinions.
But hey, you were the one that needed help.

4 Likes
234

Nope - don’t use node red. The water heater supports the action in 2024.8.3 but not 2024.9.x The only thing making the call is using the entity in HA. It’s not even via an automation.

235

What is making the call? The frontend uses websockets. What card are you using?

236

@bushcraftytim raises an issue over hive. It is legit.

  • The hive water_heater accepted the water_heater.turn_on action until 2024.9. Now it doesn’t.

  • water_heater docs say that water_heater supports turn_on, with the caveat that not all implementations support every action

Available actions: water_heater.set_temperature, water_heater.turn_away_mode_on, water_heater.turn_away_mode_off, water_heater.set_operation_mode, water_heater.turn_on, water_heater.turn_off

Tip

Not all water heater actions may be available for your platform. Be sure to check the available actions Home Assistant has enabled by checking Developer Tools > Actions.

  • As an aside, this is what the hive integration docs say about the hive

WATER HEATER

The hive water heater platform integrates your Hive hot water into Home Assistant, enabling control of setting the mode.

7 Likes
237

Excellent post. My thanks to you. I suppose if you are “at the coal face” you can be a bit too severe and perhaps I was. Apologies to anyone upset by anything I did. I’m not too big to admit I wasn’t perfect.

I did exactly what you said last night before I saw this post. Here is the scripts I used to control the water heater:

To Turn On:

alias: Turn on Gas Water Heater
sequence:
  - action: water_heater.set_operation_mode
    data:
      operation_mode: "on"
    target:
      entity_id: water_heater.hall_thermostat
description: ""
icon: mdi:water-boiler

I’m guessing that anyone can fill in the entity names and such. Turning Off is a matter of replacing “on” with “off”. If you want to toggle do a script the runs turn on if it’s off and vice versa. This can then be added to a button to act as an on-off toggle.

Works perfectly.

My thanks to you again @nickrout … virtual beer on me for you.

3 Likes
238

We seemed to get past the testiness. My apologies too if I got grumpy.

Your problem interested me.

3 Likes