I’ve read that the built in db has been improved but I’ve been running mariadb since about 2019 or so, and have not wanted to change over.
Now if only they would add the ability to import data to the energy dashboard from outside sources such as a csv file. My energy dashboard is what I lost that really irritates me. Although I still have all the same data from enphasesl. Everything else gets purged after 2 weeks so meh.
Please report back when you do!
It’s been on my to-do list for a couple of versions now and I’m not sure where to even start (aside from pulling the plug on MariaDB and starting the database again from scratch).
What is the fastest and easiest way to get ssl/https working without adding unwanted addons for vpn or other services?
The mic issue is an absolute pain and forces https now.
Fastest and easiest?
Nabu Casa.
And free. I do not want external services for a purely local system.
I use the Duck DNS add on,
but probaly you consider this as unwanted?
you can also use “let’s encrypt” add on, but I think you have to register a domain then?
and also, another add-on, but, you need to sign your certificate somehow.
Yes, DuckDNS is an addon with the side effect of ssl but not the intended use of creating it.
Maybe with the move to a forced ssl connection a dedicated addon would be better?
It does seem odd to include energy data in the original HA database which was designed for short-term tracking of events and state changes. Good database design would seem to suggest that long-term data would be stored separately.
My solution (before the energy data were even introduced) has been to store anything I wanted long-term in .csv files, which can be imported into any tool on any platform for storage and analysis. I do lose out on the pretty graphs, but generally I want to produce my own custom graphs anyway.
Imagine coming to a forum where people help for FREE and act like an entitled child. Please delete HA and you will NEVER have to deal with it again.
You are now acting like this. The person emotionally expressed his feelings about not properly tested SW.
Same. stuck on 4.6 until this works or we learn how to change a setting since majority of my HA use is with this integration 
error log as follows:
Error connecting to ElkM1 ([SSL: UNSAFE_LEGACY_RENEGOTIATION_DISABLED] unsafe legacy renegotiation disabled (_ssl.c:1007)). Retrying in 2 seconds
9:15:48 AM – (WARNING) runner.py - message first occurred at 9:12:44 AM and shows up 46 times
ElkM1 at elks://192.168.30.32 disconnecting
9:15:44 AM – (WARNING) components/elkm1/__init__.py - message first occurred at 9:13:04 AM and shows up 5 times
edit: seems to be maybe possibly related python 3.10/SSL with workaround (which I don’t understand myself yet) and permanent “fix” for the devs here: Roomba no longer detected · Issue #82775 · home-assistant/core · GitHub
That’s how long term stats are stored 
Since 2023.5, the zwave_me integration does not report data from sensors: “This entity is no longer being provided by the zwave_me integration. If the entity is no longer in use, delete it in settings.”
I use Fibaro door/window sensors, they do, indeed, report the open/closed part, but no temperature or other data. Also, i have a Aeotec plug that used to report AC voltage/power consumption. Only the on/off part is available now in Home Assistant.
All that data is available in zwave, so it must be the integration that broke with the last update.
Personally I have an Ecovacs Deebot T8. While it’s a hassle, and a bit cumbersome, I have setup separate scripts for each room, then switch templates for each script and then exposed that switch template to Google w/ aliases. Guessing there’s an easier way - but I haven’t yet seen how to (like IFTTT used to be able to do) pass ‘variables’ or raw text into HA from Google.
The ideal (for me) would be to ‘Vacuum the %’ and then parse this in HA based on the ‘vacuum the’ trigger / text match - with a big % if / elseif % statement to decipher which room to clean…
Hoping year of the voice makes this easier at some point going forward!
you can also use the template vacuum integration, and create a vacuum entity for each room (untill room support is official)
This field is now required. I opened a PR to fix the docs Require a list of entity ids when fetching history by bdraco · Pull Request #90992 · home-assistant/core · GitHub. Checked the linked PR for the backstory.
After the update, I got a message saying that I didn’t need the Workday config on YAML. I checked the new Workday Integration and it seemed to be working fine, with all the settings seemingly imported.
Canada, Ontario
I then decided to remove the Workday config from YAML and after restarting, the Workday integration does not work, I get the following on the logs:
Logger: homeassistant.setup
Source: setup.py:348
First occurred: 7:15:32 AM (1 occurrences)
Last logged: 7:15:32 AM
Unable to prepare setup for platform workday.binary_sensor: Platform not found (cannot import name 'DateLike' from 'holidays' (/usr/local/lib/python3.10/site-packages/holidays/__init__.py)).
I removed the Workday integration, I forgot to copy the error it was displaying but it was a 500 Internal server error.
I then attempted to add it again, selected “Canada” and pressed Submit, and this cryptic message is displayed:
I went to the logs and saw this new entry:
Logger: aiohttp.server
Source: components/workday/config_flow.py:56
First occurred: 7:18:59 AM (5 occurrences)
Last logged: 11:10:52 AM
Error handling request
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, 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 85, 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 80, in ban_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
return await handler(request)
File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
result = await result
File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 218, in post
return await super().post(request)
File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
result = await method(view, request, data, *args, **kwargs)
File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
result = await self._flow_mgr.async_init(
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 243, in async_init
result = await self._async_handle_step(flow, flow.init_step, data)
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/workday/config_flow.py", line 284, in async_step_init
schema: vol.Schema = await self.hass.async_add_executor_job(
File "/usr/local/lib/python3.10/concurrent/futures/thread.py", line 58, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/src/homeassistant/homeassistant/components/workday/config_flow.py", line 56, in add_province_to_schema
if not obj_holidays.subdivisions:
AttributeError: 'CA' object has no attribute 'subdivisions'
It seems the integration is failing to display the list of subdivisions for me to select, thus failing.
Cloudflared tunnel addon is free, you do need a domain set to cloudflare nameservers though.
I’m hoping for a solution coming from Debian because I really don’t want to mess up anything else.
But isn’t stuff like this NOT happening the entire reason we use Debian in the first place? I’m only using Debian because it’s supported by HA but in all fairness, Ubuntu server worked much better for me.
Hello,
If I understand correctly, now entities which have no unique ID cannot be exposed to voice assistants so it includes Google Assistant?
If it is the case it is really unfortunate.
I expose some Broadlink switches (so configured in YAML) and no unique ID can be set for Broadlink integration. And setting a template switch or helper to use another switch is not something I call a clean solution.
Ironically, this pull request I opened last October would have avoided that case but it is locked because of status of YAML integration even if some of these have been updated to allow unique ID: