HS4 Homeseer Linux - Docker Image & Repository

[wpiman]

Updated repository to include support for:

• 4.2.16.7 BETA
• 4.2.17.0 RELEASE (Release Notes)
• 4.2.17.2 BETA (Release Notes)

Additional Resources:

• [GitHub] https://github.com/HomeSeerLinux/homeseer-docker
• [DockerHub] https://hub.docker.com/repository/do...eseer/homeseer

Ok... I installed in via the YML file from the Github page. Not sure what version that makes it?

Anyways, I changed the port from 80:80 to 82:80 (Have Apache running).... ran docker compose...

Went to the web page and port... It asked for my username-- great!

default/default

Log shows:

homeseer | 07:48:10:9163:[Web Server]->Web Server authorized login successful from: 192.168.0.6 User: default

But I don't see any pages returned! I tried /homeseer/html/index.html and all sorts of permutations.

All the files look readable through the heirarchy?

-rwxr-xr-x 1 root root 6902 Mar 10 2020 index.html
-------------------
Shut of Apache and web to port 80... working now... Changing settings.ini
Changed the settings to port 82 in Homeseer-- same issue.

Something is causing this to only work on port 80.

[wpiman]

Ok, so I did a system restore within the container. I had to work through a few issues to get it to boot. I am sure the first couple are mostly Linux HS things.

The settings.ini file had some script path stuff at the top. Linux didn't find those and caused a reboot. I just comment out that line. I don't even think I was using half that stuff anymore anyways.


In the settings file, I also shut off the binding to an IP address. This is a configuration in the lab settings. After that, the web browser came up.


Once that happened, I was able to see all the devices. I had to manually readd the plug ins, and most of them seemed to bring over the settings just fine. I had a one of two that didn't work- but I think that was because I might have had the HS3 legacy version of the plugin and didn't upgrade.

Where things went downhill was on the plugins that use the subnet. For example, the Chromecast plugin checks the subnet (I think via mDNS) to see what Google devices are present. I think Airplay is similar. The AK Google plugin also seemed to require me to use a local web browse on the machine to get a Google Token. That I could work around

I tried forwarding the mDNS port. (5353) No luck. I've kicked back on the Windows instance-- but maybe I will try another port tomorrow. (5009). I think the AK Googlecast has more options for discovery so maybe that would work.

https://blog.oakbits.com/google-cast...onnection.html

The other option is to run in host mode-- but I think you can only have one container in that case...