Do they appear in your LMS web ui? (ie independently of HA)
Hi, is there already a schedule for the 2024.10.3 release, in which hopefully SolarLOG ist working correctly again?
Normally there is a point release on a weekly basis and if you look at GitHub you can check the PRs that will be included in releases so just have a look and youāll know
@nickrout - yes they appear in the LMS UI.
My LMS server is old now and hasnāt been updated for years. It did show me that updates were available but that has gone now. It appears to be looking at http://downloads.slimdevices.com/ for updates but that is now a defunct link.
My LMS version is - Logitech Media Server Version: 7.9.0 - 1477086729 @ Mon Oct 31 04:38:27 UTC 2016
So I suspect the new version of the integration that comes with 2024.10.x isnāt backwards compatible with my LMS.
Any thoughts on this?
Looks like I will have to rebuild my LMS platform.
8.5.2 here. I use docker for it, makes it easier.
I guess thatās the latest version from the v7 branch, thatās probably why you get no updates.
Here with 8.5.3 on Core 2024.10.0 and using only Squeezelite, everything works fine.
I know that jumping (immediately) on every new release of SW can become a sport/hobby and sometimes itās good to wait a little.
OTOH: not updating for a long time also can become a problem.
You can just update to a new 8.x version. No need to rebuild
Thanks to all who took the trouble to help.
I run LMS inside a Linux wrapper called Max2Play on a Pi 3. It provides easy setup of SAMBA shares, mounts of NAS drives and DLNA for vids/audio amongst other things, as well as the Squeezebox server.
I couldnāt upgrade my LMS from within the LMS instance running on Max2Play Pi. However I could update the Max2Play instance.
When the update finished I went back to the Squeezebox page within Max2Play and hey presto I could see LMS 8.5.2 as well as the nightly 8.5.3.
I upgraded to 8.5.2 and now all is well
4 Likes
Iām getting a āSSL is configured without an external URL or internal URLā error when Iāve upgraded to 2024.10.1 (and 10.2).
I am able to access Home Assistant locally but can no longer able access Home Assistant remotely using duckdns.
http configuration from configuration.yaml:
http:
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: True
login_attempts_threshold: 5
ā¦ and Iām also unable to configure the Home Assistant URL
Under homeassistant: in your configuration.yaml file you need to provide an external and internal url. See
https://www.home-assistant.io/integrations/homeassistant/#external_url
1 Like
Did you find a solution to this as I have the same issue? Iāve reboot HA and refreshed browsers etc but none of the custom cards have reappeared and new ones donāt show up either.
Take the URL (resource part) for one card from your resources file, append it to your base URL and see if your browser shows you the JS file.
Long story short, I got into the file system to see where things actually were located. Iām now confused because some of the custom cards are stored in \config\www\community, and some are stored in \config\www. Whatās really confusing me though is that the config file refers to hacsfiles in the resource path for some cards and I donāt have that folder anywhere. Is it a system variable that points to the \config\www folder or similar?
Either way, I have found all my custom cards in those two folders but HA doesnāt want to see them anymore after the upgrade. Also I didnāt have to add path statements to all the cards before so where does HA get the details from if not the config file?
Did you install everything you have via HACS?
Perhaps what you see in www was installed manually.
hacsfiles is really just an alias for www/community.
Have you tried this?
For example:
/hacsfiles/button-card/button-card.js => http://homeassistant.local:8123/local/community/button-card/button-card.js
Also, open the browserās dev tools and check for errors on the JS console.
Edit: Reading the ESP Logs for the emporiavue devices shows a million
[17:50:30][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
[17:50:30][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
[17:50:30][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
[17:50:30][E][emporia_vue:048]: Failed to read from sensor due to I2C error 3
which lead me to the following site with a workaround that seems to be working for me. Modifying the frequency and timeout of the i2c section.
Good morning, I was out of town from 10/5 and just installed the latest version of HA and noticed that this broke my energy dashboard (and power monitoring). Iām using emporia vue devices in my circuit panels. And what I am seeing is a bunch of āunknownā and no energy being tracked. If I click into a sensor it seems to be getting data.
Clicking on one of the unknown sensors (my HVAC). (Correction, this stops yesterday after updating. no data since then)
settings:
Sharing your idea saved my day. Thank you!
May I ask what theme you are using? thanks
After upgrading core to 10.3 today (from 10.2) I lost my decora_wifi and tasmota intergrations:
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 183, in async_setup_entry
raise ValueError(
ValueError: Config entry Tasmota (01JAGMFBAPQ3XZW58SY90XET4V) for tasmota.switch has already been setup!
2024-10-18 18:41:36.058 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Tasmota for tasmota
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 594, in async_setup
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tasmota/__init__.py", line 75, in async_setup_entry
await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2160, in async_forward_entry_setups
await self._async_forward_entry_setups_locked(entry, platforms)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2171, in _async_forward_entry_setups_locked
await asyncio.gather(
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 2236, in _async_forward_entry_setup
result = await async_setup_component(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/setup.py", line 159, in async_setup_component
return await existing_setup_future
^^^^^^^^^^^^^^^^^^^^^^^^^^^
OSError: [Errno 8] Exec format error: 'uv'
Iām not sure what to do about that exec format error.
This is on Windows 11 running in Vbox version 7.1.4 r165100
Core 2024.10.3
Supervisor 2024.10.2
Operating System 13.2
Frontend 20241002.3
HA info show support for amd64 and i386 arch.
1 Like
Axel,
I upgraded from 2024.9 to 2024.10.3 and as a result SolarLog stopped updating (but no errors, no warnings). Is this the problem you are experiencing?
I reloaded the integration and after that it was ok. Restarted Home Assistant and still OK.
For those who are on MacOS with HA Core and have problems with uv ānot foundā : I had a ~/Library/LaunchAgents/org.homeassistant.plist.
I placed ā/opt/homebrew/bin:ā at the beginning of EnvironmentVariables node in the āstringā part (where are the paths).