Release v0.5.4This is a general maintenance release.
Changes
Upgrades nginx to 1.16.1-r0 Upgrades add-on base image to v4.1.1 Updates HA Auth URL in NGinx LUA script
Fixes path handling for SSL certificates Use Hass.io DNS as NGinx resolverQuestions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Release v0.5.5This is a general maintenance release.
Changes
Update Readme for HA sensor caused by ingress (#28) Updates glances to v3.1.2 (#31) Updates influxdb to v5.2.3 (#30
Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Glances suddenly stopped to work. Any idea what could be wrong?
Displaying error:
502: Bad Gateway
INFO: Starting NGinx...
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
2019/10/02 23:10:54 [emerg] 5014#5014: bind() to 0.0.0.0:61209 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:61209 failed (98: Address in use)
2019/10/02 23:10:54 [emerg] 5014#5014: bind() to 0.0.0.0:61209 failed (98: Address in use)
nginx: [emerg] bind() to 0.0.0.0:61209 failed (98: Address in use)
O.K. Solved. Wrong user/password.
Looks like ‘glances’ config was reset to initial (by some update?).
{
"log_level": "info",
"process_info": false,
"refresh_time": 10,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"influxdb": {
"enabled": false,
"host": "a0d7b954-influxdb",
"port": 8086,
"username": "homeassistant",
"password": "homeassistant",
"database": "glances",
"prefix": "127.0.0.1",
"interval": 60
}
}
Can anyone give me any hints as to why I can’t get the Glances sensors detected/setup? Glances itself appears to be running fine and I can open it on the sidebar. I am running the Glances add-on in HASSIO
Below is my configuration in the Add-On
{
"log_level": "info",
"process_info": false,
"refresh_time": 10,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"influxdb": {
"enabled": false,
"host": "a0d7b954-influxdb",
"port": 8086,
"username": "glances",
"password": "",
"database": "glances",
"prefix": "localhost",
"interval": 60,
"ssl": false
}
}
My configuration for the sensor is in my sensor config file and is below:
- platform: glances
host: 127.0.0.1
port: 61209
version: 3
resources:
- 'processor_load'
- 'memory_use_percent'
- 'disk_use_percent'
This is a general maintenance release.
Changes Updates docker to v4.1.0 (#34) Updates glances to v3.1.3 (#35) Updates paho-mqtt to v1.5.0 (#36) Updates zeroconf to v0.24.0 (#40) Upgrades add-on base image to v5.0.2 Upgrades python3 to 3.7.5-r1 Upgrades nginx to 1.16.1-r1 Updates psutil to v5.6.7 (#42)Questions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Hi all
I’ve just installed this component but I don’t find any sensor, but I can see the web page with all the values.
This is the add-on config
{
"log_level": "info",
"process_info": false,
"refresh_time": 10,
"ssl": false,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"influxdb": {
"enabled": true,
"host": "a0d7b954-influxdb",
"port": 8086,
"username": "username",
"password": "password",
"database": "glances",
"prefix": "127.0.0.1",
"ssl": true,
"interval": 60
}
}
This is the sensors.yaml
- platform: glances
host: 127.0.0.1
port: 61209
version: 3
resources:
- 'processor_load'
- 'memory_use_percent'
- 'disk_use_percent'
and this is the influxdb add-on
{
"auth": true,
"reporting": true,
"ssl": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem",
"envvars": []
}
In the log there is nothing related to “glances”
Should I follow what in this page or this is valid only if lances is not installed as add-on?
What can I check?
Thanks
Hello, I have just upgraded HA from 0.100.3 to 0.103.5 and glances no longer works for me? Glances is running on another Ubuntu server on my network running plex server and glances was all good till this upgrade. My current config for this is below. Any help or suggestions would be greatly appreciated.
- platform: glances
host: 192.168.1.10
resources:
- 'processor_load'
- 'cpu_use_percent'
- 'memory_use_percent'
- 'cpu_temp'
- 'disk_use_percent'
@trhessel - I was having a similar issue (but using the integration rather than YAML sensor), tried opening Glances on laptop via ip_address:61208, and was prompted for a username and password, put in my HA login details which allowed access.
Tried re-adding my integration but still wouldn’t work, checked the logs of the Glances add-on and it was reporting repeated error accessing the Influx db, checking realised I didn’t have the glances database or user, created both of these, restarted the glances add-on and my integration connected first time.
Hope this helps you out!
Sorry no luck, removed old config tried to add as integration and as config in configuration.yaml vs sensors file :(. Any other thoughts?
Are you able to open Glances in a browser window on another machine? Do you get a login prompt?
I am able to open glances from a browser but do not get a login prompt, seems to work without a login.
Release v0.6.0This is a general maintenance release.
Changes Updates bottle to v0.12.18 (#43) Updates zeroconf to v0.24.4 (#47)
Updates maintenance/license year to 2020
Fixes some spelling and grammar Adjust add-on installation instructions Funding adjustments Upgrades add-on base image to v6.0.1 Upgrades gcc to 9.2.0-r3 Upgrades musl-dev to 1.1.24-r0 Upgrades python3 to 3.8.1-r0 Upgrades lua-resty-http to 0.15-r0 Upgrades nginx to 1.16.1-r4 Update Hass.io wheels for Alpine 3.11 Fixes some spelling and grammarQuestions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
anyone have success with showing mount drives into HA via the API?
the local drives are no problem, but if i have a usb or nfs/cifs drive mount im not able to get it over in HA, but can fine see it on the web-interface of glances
Release v0.7.0This is a general maintenance release.
Changes Add integrations setup instructions. (#48) Upgrades nginx to 1.16.1-r6 Update add-on documentation to use new YAML configuration format Update add-on config with new password & list features Updates for upstream Supervisor changes Re-branding Updates psutil to v5.7.0 (#53) Updates requests to v2.23.0 (#54) Upgrades add-on base image to v7.0.2
Fix lint warnings Update community forum linksQuestions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Since home assistant 0.106 and glances 0.7.0 I’m getting the following errors on server startup:
2020-02-28 11:41:56 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.glances
2020-02-28 11:41:56 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 425, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.glances_thinkpad_1_temp. Platform glances does not generate unique IDs
2020-02-28 11:41:56 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 425, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.glances_core_2_temp. Platform glances does not generate unique IDs
2020-02-28 11:41:56 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 425, in _async_add_entity
raise HomeAssistantError(msg)
homeassistant.exceptions.HomeAssistantError: Entity id already exists: sensor.glances_core_0_temp. Platform glances does not generate unique IDs
I have tried removing the integration, addon, make sure no entities exists, delete glances.conf file and adding all again.
I’m guessing it is related to the dynamic sensors loading, when I check the glances WebUI there is no sensor appearing more than once.
Any idea what may cause the error?
Thanks.
Since 2 days, after reboot of hassos I get around 90 percent user cpu. Hass is unresponsive untill I disbale glances via supervisor panel and after enable everything turns back to normal… did anything change?
some more info. Directly after restart:
Turn Glances off and on via supervisor:
Info:
Add-on version: 0.7.0
You are running the latest version of this add-on.
System: HassOS 3.11 (amd64 / qemux86-64)
Home Assistant Core: 0.106.5
Home Assistant Supervisor: 209
Release v0.7.1This is a general maintenance release.
Changes Updates docker to v4.2.0 (#49) Updates zeroconf to v0.24.5 (#55) Updates glances to v3.1.4 (#56) Upgrades add-on base image to v7.0.3 Upgrades gcc to 9.2.0-r4 Upgrades musl-dev to 1.1.24-r1 Upgrades python3 to 3.8.2-r0 Don’t use apk cache on cleanupQuestions? Join our Discord server! https://discord.me/hassioaddons
Enjoying my add-ons? Consider supporting my work: https://patreon.com/frenck
Hi all… in home assistant log i receive this error…
Entity id already exists - ignoring: sensor.glances_package_id_0_temp. Platform glances does not generate unique IDs
I have delete integration in configuration.yaml , and use direct integration in home assistant.
The same error.
Glance is install on a debian OS.
Manyy thanks!
