This addon seems to be flooding my HassIO system log with authentication requests. See a sample of the log below.
I believe this has been happening since the initial release of the addon.
I don’t get this for any other addon, and it’s mildly annoying that the entire log gets overrun with these messages after ~30 minutes, pushing out any other useful information.
Is there a way to change the authentication so it’s persistent, and only logs in when the addon starts?
19-04-22 14:03:48 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:03:48 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:04:50 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:04:50 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:05:51 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:05:51 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:06:52 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:06:52 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:07:53 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:07:53 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:08:55 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:08:55 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
19-04-22 14:09:56 INFO (MainThread) [hassio.auth] Auth request from a0d7b954_glances for _USERNAME_
19-04-22 14:09:56 INFO (MainThread) [hassio.auth] Success login from _USERNAME_
I added the galande add-on in Hassio with nabucase remote, everything works fine and ingress is awesome. However, I can’t get the sensors to work, I added config as example but nothing. Any thoughts,what I have missed?
Home Assistant wants to connect to a port. Individual components itself do not support Ingress. So you have to assign a port in the add-on configuration in the Network section in order for the component to work.
019-04-23 17:27:34 ERROR (MainThread) [glances_api] Can not load data from Glances API
2019-04-23 17:27:34 ERROR (MainThread) [homeassistant.components.glances.sensor] Unable to fetch data from Glances
2019-04-23 17:28:35 ERROR (MainThread) [glances_api] Can not load data from Glances API
2019-04-23 17:28:35 ERROR (MainThread) [homeassistant.components.glances.sensor] Unable to fetch data from Glances
2019-04-23 17:30:06 ERROR (MainThread) [glances_api] Can not load data from Glances API
2019-04-23 17:30:06 ERROR (MainThread) [homeassistant.components.glances.sensor] Unable to fetch data from Glances
2019-04-23 17:32:07 ERROR (MainThread) [glances_api] Can not load data from Glances API
2019-04-23 17:32:07 ERROR (MainThread) [homeassistant.components.glances.sensor] Unable to fetch data from Glances
2019-04-23 17:34:38 ERROR (MainThread) [glances_api] Can not load data from Glances API
2019-04-23 17:34:38 ERROR (MainThread) [homeassistant.components.glances.sensor] Unable to fetch data from Glances
Thanks all, for the recent conversation . Finally after many attempts, Glances is now performing as a sensor.
As per suggestions, I had to specify the localhost ip address 127.0.0.1, specify the port 61208 on both the Addon config screen and within the sensor configuration.
A restart of HA , and the sensors appeared as entities, to be used on the UI and to populate InfluxDB
I have gotten a bit further now! The only thing left seems to be that it gives me a 400 error now in the addon (same in MotionEye where I’m trying to get the camera still images), so it seems I am doing something wrong in the request, but at least I have a connectiong going on. I have put in my username in Home assistant and the password I use to login.
EDIT: Alright, got it now. What made the difference for me was setting ssl to true in the sensor config, but verify_ssl: false.