Open roblandry opened 5 years ago
Hi roblandry,
Cool that you are extending my sensor;) If we can make it work stable I would like to merge your changes in the component.
I don't have experience with TLS, so maybe you can tell more about your setup such that I can recreate it at home for testing.
BTW: I've editted your post for syntax highlighting. After the 3 back-ticks, you can specify the language for syntax highlighting as explained in this cheatsheet.
@Sanderhuisman, I updated the issue to provide more info. I am thinking that using the tls option is causing the errors due to async. I think to make it work without errors, the component needs to be updated to async. But that is just a thought. I tried messing with the code for async, but i dont know enough about how this component ACTUALLY works, nor do i know much about async. I was able to get the errors to go away, however, nothing actually populated.
hi, just reading this ; is it already possible for a restart service, to restart a specific container or a switch turn off/turn on ?
@pergolafabio I believe that is working in the latest version of the component (it moved to a new repository such that it can be installed using hacs)
ah cool, i am new to this i still need to install ha-dockermon , right, this cutsom component is not working as a standalone ?
This component works without ha-dockermon as it can access the Docker daemon directly. Therefore, it is important that you mount the Docker socket when you are using HA in a Docker container.
yes, but i am using HassOS , can i use it too then?
i am not sure how i can mount that docker socket , little bit confused :)
Also posted in the hass forum.
Hi, I am needing assistance... I am so close i think. I have transitioned to using docker_monitor custom component. I have added tls connections which are working great. The last leg of my transition is to create a service, that will allow restarting containers (ultimately i want it so i can restart the home-assistant container). I added the code and it works, however i am getting this traceback on hass start. I have placed comments in the code to identify my changes and provide a means of identifying where the problem lies. Any assistance would be awesome!
TLS is used based on THIS Securing the docker.sock
This is my docker-compose for the proxy:
This is an example configuration. Default config works also.
This is the current __init__.py