Closed Mariusthvdb closed 4 years ago
I just tested this issue and I get the same result. Any status other than 200 seems to trigger the exception. The text about bad credentials is either supplied by the pygithub package or the github api as this text is not present in the code for the sensor.
I'll try to see if I can find something to fix this issue seeing as I need my python practice.
Thanks! Could you please check also why the first ( and copied directly from the documentation) homeassistant repo doesn’t work either? No error, but no sensor either ;-)
If i use the following example from the integration page I get a sensor that works just fine for me
sensor:
- platform: github
access_token: removed
repositories:
- path: 'home-assistant/home-assistant'
If you have a invalid or moved repository in the list it does break the setup of valid repositories
thanks for checking! and, well, I checked again too, and what do you know, the home assistant sensor is there after all, but it's the only one without the prefix (entity_namespace) Github, as Ive configured the full config posted above... How on earth is that possible?
thanks @kuchel77 for the fix, much appreciated! hope we see it soon in the update
The problem
using the GitHub sensor with an extensive list of tracked repos, the sensor isn't created at all, even if only 1 of the listed repos is incorrect/unavailable
Environment
Problem-relevant
configuration.yaml
Traceback/Error logs
Additional information
any of the above commented repos cause the complete sensor to not being created/initiated. would expect the sensor to error on the given repo, and create the rest of the sensor.
more over, the GitHub error is about bad credentials, which is incorrect, but maybe out of control for the HA system. Please see if this sensor can isolate the incorrect repo, and continue building the rest.