Home Assistant Addon

[boennemann]

Hey all,

I'm planning to run the docker container as a Home Assistant Add-on directly on my Home Assistant Yellow – as I understood an add-on is anyway just a super slim layer of metadata on top of docker containers.

Before I dive into that I wanted to open the discussion already.

1. Has anyone done this before and can share something?
2. Are there any reasons I'm missing why this is either a bad idea or not possible
3. Once I've got it working I'd love to contribute the setup back, ideally getting this into Home Assistant as an Add-On without the need to fork.

Let me know what you think!

[busaku]

I would love an direct HA-Addon :)

[boennemann]

In the end it's really just a matter of 3 steps

1. copying the contents of the src/ folder to /addons/solarflow-control
2. adding config.yaml, here is mine:

name: "Solarflow Control"
description: "Solarflow Control"
version: "0.0.1"
slug: "solarflow_control"
init: false
arch:
  - aarch64
  - amd64
  - armhf
  - armv7
  - i386

3. I added this one line to the Dockerfile: COPY ./config.ini /solarflow/config.ini

Edit: In order to ship this we'd probably need to map out all config.ini parameters in the config.yaml and make those available as env vars.

[busaku]

So it worked without any extras?
You should publish it into official HA-Addon Repo :)
( After the okay from all contributor here :) )

[busaku]

Wow, that was easy!
Love it :)

[boennemann]

I hope I get to mapping out the config values soon – it's anyway annoying to rebuild the docker container for every config change. Afterwards it might be almost universally applicable.

Maybe a sprinkle of metadata on top and we're good to go :)

[busaku]

@boennemann any updates here? if not, i would give it a try :)

[Sweti934]

Hi all thank you for the amazing work so far!! Really awesome. To get it right - I could integrate this into home assistant ? I have all the things reporting already to my home assistant mosquito Mqtt. Would I have to change the topics or could I change the topics inside the docker where this here listeners to?

[dfigus]

Hi all,

I just started with a HA addon here dfigus/addon-solarflow-control. It's still in an early state, but you can already configure everything via addon configs and it's runny already for a few days without issues in my setup.

If you want to give it a try and provide feedback or even contribute, you can install it via my EDGE addon repository:
https://github.com/dfigus/hassio-addons-edge

Once I added a bit of docs, I will promote it to a beta (https://github.com/dfigus/hassio-addons-beta) and finally release it (https://github.com/dfigus/hassio-addons).

[Sweti934]

Thanks @dfigus - Highly appreciated! I am so curious how it works out!

[jschroeter]

I wanted to give this a try but I'm stuck at allowing anonymous MQTT access to my broker running in HA, how did you guys do this? I do see in the logs that Hyper wants to connect but the connection gets refused due to the credentials.

[dfigus]

@jschroeter I use the EMQX add-on as this allows anonymous login. The Mosquito add-on does no longer allow anonymous login. The best option would be to spoof the login credentials the hub is sending to the broker, but I didn't have the time to look into this so far...

[reinhard-brandstaedter]

@jschroeter if the hyper uses the same (stupid) credentials as the rest of the SF devices then you can calculate the password it from the device ID and add that user to your MQTT broker.

[reinhard-brandstaedter]

@jschroeter @dfigus as sooner or later people will find out the password of their SF/Hyper device anyway here is how you can calculate it from your device ID, without snooping (verified only on SF devices):

#!/usr/bin/python
import hashlib
device_id = "<DEVICEID>"
md5_hash = hashlib.md5(device_id.encode()).hexdigest().upper()[8:24]

[jschroeter]

Awesome, will give it a try! Username is the device ID?

[reinhard-brandstaedter]

username = device ID, correct