Skip to content
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

Open
marcobto58 opened this issue Sep 12, 2023 · 4 comments
Open

fiatchamp does not work in a standalone container #59

marcobto58 opened this issue Sep 12, 2023 · 4 comments

Comments

@marcobto58
Copy link

marcobto58 commented Sep 12, 2023

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)

@wubbl0rz
Copy link
Owner

wubbl0rz commented Sep 18, 2023

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.

@marcobto58
Copy link
Author

Thanks for the reply
with the simple url of home assistant (without references to the supervisor path) it now works!!!
Great!!
I look forward to the next standalone version.

Thank you

Marco

hkuehl added a commit to hkuehl/FiatChamp that referenced this issue Aug 25, 2024
Gave me an error that I discovered described in this issue: wubbl0rz#59
@Wetzel402
Copy link

I am getting the following error trying to run in a standalone container...

curl: (6) Could not resolve host: supervisor
[16:23:54] ERROR: Something went wrong contacting the API
curl: (6) Could not resolve host: supervisor
[16:23:54] ERROR: Something went wrong contacting the API
/run.sh: line 14: SUPERVISOR_TOKEN: unbound variable

Is this because my HA URL isn't working? I'm currently trying via docker network...

FCAUconnect_HomeAssistantUrl: http://10.10.0.99:8123
    networks:
      ha:
        ipv4_address: 10.10.0.107
networks:
  ha:
    external: true

@Blueion76
Copy link

I am getting the following error trying to run in a standalone container...


curl: (6) Could not resolve host: supervisor

[16:23:54] ERROR: Something went wrong contacting the API

curl: (6) Could not resolve host: supervisor

[16:23:54] ERROR: Something went wrong contacting the API

/run.sh: line 14: SUPERVISOR_TOKEN: unbound variable

Is this because my HA URL isn't working? I'm currently trying via docker network...


FCAUconnect_HomeAssistantUrl: http://10.10.0.99:8123

    networks:

      ha:

        ipv4_address: 10.10.0.107

networks:

  ha:

    external: true

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants