Is anybody else having the issue that long-term statistics / history seem to have been reset/deleted? E.g. if Ido a ‘compare’ in the Energy dashboard I only see today’s data. It worked before I upgraded to 2022.11.
Maybe in the future.
We kept that out of scope for this iteration. Initially, it isn’t expected for water to be widely used. The amount of available hardware and integrations that can support it is really low as well at this point.
Who knows what the future has in stock 
1 Like
there’s another thing I now notice on stats:
my processor usages has yet again gone up to an average of 11.27%. 2 release ago that was 6/7. Also mem is still creeping up, now to round 22%. huge jumps, and no release, really odd.
no idea what is causing this, but I sincerely suspect the new BT proxies and the devices on those proxies to cause this. It has been the only fundamental change in my config…
So HHCC didn’t make it?
Edit:
No replies, so I’m rephrasing the question. Passive BLE Integration is currently being integrated to Home Assistant. I’m using Tilt Hydrometer (million thanks again @Ernst for this), HHCC plant monitors and RuuviTags. Passive BLE GitHub page says that “Expected in November release, Oral-B and HHCC”. I see Oral-B, but not HHCC. RuuviTag seems to be still in development.
Hi,
I am also having the same problems as Cataseven. Exactly the same errors in my log files, regarding ssdp and default_config
anyone an idea how to solve this?
UPDATE: Problem solved here by putting this into configuration.yaml:
homeassistant:
internal_url: "https://<MYHOST.MYDOMAIN>:8123
Did I perhaps miss a breaking change somewhere (in the past)?
Since this update I receive the following error during rest setup:
Unable to prepare setup for platform rest.sensor: Unable to set up component.
→ Resource not set for RestData
2022-11-03 10:36:02.024 ERROR (MainThread) [homeassistant.setup] Error during setup of component rest
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 235, in _async_setup_component
result = await task
File "/usr/src/homeassistant/homeassistant/components/rest/__init__.py", line 77, in async_setup
return await _async_process_config(hass, config)
File "/usr/src/homeassistant/homeassistant/components/rest/__init__.py", line 97, in _async_process_config
rest = create_rest_data_from_config(hass, conf)
File "/usr/src/homeassistant/homeassistant/components/rest/__init__.py", line 185, in create_rest_data_from_config
raise HomeAssistantError("Resource not set for RestData")
homeassistant.exceptions.HomeAssistantError: Resource not set for RestData
Nope, rest has always required a resource. Make a new thread and post your yaml & error.
Exactly the same experience here. Those cards are not loading faster for me at all. Using MariaDB, 14 days of history in the recorder.
2 Likes
Add a width: *% value to style and then you’ll have to reposition everything. I have no idea what has changed.
1 Like
Tile: very interesting card , it should be nice to show attribute of an entity in it .
like
type: tile
entity: sensor.sensor
type : attribute
attribute: name
i agree completely, i would also like to have the previous history display back.
7 Likes
Yeah I was just trying to debug an issue with an intermittently high sensor but the more info pop up was totally useless. I had to use the history panel.
Looks like I’ll be disabling LTS for everything, which also means removing the energy panel (I mostly use my own anyway).
5 Likes
Thank you for submitting this issue. My floorplan is empty 
Thanks. Will wait for a fix if there’ll be one… Otherwise I’ll do that 
cant you use browser-mod to use a history card popup on more-info?
I can see it being useful to detect water leaks, monitor device efficiency. The reality is that to buy the hardware and plumb the device into the home would be costly and labour intensive.
it was requested many many times in the wth and feature requests - so, why not having it?
you don’t need to use it, if you don’t want to buy the hardware - but many others already had the hardware up and running - and the only place where it was missing - was the dashboard
1 Like
The changes to the ZAMG integration should be listed as breaking changes, for
a) some of the monitored_conditions are not recognized anymore
Invalid config for [sensor.zamg]: value must be one of ['dewpoint', 'dewpoint_average', 'humidity', 'precipitation', 'pressure', 'pressure_sealevel', 'snow', 'sun_last_10min', 'temperature', 'temperature_average', 'wind_bearing', 'wind_max_bearing', 'wind_max_speed', 'wind_speed'] @ data['monitored_conditions'][7]. Got 'sun_last_hour'. (See ?, line ?).
b) some of the entity_ids changed (most likely because the friendly names of the sensor family (the “suffix” for all monitored conditions) cannot be overridden anymore)
For example:
- platform: zamg
station_id: 11389
name: St. Pölten/Landhaus # The name fetched from the Server is "ST.POELTEN LANDHAUS"
...
resulted in entity_ids of sensor.st_polten_landhaus_*, instead of sensor.st_poelten_landhaus_* (o→oe).
The dashboard now throws this massive chain of capital letters at you: “ST.POELTEN LANDHAUS dewpoint”, as one example.
And last but not least: For the first time while using this integration (on several HA instances and for more than a year now) I observe a lot of failed data fetches, resulting in unknown sensor states – is it blocked due to too many requests? (I fetch data from 2 stations)
Some log examples:
Logger: homeassistant.components.zamg
Source: helpers/update_coordinator.py:151
Integration: Zentralanstalt für Meteorologie und Geodynamik (ZAMG) (documentation, issues)
First occurred: 11:40:29 (2 occurrences)
Last logged: 11:51:03
Timeout fetching zamg data
Logger: homeassistant.components.zamg
Source: helpers/update_coordinator.py:151
Integration: Zentralanstalt für Meteorologie und Geodynamik (ZAMG) (documentation, issues)
First occurred: 10:15:12 (5 occurrences)
Last logged: 11:45:52
Timeout fetching zamg data
Error requesting zamg data: Cannot connect to host dataset.api.hub.zamg.ac.at:443 ssl:default [Connect call failed ('138.22.160.100', 443)]
Has anyone had issues with authentication to Jandy / Iaqualink? I note there was an upgrade to the integration in the full change log. Restored back to 2022.10.5 all good. Upgraded my test pi to 2022.11 and could not get it to authenticate either
2022-11-03 22:25:44.954 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py”, line 435, in _handle_request
resp = await request_handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py”, line 504, in _handle
resp = await handler(request)
File “/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py”, line 117, in impl
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/security_filter.py”, line 60, in security_filter_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/forwarded.py”, line 100, in forwarded_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/request_context.py”, line 28, in request_context_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/ban.py”, line 82, in ban_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/auth.py”, line 236, in auth_middleware
return await handler(request)
File “/usr/src/homeassistant/homeassistant/components/http/view.py”, line 136, in handle
result = await result
File “/usr/src/homeassistant/homeassistant/components/config/config_entries.py”, line 180, in post
return await super().post(request, flow_id)
File “/usr/src/homeassistant/homeassistant/components/http/data_validator.py”, line 73, in wrapper
result = await method(view, request, data, *args, **kwargs)
File “/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py”, line 110, in post
result = await self._flow_mgr.async_configure(flow_id, data)
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 280, in async_configure
result = await self._async_handle_step(
File “/usr/src/homeassistant/homeassistant/data_entry_flow.py”, line 367, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File “/usr/src/homeassistant/homeassistant/components/iaqualink/config_flow.py”, line 41, in async_step_user
async with AqualinkClient(username, password):
File “/usr/local/lib/python3.10/site-packages/iaqualink/client.py”, line 72, in aenter
await self.login()
File “/usr/local/lib/python3.10/site-packages/iaqualink/client.py”, line 126, in login
r = await self._send_login_request()
File “/usr/local/lib/python3.10/site-packages/iaqualink/client.py”, line 121, in _send_login_request
return await self.send_request(
File “/usr/local/lib/python3.10/site-packages/iaqualink/client.py”, line 92, in send_request
self._client = httpx.AsyncClient(
File “/usr/local/lib/python3.10/site-packages/httpx/_client.py”, line 1386, in init
raise ImportError(
ImportError: Using http2=True, but the ‘h2’ package is not installed. Make sure to install httpx using pip install httpx[http2].
1 Like