-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fiatchamp does not work in a standalone container #59
Comments
i think you need to set these two environment variables in your docker config. export FiatChamp_HomeAssistantUrl="https://hass.example.com" and the token for the home assistant api. export FiatChamp_SupervisorToken="jhiswgfrhjsfgdhjsgfhjfgsjhfghjfgshjgfhjfgdhjfgdhjgdf" im not really sure 🤔 the problem is the standalone mode was not planned to be used and exists only that i can test it locally without loading a new addon in home assistant everytime. but im working on the next version which can be used both as standalone or as home assistant addon. with its own minimal webinterface for configuration. |
Thanks for the reply Thank you Marco |
Gave me an error that I discovered described in this issue: wubbl0rz#59
I am getting the following error trying to run in a standalone container...
Is this because my HA URL isn't working? I'm currently trying via docker network...
|
Make sure you have a valid long lived access token in your Docker Compose. It seems like it may not be registering your Home Assistant URL environment variable as well? The default is supervisor if not running in standalone mode and the URL is not specified. |
HI
Congratulations for the excellent work.
I would like to migrate home assistant from the supervised version (where it works perfectly) to the one that uses containers.
Unfortunately I can't if I can't get Fiatchamp to work
I tried using the example configuration. I generated the token but I get this error:
ERROR: Call failed. Resource temporarily unavailable (supervisor:80): GET http://supervisor/core/api/states
see logs attached
Thanks in advance
portainer.fiatchamp.log
_FiatChamp_logs.txt
Originally posted by @marcobto58 in #22 (comment)
The text was updated successfully, but these errors were encountered: