john whately
john whately
> This requires docker to either be bundled (bloating app size) or to be preinstalled (for only one app??). > > What is a better approach is to utilize native...
> > I'm not sure how the Flatpat works, but to my understanding a FLatpak opens up alot of holes by default to get it to run (like the home...
Sounds good, tempuarily however I have got a docker container "working" (lets call it alpha) for windows: Dockerfile ```docker FROM redhat/ubi8 # or the nvidia cuda's version of ubi8, im...
@davidusb-geek is the "currency" homeassistant variable being passed in. Could that be used as default?
A temporary stop gap could be another param *(for addon users)*: web_server.py ```python ... params['retrieve_hass_conf']['alt'] = options['Altitude'] params['retrieve_hass_conf']['unit_of_measurement'] = options['Currency'] params['optim_conf']['set_use_battery'] = options['set_use_battery'] ... ``` utils.py ```python ... if 'custom_unit_load_cost_id'...
> When was this first time that you tried? There has been a lot of improvements for these types of issues thanks to the work of @GeoDerp earlier this year....
If you with to grab the image via a container registry: *(not build the image locally)* - EMHASS amd64 add-on: https://hub.docker.com/r/davidusb/image-amd64-emhass - Docker run example: ```bash docker run -it -p...
> I'm not sure I understand the difference between the 'addon' and the regular version of EMHASS. I thought addons were just for HAOS, and I'm not using HAOS, so...
I think the best way to use add-on mode is via passing in the arguments via the standalone mode Image ``` docker run -it -p 5000:5000 --name emhass-container -v $(pwd)/options.json:/app/options.json...