#manually running add-on(s)

1 messages · Page 1 of 1 (latest)

river patrol
#

So... I have to run the add-on manually/standalone. As far as I know, add-ons are just Docker images/containers.

Here’s my question: at the beginning of the Dockerfile, there should be two lines according to the HA dev docs:

ARG BUILD_FROM
FROM $BUILD_FROM

What does the supervisor put into the BUILD_FROM variable when the container is created?

info I have HA running in a Docker container on my home/lab server alongside many other services. So no add-ons for me 😠 - at least not in the “normal” way…

Anyway, if somebody is curious what I’m trying to run, here it is:
👉 https://github.com/kind3r/hass-addons/tree/master/ttlock-hass-integration

I got a good deal on a TTLock-compatible smart door lock, and since I don’t like cloud services (especially CN ones), I want to run this add-on that provides a GUI for controlling these locks offline. Finally, I’m planning to run it on an rpi0w located near the lock (since BT in these locks is very weak).

GitHub
hass-addons/ttlock-hass-integration at master · kind3r/hass-addons

Integration of the offline TTLock sdk into Home Assistant - kind3r/hass-addons

keen creek
#

You generally can't run add-ons outside of HAOS because they require the Supervisor

#

Are you trying to modify that add-on to work outside of HAOS?

river patrol
# keen creek Are you trying to modify that add-on to work outside of HAOS?

I'm pretty sure, that I wrote this that I need to run this "standalone".
Seems like I have to tinker with start.sh script inside this one - it's calling bashio and some variables from it.

Anyway I found answer putting in my case node:18-bullseye works.
I think there should be something like ghcr.io/hassio-addons/base:14.2.0 , but node works too 😆

keen creek
#

The add-on hasn't been touched in 4 years though

#

But yeah, the bashio stuff is the API network calls to Supervisor to get the add-on config.

river patrol
#

Oh, never found this issue 🤦‍♂️

yes, I know it's looks old, but there is not much to change in the code anyway, updates would be only to bump up version.

I know another "old" project for esp8266, where there is no point in update since it "works just fine".

I'm from those: if it works, don't touch 😆

river patrol
keen creek
#

But, "Using these images as a base for other Docker projects is, however, not recommended." So finding another like node is probably best.