I had this too, long time a go… I think I fixed it by deleting the .db file and reboot
The supervisor contacts a web source and checks for the latest available version.
Hassio always lags behind the release announcement as it takes time to build. Keep in mind the builder may not be in your time zone so a daytime release for you may be overnight for them.
The check is only made a couple of times a day. If one is missed or the timing just isn’t right you may have a delay in getting it to show up.
As for the update to 92 when you are on 93, I think the check must be rather simple and doesn’t check that 93.1 is greater than 92.
Not quite true that only used for legacy UI. The javascript templates enabled in customize.yaml by custom-ui worked in Lovelace nicely until 93.
After a manual update indeed the check did not took place. After the check the prompt Will disappear.
It sounds like the HomeKit integration is starting faster than HA can discover all of your speakers?
Do you have an automation set to disable and delay the HomeKit integration from starting? If not, you should, give it a 15-30 second delay to give HA time to discover everything before the HomeKit integration spins up. Check out the documentation, scroll down to Disable Auto start.
If you already have it set up, you might have the delay set too short, add more time.
After reading this, I decided to update the HASSOS to 2.12. Upon reboot, within the system log, I see this:
18-06-22 11:12:18 WARNING (MainThread) [hassio.updater] Can't fetch versions from https://s3.amazonaws.com/hassio-version/stable.json: Cannot connect to host s3.amazonaws.com:443 ssl:True [SSLCertVerificationError: (1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate is not yet valid (_ssl.c:1056)')]
If I understand correctly, the system has to be able to read stable.json to know what the latest stable version is. I have no idea where to begin resolving this certificate_verify_failed error .
EDIT: I see the date in the log is off badly (6/22/18). Within Home Assistant, the date and time displays correctly within the HA log, but not in the system log. Any help on how to correct the system date, or perhaps I’m not on the right track?
EDIT2: I see the date in the system log is now correct. Going to reboot and see if I still cannot retrieve stable.json.
Edit3: Now no errors in system log regarding stable.json, but still prompting me with the old version of Hassio. Not sure how to proceed with troubleshooting.
quite right, see my remarks in 0.93: Essent, AmbiClimate, VS Code debugging
hope this gets restored asap, since there’s no real reason to deprecate this…
The date & time on your machine are incorrect. It thinks the AWS certificate is dated in the future.
Yes, that is happens if the NTP is not available to update the host time. He adjust it self after he can reach the NTP server and you can simple click reload on Hass.io/System/Supervisor Panel to force a reload of version file.
The Backend check every 8 Hours for updates. Maybe we can try it to 6 Hours but we have over 260 request per seconds to that file now.
probably due to HTML_imports being deprecated itself. https://www.chromestatus.com/feature/5144752345317376
also i think the dev of the custom-ui hhas released a version that now works
The Sonos integration now discovers players continuously and thus it no longer pauses startup to wait for all players to be found. So it sounds likely that you will indeed have to delay HomeKit startup to make sure that it sees all players.
Climate - EQ3 Bluetooth Smart Thermostats can’t install requirements.
Hello,
after updating from HA 0.92.2 to 0.93.1 my eq3bt thermostats are broken.
It seams Hassbian can not install requirements package python-eq3bt version 0.1.9.
When I try to install python-eq3bt with pip it installs version 0.1.10?
On the same update hassbian updated python to version 3.7.
os: hassbian
python: 3.7.3
ha: 0.93.1
Unable to install package python-eq3bt==0.1.9: ERROR: Complete output from command /srv/homeassistant/bin/python -u -c ‘import setuptools, tokenize;file=’“'”‘/tmp/pip-install-h5o07c45/bluepy/setup.py’“'”‘;f=getattr(tokenize, ‘"’“‘open’”’“‘, open)(file);code=f.read().replace(’”‘"’\r\n’“'”‘, ‘"’"’\n’“'”‘);f.close();exec(compile(code, file, ‘"’“‘exec’”’“‘))’ bdist_wheel -d /tmp/pip-wheel-f50qtumo --python-tag cp37:
ERROR: running bdist_wheel
running build
running build_py
Working dir is /tmp/pip-install-h5o07c45/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
Failed to compile bluepy-helper. Exiting install.
Command was ‘make -C bluepy -j1’ in /tmp/pip-install-h5o07c45/bluepy
Return code was 2
Output was:
b"make: Entering directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\ntar xzf bluez-src.tgz\ntouch ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'glib-2.0' found\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc’\nto the PKG_CONFIG_PATH environment variable\nNo package ‘glib-2.0’ found\ncc -L. -g -Wall -Os -DHAVE_CONFIG_H -I./bluez-5.47/attrib -I./bluez-5.47 -I./bluez-5.47/lib -I./bluez-5.47/src -I./bluez-5.47/gdbus -I./bluez-5.47/btio -I./bluez-5.47/sys -o bluepy-helper bluepy-helper.c ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c \nbluepy-helper.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/att.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gatt.c:32:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gattrib.c:34:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/utils.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/btio/btio.c:37:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/log.c:38:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/io-glib.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/timeout-glib.c:22:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\nMakefile:30: recipe for target ‘bluepy-helper’ failed\nmake: *** [bluepy-helper] Error 1\nmake: Leaving directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\n”ERROR: Failed building wheel for bluepy
ERROR: Complete output from command /srv/homeassistant/bin/python -u -c ‘import setuptools, tokenize;file=’“'”‘/tmp/pip-install-h5o07c45/bluepy/setup.py’“'”‘;f=getattr(tokenize, ‘"’“‘open’”’“‘, open)(file);code=f.read().replace(’”‘"’\r\n’“'”‘, ‘"’"’\n’“'”‘);f.close();exec(compile(code, file, ‘"’“‘exec’”’“‘))’ install --record /tmp/pip-record-dyqemqc8/install-record.txt --single-version-externally-managed --compile --install-headers /srv/homeassistant/include/site/python3.7/bluepy:
ERROR: running install
running build
running build_py
Working dir is /tmp/pip-install-h5o07c45/bluepy
execute make -C ./bluepy clean
execute make -C bluepy -j1
Failed to compile bluepy-helper. Exiting install.
Command was ‘make -C bluepy -j1’ in /tmp/pip-install-h5o07c45/bluepy
Return code was 2
Output was:
b"make: Entering directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\ntar xzf bluez-src.tgz\ntouch ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc'\nto the PKG_CONFIG_PATH environment variable\nNo package 'glib-2.0' found\nPackage glib-2.0 was not found in the pkg-config search path.\nPerhaps you should add the directory containingglib-2.0.pc’\nto the PKG_CONFIG_PATH environment variable\nNo package ‘glib-2.0’ found\ncc -L. -g -Wall -Os -DHAVE_CONFIG_H -I./bluez-5.47/attrib -I./bluez-5.47 -I./bluez-5.47/lib -I./bluez-5.47/src -I./bluez-5.47/gdbus -I./bluez-5.47/btio -I./bluez-5.47/sys -o bluepy-helper bluepy-helper.c ./bluez-5.47/lib/bluetooth.c ./bluez-5.47/lib/hci.c ./bluez-5.47/lib/sdp.c ./bluez-5.47/lib/uuid.c ./bluez-5.47/attrib/att.c ./bluez-5.47/attrib/gatt.c ./bluez-5.47/attrib/gattrib.c ./bluez-5.47/attrib/utils.c ./bluez-5.47/btio/btio.c ./bluez-5.47/src/log.c ./bluez-5.47/src/shared/mgmt.c ./bluez-5.47/src/shared/crypto.c ./bluez-5.47/src/shared/att.c ./bluez-5.47/src/shared/queue.c ./bluez-5.47/src/shared/util.c ./bluez-5.47/src/shared/io-glib.c ./bluez-5.47/src/shared/timeout-glib.c \nbluepy-helper.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/att.c:33:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gatt.c:32:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/gattrib.c:34:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/attrib/utils.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/btio/btio.c:37:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/log.c:38:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/io-glib.c:30:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\n./bluez-5.47/src/shared/timeout-glib.c:22:18: fatal error: glib.h: No such file or directory\n #include <glib.h>\n ^\ncompilation terminated.\nMakefile:30: recipe for target ‘bluepy-helper’ failed\nmake: *** [bluepy-helper] Error 1\nmake: Leaving directory ‘/tmp/pip-install-h5o07c45/bluepy/bluepy’\n”
Any suggestion?
Hi, i am not able to upgrade my Hassio from 92.2 to 93.1, i tried to reboot my Raspberry pi but it does not work, i am always getting the same error :
19-05-19 15:31:04 INFO (MainThread) [hassio.homeassistant] Update Home Assistant to version 0.93.1
19-05-19 15:31:04 INFO (SyncWorker_0) [hassio.docker.interface] Update image homeassistant/raspberrypi3-homeassistant:0.92.2 to homeassistant/raspberrypi3-homeassistant:0.93.1
19-05-19 15:31:04 INFO (SyncWorker_0) [hassio.docker.interface] Pull image homeassistant/raspberrypi3-homeassistant tag 0.93.1.
19-05-19 15:31:05 ERROR (SyncWorker_0) [hassio.docker.interface] Can’t install homeassistant/raspberrypi3-homeassistant:0.93.1 -> 500 Server Error: Internal Server Error (“readlink /mnt/data/docker/overlay2/l: invalid argument”).
19-05-19 15:31:05 WARNING (MainThread) [hassio.homeassistant] Update Home Assistant image fails
Can i get some help with that please ?
You seem to be missing one of the required library packages.
I’ve been struggling also on this one… Want to use it as an alarm for thunderstorms as my dog is very anxious for it.
And the odd part is that the sensor did as if the config was ok (no error messages anywhere), and displaying the state as “Safe”. Today it was code orange here for thunderstorms, but my dashboard just keep showing “safe”. So I only knew by accident it wasn’t doing anything bcs of wrong values in the config.
So the values need to be 100% identical as in the XML files, 1 space or something different and it’s not working. (without error message). I also noticed the language need to be set if you’re not in an English part. I live in Belgium (Dutch) and I am ok with everything in English, but the XML file doesn’t provide the info in English (only Dutch and French), so again the sensor just stated “safe” the whole time…
Little extra info.
I pulled the base XML file for my country from this url: (replace country code with your own)
http://meteoalarm.eu/ATOM/BE.xml
There you can lookup your region and click on the “title link”. Should be something like this:
http://meteoalarm.eu/CAP/POLY/BE_19052019_156231427.cap.xml
Then you need exact this information (marked in Yellow)
For me, the region needed to be “Limburg / Limbourg” exactly. So with the spaces, slash etc…
Same for the language! (notice I need to use country NL and not BE in my case)
Lots of confusion 
My code is this. And now the alert comes in my HA
- platform: meteoalarm
country: BE
province: ‘Limburg / Limbourg’
language: ‘nl-NL’
1 Like
That means 7.5 million hass.io installation if my math is correct. Can you see the top 10 IP to query that file? I think some user just write a script or something to query that file too frequency.
After upgrading to 0.93.9 and 0.93.1
I found that my cpu_load has increased and remains around 3-4 and some times increases to 8-10.
Can’t find anything wrong from my logs.
I am on hassio installed on raspbian on rpi3b+.
Please guide if someone can?
Holy christ 0.93 is doing number on me.
I’ve lost my dark sky sensors. Went back to 0.91 and they are there again.
Most things are taking “more than 10 seconds” so the log is full of that.
Had errors with the logbook all of a sudden and now I get “404: Not Found” trying to access it through the browser.
Fresh install of 0.93, roll back to 0.91 (latest snapshot) and I get the “404: Not Found” straight away.
So that means now I am stuck on 0.93 with no dark sky and log errors from everything being slow. On a Pi 3B+ and never seen this before!
Anyone have an idea why I am having trouble all of a sudden?
dear,
do you face cpu_load higher with new 0.93.0?