Doesn’t work, sensor.next_swatch_time updates its value only when HA starts.
Hi
Having this ewrror. HA is working fine but a message in supervisor appear.
Any information on it?
24-02-09 09:02:07 WARNING (MainThread) [supervisor.homeassistant.websocket] Connection is closed
24-02-09 09:02:07 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 257
I would suggest to remove that 4th sentence, as that is already covered by the third option.
As your 4th option also doesn’t have the oil_heater parameter, it can’t map it to a climate entity.
Basically only one sentence is needed to cover all your 4 sentences:
"[set|change] {oil_heater} [temperature] to {temp_degrees} [degrees]"
Solved this problem of connection is closed ?. In my case rollback was no t executed, and I working fine in 2024.2 but I don´t know whichj warning is this
Same question
Do you have a second instance of evohome setup as custom component?
If yes did you update this also to latest 2024.2 version?
Thx @finity, found it.
It is a bit weird and difficult to find for a regular user tho. It is fine to have it there just in case of an updete but in my opinion this option should be available to set also at the proximity sensor creation time. Imagine creating multiple proximity sensors, we have to now go to every single one, find correct entity just to change unit of measurement, instead of setting it while creating a sensor 
Anyway, it is possible to change it so that’s a good start. Will see if it works later 
Thx again
Also just noticed that even I am home, the direction of travel shows Arrived. Shouldn’t be Stationary or that’s ok when tracking the specific zone and stationary will be showing only when in one place but out of this zone, which kind of make sense?
Restarting HA worked like a charm and then the QR came. Luckily. Thanx for pointing me to that direction. The documentation doesn’t state it.
I think i have the same issue en kovlaca also. all my motion sensors lost there icons and the blinds and awning . It did not happen directly after the update ,but a day later or so.i go back to the 2024.1.6 version and all the icons are back
It’s not an issue. Clear the cache and refresh the page. You may need to manually clear the full cache to get it to work, a simple CTRL+F5 may not do the job.
1 Like
thanks , that worked for me.
@petro i know is not a issue for 99% of the time, my point was if they try to raise a issue they would see the issue already is raised. Being the one I shared the link of, what would had told them the same you also did.
Sometimes looking a little further not hurts
1 Like
No some hardly won’t, because some never use the search, they open multiple issues/topics here in the forum in the weeks after a new release, don’t even do a search in the Release blog, same way it looks in github, in various custom-repos, 3-4 bugs raized for same issue.
BTW , maybe it would be a good idea to “Pin” the release blog, in the top of Forum, for a week or 2 ( with a Commend … " Read commends or search for reported issues " )
1 Like
That is why instead of giving them the most likely solution for their issue, I tried to “educate” them a bit by pointing them in the right direction
In the end we almost all where same when we started our HA journey, only some did learn and evolve also 
But main porpoise of these forums still are to be there for all of us to ask, help and learn 
2 Likes
It doesn’t work either, next_swatch_time is always greater than the current one.
@andrewjswan try the post I’m replying to again, I edited it. I think I know what the problem was.
1 Like
I’ll check now, I was thinking about this trigger option, but I don’t know whether it will update normally, or only once a minute.
- platform: template
value_template: "{{ ((now() - today_at()).total_seconds() * 10) | int % 864 == 0 }}"
Would a device running the companion app not be using the token / logging in constantly in the background when updating sensors?
That will only update once a minute, now() causes templates to update on the minute.
1 Like
More… processor usage…
seems to have happend during the last beta, and all I can think of now is the Proximity integration, because for me nothing else really changed.
I do notice an awful amount of switch.automation_xxx entities on my Hue bridges I never saw before, (and can not be mapped to any automation on the Bridge, I have none) but that wont influence the processor I presume.
this seems to be the average now, around 22-24%
while before it was 10% less.
anyone else seeing this increase in usage?
1 Like