Skip to content
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

Create hass.io component for Home Assistant #63

Closed
TD22057 opened this issue Apr 9, 2018 · 8 comments
Closed

Create hass.io component for Home Assistant #63

TD22057 opened this issue Apr 9, 2018 · 8 comments

Comments

@TD22057
Copy link
Owner

TD22057 commented Apr 9, 2018

hass.io: https://www.home-assistant.io/hassio/
Tutorial: https://www.home-assistant.io/developers/hassio/addon_tutorial/
More config: https://www.home-assistant.io/developers/hassio/addon_config/

@larizzo
Copy link

larizzo commented Apr 9, 2018

You can use this to get you started: https://github.com/larizzo/docker-insteon-mqtt

@lnr0626
Copy link
Contributor

lnr0626 commented Jul 17, 2018

Would you accept a PR for this? I'd find this useful for my own setup, and can work on it as time allows. Only limitation is that I am using one of the old hubs with the ethernet PLM interface, and don't have any USB/serial PLMs to test with.

@TD22057
Copy link
Owner Author

TD22057 commented Jul 17, 2018

Sure - the device shouldn't make any difference in the docker set up.

@jrhorrisberger
Copy link

jrhorrisberger commented Jul 17, 2018

I bumbled around with it last night and got it working, just need to clean it up (never messed with creating HASSIO Dockers before). Borrowed a lot from AppDaemon add-on. But here's what I have now in the meantime, in case someone else gets to it sooner

  1. Download/Rename config.yaml to insteon_mqtt.yaml and put it in the root of the config folder
  2. Create folder insteon-mqtt in addons and place the three below files
  3. Add/Install from local add-ons from under hass.io ADD-ON STORE in UI

FILE1: config.json

{ "name": "InsteonMqtt", "version": "11", "slug": "insteonmqtt", "description": "Insteon to MQTT", "startup": "before", "boot": "auto", "host_network": true, "ports": { "1883/tcp": 1883 }, "map": [ "config:rw", "share:rw", "ssl" ], "options": {}, "devices": ["/dev/ttyUSB0:/dev/ttyUSB0:rwm"], "schema": {} }

FILE2: insteon_mqqtt_run.sh

insteon-mqtt /config/insteon_mqtt.yaml start

FILE3: Dockerfile

FROM $BUILD_FROM

RUN \
    apk add --no-cache --virtual .build-dependencies \
        python3-dev=3.6.4-r1 \
    \
    && apk add --no-cache \
        python3=3.6.4-r1 \
        git \
    && pip3 install --upgrade virtualenv wheel \
    && git clone 'https://github.com/TD22057/insteon-mqtt.git' --branch dev /opt/insteon-mqtt \
    && pip3 install /opt/insteon-mqtt \
    && apk del --purge .build-dependencies

COPY insteon_mqqtt_run.sh /
RUN chmod a+x /insteon_mqqtt_run.sh

CMD ["/insteon_mqqtt_run.sh"]

@WLS7
Copy link

WLS7 commented Aug 22, 2018

Hello, I'm totally new to this. What am I missing? when I tried the above, I get this:

18-08-22 02:12:05 INFO (SyncWorker_0) [hassio.docker.addon] Start build local/armhf-addon-insteonmqtt:11
18-08-22 02:12:09 ERROR (SyncWorker_0) [hassio.docker.addon] Can't build local/armhf-addon-insteonmqtt:11: oci runtime error: container_linux.go:263: starting container process caused "exec: "/bin/sh": stat /bin/sh: no such file or directory"

This is on a Raspberry pie 3B. I tried it on a clean install of Hassio 1.3 and also 1.9. Do I need to install something else also?
Thanks

@billchurch
Copy link

+1 for hassio add-on. I am happy to help formalize this as an add-on if needed. Has someone already done a PR on this?

@billchurch
Copy link

Answering my own question, looks like #76 has it

@TD22057
Copy link
Owner Author

TD22057 commented Sep 9, 2018

I'm calling this closed w/ the merge of PR #76. If there are any problems, please open a new issue.

@TD22057 TD22057 closed this as completed Sep 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants