Isn’t it heating season in the bottom half of the world right now?
Same here, using the pi4 8g with a ssd and it is rock stable. Have 27 container running and it runs just fine. The ssd is a must!
generic_thermostat stuck in celsius after update
Then that is a Supervised Install, and indeed, you forgot to follow instructions to install it on Debian 11.
There are four supported installation methods:
HA OS
Supervised
Container
Venv.
None of them are called “Docker”, although of course the first three do use docker. When you say “I did try Docker…on ubuntu” you confuse the issue because that could be a bad attempt at Supervised or it could be Container.
Sure is, you should see out my window, and now there is a slip on the road and I have to go the long way to town!
You will be brought into the modern age of units!
They tried to push metric when I was in school in the 60’s and 70’s, ever since we’ve been stuck in a dual units confusing world. At 66 I’d be happy now if the change would wait till I’m gone I’m stuck n my ways now.
Further to this, it appears that any platform: homeassistant
sensors aren’t even appearing in Home Assistant post-upgrade. Something wrong or changed with the native API calls?
I didn’t want to use Debian. I had been using Ubuntu for years and didn’t want to switch. It was just much easier to use the X-86 image.
There was a fix in .6 for not catching bad syntax but this doesn’t look obvious bad syntax, but its hard to tell without seeing the actual yaml.
It looks like something is returning a list
as the name instead of a string. Please open a github issue with your yaml config that isn’t working. Thanks
Thanks
I will try to load .6 and check if I still get error.
Open in core
This… I have the history.yaml and recorder.yaml set up to show me what i wanted to see in the history pannel. the way it is now with selecting filters i get a bunch of unknown bars from stuff i dont have recorded or i have a full page of active filters i have to scroll past to see any info and still cant get it to show everything i had it showing before. Please give us an option to have it show what the history.yaml says to show
Hi,
Does anyone know who normally maintains the code for the haveibeenpwned integration (the one which uses an API key so you can check a long list of email addresses)? I have opened a bug-ticket on github for this integration as it stopped working with the upgrade to 2022.07.x, but the git-bot does not flag any maintainer.
Together with this haveibeenpwned integration failing to work the following integration/ sensor also stopped working with 2022.07.x:
- Luftdaten
There is a some info in the logs, which, as far as my -admittedly very limited- insights hint at, are linked to something having to do with http…
I am more than willing to test, try out new stuff, etc. to help squash this one.
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/anyio/streams/tls.py", line 130, in _call_sslobject_method
result = func(*args)
File "/usr/local/lib/python3.10/ssl.py", line 917, in read
v = self._sslobj.read(len)
ssl.SSLWantReadError: The operation did not complete (read) (_ssl.c:2548)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 33, in read
return await self._stream.receive(max_bytes=max_bytes)
File "/usr/local/lib/python3.10/site-packages/anyio/streams/tls.py", line 195, in receive
data = await self._call_sslobject_method(self._ssl_object.read, max_bytes)
File "/usr/local/lib/python3.10/site-packages/anyio/streams/tls.py", line 137, in _call_sslobject_method
data = await self.transport_stream.receive()
File "/usr/local/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 1265, in receive
await self._protocol.read_event.wait()
File "/usr/local/lib/python3.10/asyncio/locks.py", line 214, in wait
await fut
asyncio.exceptions.CancelledError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpcore/_exceptions.py", line 8, in map_exceptions
yield
File "/usr/local/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 31, in read
with anyio.fail_after(timeout):
File "/usr/local/lib/python3.10/site-packages/anyio/_core/_tasks.py", line 118, in __exit__
raise TimeoutError
TimeoutError
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 60, in map_httpcore_exceptions
yield
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 353, in handle_async_request
resp = await self._pool.handle_async_request(req)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 253, in handle_async_request
raise exc
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection_pool.py", line 237, in handle_async_request
response = await connection.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/connection.py", line 90, in handle_async_request
return await self._connection.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http11.py", line 105, in handle_async_request
raise exc
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http11.py", line 84, in handle_async_request
) = await self._receive_response_headers(**kwargs)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http11.py", line 148, in _receive_response_headers
event = await self._receive_event(timeout=timeout)
File "/usr/local/lib/python3.10/site-packages/httpcore/_async/http11.py", line 177, in _receive_event
data = await self._network_stream.read(
File "/usr/local/lib/python3.10/site-packages/httpcore/backends/asyncio.py", line 30, in read
with map_exceptions(exc_map):
File "/usr/local/lib/python3.10/contextlib.py", line 153, in __exit__
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.10/site-packages/httpcore/_exceptions.py", line 12, in map_exceptions
raise to_exc(exc)
httpcore.ReadTimeout
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 205, in _async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 164, in _async_update_data
return await self.update_method()
File "/usr/src/homeassistant/homeassistant/components/luftdaten/__init__.py", line 43, in async_update
await sensor_community.get_data()
File "/usr/local/lib/python3.10/site-packages/luftdaten/__init__.py", line 29, in get_data
response = await client.get(str(url))
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1751, in get
return await self.request(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1527, in request
return await self.send(request, auth=auth, follow_redirects=follow_redirects)
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1614, in send
response = await self._send_handling_auth(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1642, in _send_handling_auth
response = await self._send_handling_redirects(
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1679, in _send_handling_redirects
response = await self._send_single_request(request)
File "/usr/local/lib/python3.10/site-packages/httpx/_client.py", line 1716, in _send_single_request
response = await transport.handle_async_request(request)
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 352, in handle_async_request
with map_httpcore_exceptions():
File "/usr/local/lib/python3.10/contextlib.py", line 153, in __exit__
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.10/site-packages/httpx/_transports/default.py", line 77, in map_httpcore_exceptions
raise mapped_exc(message) from exc
httpx.ReadTimeout
Hello everyone,
I’ve noticed for a few days that my database size was increasing. I checked and I can find many new entities stored in database that were not recorded previously.
I have many entities automatically created that I have renamed with a suffix “_full”. For instance “sensor.pir_hue_1_battery_full” is the battery entity automatically created by Zigbee2MQTT for a Hue PIR Sensor. I’ve done this for many entities that are too frequently updated or with too many attributes for my needs. So I’ve created using templates many new entities called for instance “sensor.pir_hue_1_battery”. This is the entitity I use and want to record. It contains only the battery percentage and that’s it, way more efficient than use and record the original battery entity and sufficient for my needs.
The relevant part of my recorder configuration :
recorder:
purge_keep_days: 11
exclude:
entity_globs:
- sensor.*_full
include:
entity_globs:
- sensor.*battery
This used to work very well for my needs.
My entities “sensor.pir_hue_1_battery” were correclty recorded, and the original entities named “sensor.pir_hue_1_battery_full” were not. Perfect.
However this does not work like this anymore. Now, both are recorded. And when I look at the Recorder configuration filter help (Recorder - Home Assistant), it seems pretty logical and expected.
Any idea how I could easily get the former behaviour still using entity_globs filter and if possible without having to rename all my entities ?
Thanks,
David
Same from here, using EQ3 & HA since 3 years in a satisfactory way
Seems like my SIA integration (I’m using it together with AJAX) is not working after updating to 2022.7.6…
I am unable to update to any version of 2022.7.x from 2022.6.7 mac os mojave python 3.9
I am getting connection refused all the time.
any help please its driving me crazy
Logs? How are you upgrading?