Can we get a circular thermostat-like control for any old input.number
entity? I have a custom input.number
for the volume on my receiver that matches the dB level on its front panel (and not simply from 0 - 100%), and would love to be able to use that style of circular control rather than the default slider.
Everything is working great after the upgrade except my Bluetooth module on my CM4 Lite. Detects a new hci0, but if I delete all the BT and rediscover it’s not setting up correctly.
This is on a Home Assistant Yellow with a 4GB CM4 Lite (BT and WiFi module).
ok …
On the other hand the message about the new feature made me assuming there will be an impact on DB size and need to reconfigure the recorder
If you have manually modified the days to keep before purging recorder on your system, consider removing that customization. With the long-term statistics and new feature, you most likely don’t need it anymore, resulting in a smaller database and, thus, faster and smaller backups.
I’m fighting with a huge database and appreciate any help
Yes, it’s basically telling you “If you used a larger purge_keep_days, you might want to reconsider this because history now shows you everything that’s stored forever”. Instead of you holding everything forever in your regular history.
Hello,
i’ve mentioned this in beta discord channel :
calendar.get_events
is not documented here
can this be fixed as i have no idea how to migrate ?
EDIT : i’ve realised that i can actually use developer tools and see the response to understand the new format (and since both old and new services are available, the format changes are easy to spot !)
OK, fixed the Bluetooth. Had to delete the Bluetooth HCI0 and any BLE devices. Restarted Home Assistant Yellow and then was able to configure properly without error.
I’m not sure if this is a change with 2023.12 or the recent HAOS 11.2 upgrade that was just last week. Perhaps my reboot after 2023.12 realized the change in HAOS 11.2? I do see that there was a change related to the HA Yellow UART settings in that release.
The new thermostat card is great, except the actual temperature is now very tiny and very hard to find at a glance. Is there a way to make it more prominent?
You can set a default dashboard for a device by tapping on your avatar in the menu on the left. This setting is per device.
I’m just reading the release notes and discussion under the breaking change for ther removal of switch platform from Harmony integration. And I must say that I’m astonished that comments from people who didn’t like the change have been left without even answering and the change went through. Not very community…
This release has 773 changes listed in its changelog.
This is great, in my view, but even for me, as someone that always try to review all the changes, it’s becoming quite hard to fully process this amount of information by reading.
To simplify things and save myself some time, I’ve quickly hacked some commands together to reduce this list to what’s relevant to my config.
Read more here if you’re interested: Processing a Home Assistant new release changelog.
EDIT: As I’m going through my list, I just picked up e.g. on this change that might affect me: Remove rest api service call timeout by MartinHjelmare · Pull Request #104709 · home-assistant/core (github.com).
This is why I’m glad I had template switches before the switch platform was added. What has been given has been taken away. But you can’t take away my switch templates!
@bdraco or any other ESPHome developer:
pls implement the ability to play from HTTPS (now only works with HTTP) source with ESPHome built-in Media Player (Radio, TTS, other)
Yeah, actually I was only using it in two cases in one automation, so was easy to replacy with select
. It is more about how such change is managed.
I’m using extensively template switches as well partially because I’ve done it before they were added to the integration and partially because I have a few which have some additional complexity which was not possible (or hard) to resolve on Harmony side (e.g. playing a preset or selecting a source which was easier in HA).
this is wonderful, i just got an alert since i’m using a deprecated function and to update to a function that isn’t even documented
Just upgraded to 2023.12, and my dashboard is super slow, and uses 100% cpu time on my pc (macOS + Safari), and it also seems to be happening on my iphone’s HA app. even scrolling down the page is barely functioning. Anyone else having this issue ?
I think it’s a bad idea to remove them. And why… It’s not take all resources of HA to function and those switches are very easy to use.
I have to rebuild lots of automations when they gonna remove them…
Hi. Thanks for new version i t looks good. But for thermostat… good feature will be add to user can add own label for mode… like for mode heat i want add label DAY for coold i want add label NIGHT. I want this because i have created thermostat climate entity by MQTT from my Vaillant boiler… and my Vaillant has manufacturer mode auto, day, night and off… i want clone it to HA.
People using the Thermal Comfort integration or the Skoda Connect integration may want to wait a bit - both stopped working after the update for me.
This core update is failing for me. Can somebody throw me a bone as to what the log is showing
`23-12-06 15:48:55 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
resp = await request_handler(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 543, in _handle
resp = await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 114, in impl
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 186, in block_bad_requests
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 202, in system_validation
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 269, in token_validation
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/middleware/security.py", line 280, in core_proxy
return await handler(request)
^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/utils.py", line 62, in wrap_api
answer = await method(api, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/homeassistant.py", line 93, in options
body = await api_validate(SCHEMA_OPTIONS, request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/supervisor/supervisor/api/utils.py", line 149, in api_validate
data: dict[str, Any] = await request.json(loads=json_loads)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_request.py", line 684, in json
body = await self.text()
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_request.py", line 678, in text
bytes_body = await self.read()
^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/web_request.py", line 663, in read
chunk = await self._payload.readany()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 395, in readany
await self._wait("readany")
File "/usr/local/lib/python3.11/site-packages/aiohttp/streams.py", line 302, in _wait
await waiter
ConnectionResetError: Connection lost
23-12-06 15:49:01 ERROR (MainThread) [supervisor.homeassistant.core] Home Assistant has crashed!
23-12-06 15:49:01 CRITICAL (MainThread) [supervisor.homeassistant.core] HomeAssistant update failed -> rollback!
23-12-06 15:49:01 INFO (MainThread) [supervisor.homeassistant.core] A backup of the logfile is stored in /config/home-assistant-rollback.log`
Just upgraded to 2023.12, I noticed that my nuc temperatures are gone.
CPU, Motherboard. More havening this issue?
I can’t find anything the changelog…
Sensors don’t exist anymore.