Clicking Start in HA will make the plugin look like its starting, but then after refreshing the page its stopped again.
Tried reinstalling plugin, no luck.

Logs in the plugin are empty.
Logs in supervisor show this:

Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:125
Integration: Home Assistant Supervisor ([documentation](https://www.home-assistant.io/integrations/hassio), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+hassio%22))
First occurred: 20:43:44 (16 occurrences)
Last logged: 21:09:59

Failed to to call /addons/d44967b1_bbuddy-grocy/stats - Container addon_d44967b1_bbuddy-grocy is not running
Failed to to call /addons/d44967b1_bbuddy-grocy/stats -

I'm looking for a way to connect a physical barcode scanner (/dev/input/event0)

I saw this issue #47 about a work-around using keyboard_remote + Node-RED to make an api call to barcodebuddy. Is this the only way to make it work or does the add-on support it directly now?

I noticed in the startup log:

[EnvParser] Parsing environment variables
[EnvParser] ATTACH_BARCODESCANNER not set, disabling input grabber

https://developers.home-assistant.io/docs/add-ons/presentation/#ingress

Adding Ingress feature to barcode buddy will make barcode buddy more integrated with Home Assistant.

Hi,

I see that many upgrades have been done on the "https://github.com/Forceu/barcodebuddy". Does it possible to transfer this enhancements to the HomeAssistant add-on ?

Thank you !

Hello,
I just discovered this add-on and thought I would try it. I've managed to make it connect to my Grocy instance (through disabling SSL, still trying to make it work with SSL).

I see the following error for Redis Cache: "Cannot connect to Rediscache! Connection refused". I assume that should not happen. Any suggestions how to fix this, other than disabling Redis Cache?

The addOn doesn't store data in a persistent storage, leading to loosing all data after a shutdown/restart.

As far as I know there should be a WORKDIR in the Dockerfile to set this up.

Reproduce:

• install addOn
• configure it (user, API key)
• restart addOn
• all data is missing including the first user

Followed the steps that you have in the Read me, by adding the the repository to the Supervise /Add-on/Repositories directory. I then saved and reloaded. The BCB add-on did not show up. I did a system restart and still not add-on. Has the repository changed by any chance? Can you please take a look into this

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

Hello,

I'm trying to install this addon on HA 2023.3.4 and when I try to run this addon I'm getting in logs:

s6-overlay-suexec: fatal: can only run as pid 1

Any idea how to fix it?

Thanks

Just attempted to install this add-on and got an error when I try to enter the web UI.

Error as follows:

FS Error DATA_PATH_NOT_WRITABLE: Database file cannot be created, as folder or database file is not writable. Please check your permissions.
Have a look at this link to find out how to do this: How do I make files and folders writable for the web server?

not clear which folder I need to add permissions to as the linked instructions are for a folder that does not exist.

Edit to add running

Home Assistant 2023.1.4
Supervisor 2022.12.1
Operating System 9.4
Frontend 20230110.0 - latest

Homeassistant version: 2023.3.1
Running on: rpi4 (Arm64)
Using an external SSD

I can not install the Addon into my Homeassistant installation (I uninstalled it recently when i migrated back from an x86 device as the addon made issues with full backups). Now on my PI I wanted to set it up again and get this error when I try to inatall the Addon:

23-03-09 08:42:30 ERROR (SyncWorker_4) [supervisor.docker.addon] Can't build d44967b1/aarch64-addon-bbuddy-grocy:dev-docker-based: no matching manifest for linux/arm64 in the manifest list entries
23-03-09 08:42:30 ERROR (SyncWorker_4) [supervisor.docker.addon] Build log: 
Step 1/13 : ARG BUILD_FROM
Step 2/13 : FROM ${BUILD_FROM}

Any suggestion what I can do, do others also have this issue?

I noticed that the addon stores files directly in /config in Home Assistant. This makes it more difficult to clean up after uninstalling and clutters the directory.

Would it be possible to use a subfolder such as "barcodebuddy"?

I think this is related to #4.

Not sure why but the addon installs fine and the log says its working but I cant seem to connect. The port is forwarded to home assistant server as well. It just says the site cant be reached.
Any ideas?

I tried to install the addOn, the log gives a success message, but if I try to start the addOn it throws an error in the addOn log.

HA Supervior log:

21-02-28 04:19:03 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/d44967b1_bbuddy-grocy
21-02-28 04:19:03 INFO (SyncWorker_4) [supervisor.docker.addon] Starting build for d44967b1/armv7-addon-bbuddy-grocy:dev-docker-based
21-02-28 04:19:10 INFO (SyncWorker_4) [supervisor.docker.addon] Build d44967b1/armv7-addon-bbuddy-grocy:dev-docker-based done
21-02-28 04:19:10 INFO (MainThread) [supervisor.addons] Add-on 'd44967b1_bbuddy-grocy' successfully installed
21-02-28 04:19:49 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on d44967b1/armv7-addon-bbuddy-grocy with version dev-docker-based

If I try to start the addOn, it gives an error in the addOn log:

[FATAL tini (7)] exec /init failed: Exec format error

There are no other error messages, but the addOn doesn't start.

My system is a Pi4, with the following specs:

Version | core-2021.2.3
-- | --
Installationstyp | Home Assistant Supervised
Entwicklung | false
Supervisor | true
Docker | true
Virtuelle Umgebung | false
Python-Version | 3.8.7
Betriebssystemfamilie | Linux
Betriebssystem-Version | 5.10.11-v7l+
CPU-Architektur | armv7l

Host-Betriebssystem | Raspbian GNU/Linux 10 (buster)
-- | --
Update-Channel | stable
Supervisor-Version | supervisor-2021.02.11
Docker-Version | 20.10.3
Speicherplatz gesamt | 109.5 GB
Speicherplatz genutzt | 18.0 GB
Healthy | true
Unterstützt | Unsupported
Supervisor-API | ok
Versions-API | ok

Any ideas where to look at? A (very) short search showed the error message in combination with some armv7 architecture, but that's unfortunately outside my knowledge. Thanks for any help!