-
Notifications
You must be signed in to change notification settings - Fork 12
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
Not starting.. #19
Comments
21-03-16 17:38:47 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host 172.30.33.8:8099 ssl:default [Connect call failed ('172.30.33.8', 8099)] By default homegear is not running on port 8099, but homeassistant ingress des expect to run the webserver on port 8099. --> https://developers.home-assistant.io/docs/add-ons/presentation/Here are the requirements of Ingress: Ingress must be enabled. Set ingress: true in config.json. but simply setting the Port 80 to 8099 ends in "error 404" because homeassistant's ingress requests "index.php", which does not exist: |
I've added some bugfixes to the new release. Now the nodeBlueCredentialKey.txt will be created if it not exist so the sartup is not blocked by this issue. i have some trouble to get the webui running, test this fixes and give me some feedback pleace. |
Hi Sebastian, i forked your repo and made some changes to "my" environment. I got it now up and running. One big problem is, that my /dev/ttyUSB0 device is in group 18/audio. Homegear is started with the "homegear" user and there is no group 18 in the addon-container.. So homegear must be started as root. For the webserver you need to set It looks like homegear is not really maintained and it looks a bit orphaned. But unfortunately i need it for my Max! thermostat via 868 MHz nanoCUL. :/ |
Hi Flo, it's not so nice to running homegear as root but for the moment it's the best workaround i think. I will have a look to the HA user management to get the ha user running in the docker container like mosquito and other add-ons. I'm not shure if this will fix the problem. As I see it, homegear has not been developed properly for a long time. Version 0.8 has been in the documentation for a good two years now and the documentation sucks. Did you try to newly install your fork (by deleting the existing folders)? Did you get the webfrontend up? |
I think you don't need the ingress_entry setting in your config.json becouse there is a index.php that will direct you to /admin. |
At the first start, it tells: nodeBlueCredentialKey.txt
After creating this file with a random key, homegear ist starting, but the RPC-Server on Port 2001 does not anwer.
Also the Webinterface just showing 502: bad Gateway
Home Assistant OS 5.12
supervisor-2021.03.6
core-2021.3.4
Homegear
Current version: 0.72.0
homegear_log.txt
The text was updated successfully, but these errors were encountered: