Open have-no-clue-what-im-doing opened 1 week ago
How did you enter token the first time, through web ui or did you edit config.yaml with editor like nano or vim?
I am experiencing the same issue. I first entered the api key using the web interface. This inserted it into the ID field in the config file, but with the !!int
prefix, as mwntioned before.
How did you enter token the first time, through web ui or did you edit config.yaml with editor like nano or vim?
Yeah I updated through the web GUI. I am using the latest non dev docker image.
Okay, it is a bug in web ui settings then, I'll fix this for next release.
About 20 minutes after adding my BirdWeather API Token to the config (Through the web GUI) my container crashed. When I went to restart the container I got this error:
Error loading settings: error initializing viper: fatal error reading config file: While parsing config: yaml: cannot decode !!str my_birdweather_api_token as a !!int
Did BirdWeather tokens use to be only int based?
I edited the config file and changed
!!int
to!!str
Started the container back up and all is running well.I think the container crashed only when it detected a bird and was trying to upload it to BirdWeather and trying to use the API key. It's working perfectly fine now and is properly uploading data to BirdWeather