Forceu / barcodebuddy-homeassistant

MIT License
26 stars 22 forks source link

Unable to connect to API: Invalid API key #26

Open awdark opened 1 year ago

awdark commented 1 year ago

Trying out barcodebuddy for the first time, set up the username/password but stuck on the API screen.

I have Grocy as well as this barcodebuddy-homeassistant both installed in my Home Assistant running in a VM behind a Nginx reverse proxy.

Per the documentation, I added 9192 to the grocy configuration

Using http://192.168.0.x:9192/api Unable to connect to API: Invalid response. Are you using the correct URL?

https://192.168.0.x:9192/api Unable to connect to API: Invalid SSL certificate! If you are using a self-signed certificate, you can disable the check in config.php

I have both curl_allow_insecure_ssl_ca as well as curl_allow_insecure_ssl_host enabled.

In Grocy > wrench > REST API BROWSER

I am presented with https://redacted.duckdns.org/api/hassio_ingress/REALLYlongString/api/

Entering the API key I generated, I get Unable to connect to API: Invalid API key

I believe this means this install of barcodebuddy is communicating with my install of Grocy. But there may be a disconnect with the GUI configuration in Home Assistant or I may be doing something wrong.

The log is fantastically dull especially with debug enabled. Barcode Buddy for Grocy Barcode Buddy supervisor started

Initialising container File permissions set Using SSL keys found in /config/keys Parsing environment variables ATTACH_BARCODESCANNER not set, disabling input grabber Setting timezone to America/Los_Angeles Starting Nginx Starting Websocket Server Starting Redis Starting PHP-fpm8

monsieurhannes commented 1 month ago

Same here, any guidance how to connect? When using 9192 GROCY doesn't start...