marthoc / docker-homeseer Goto Github PK

I am not able to change to 24 houc clock after I installed the container on my Unraid server. I had a Ubuntu Server and there I change the go file and autoupdate_hs file from export LANG=en_US.UTF-8 to export LANG=en_GB.UTF-8. But that is not working. Is it possible to make one dockerfile so Homeseer gets a 24 hour clock?

Hi

i have had two plugins where due to the command used to run HSConsole in the startup.sh / services.d/run file. Basically the mono HSConsole process needs to be started in the HomeSeer Directory. For example when running HSConsole.exe manuall i have to CD into /HomeSeer and then run the "mono /HomeSeer/HSConsole.exe --log" command. This has affected two plugins, one was reworked by the plug in writer. The other has the plugin writer looking at it. But probably best to fix in the image - there maybe other plugins hanging around like this.

Link to issue in HS forums https://forums.homeseer.com/showpost.php?p=1371794&postcount=9

PS took me about an hour to work out in the tag:avahi you had dumped the startup.sh and moved to somehting called a s6 init daemon :-) i tried altering the run file to:

exec cd /HomeSeer && mono /HomeSeer/HSConsole.exe --log

this still errored as per below (i am out of my depth here, this plug in won't let one save the config file on main or avahi tag builds):

`

`

The current HomeSeer version is 3.0.0.5. Are you able to update the docker container?

https://forums.homeseer.com/forum/homeseer-products-services/system-software-controllers/hs3-hs3pro-software/hs3-hs3pro-discussion/89843-hs3-release-notes

as per title

Hi,

I'm running you homeseer docker container, all good, thanks for the work...
Are you able to update the image to version 3.0.0.534 ?
Thank you...

I get this randomly, isn't every startup, does it matter?

Not sure if anyone else created a fork for this purpose?

If you would like to pull this to a beta repository and tag let me know if there is anything you want me to do. I may play with using buildx to do a multiarch tag / build too.

https://hub.docker.com/repository/docker/scyto/docker-homeseer4beta
https://github.com/scyto/docker-homeseer

I'm seeing the following error in my log file when I start the :latest container

I have confirmed that Scheduler.dll is present in the /opt/homeseer directory.

Sonos plugin isn't able to build its DB - seeing these errors in the log after fresh install of HS3 and Sonos beta plugin -

Jun-23 1:18:17 PM Sonos Error An Error occurred in BuildTrackDatabase for zoneplayer = Bedroom Sonos. Error = Could not load file or assembly 'System.Data.SQLite, Version=1.0.87.0, Culture=neutral, PublicKeyToken=db937bc2054ff139' or one of its dependencies.

Jun-23 1:18:16 PM Device Control Device: Sonos Master Master to BuildDB (1004) by/from: CAPI Control Handler

Jun-23 1:17:30 PM Sonos Error Error in TransportStateChange getting track info. Error = Could not load file or assembly 'System.Data.SQLite, Version=1.0.87.0, Culture=neutral, PublicKeyToken=db937bc2054ff139' or one of its dependencies.. XML =

Jun-23 1:17:30 PM Sonos Error Error in UpdateHS for Zone = Bedroom Sonos. Couldn't get transport Info with error = Could not load file or assembly 'System.Data.SQLite, Version=1.0.87.0, Culture=neutral, PublicKeyToken=db937bc2054ff139' or one of its dependencies.

Jun-23 1:17:29 PM Starting Plug-In Plugin Sonos started successfully in 4 milliseconds

Jun-23 1:17:29 PM Starting Plug-In Initializing plugin Sonos ...

Hi, thanks for the docker, would do you mind bumping up the version on the docker hub as well, currently latest version is HS3 3.0.0.500.
Thanks again

Hi,

what is the user name and password to access hs3?

I get this error when I try to load the container:
docker: Error response from daemon: error while creating mount source path '/opt/homeseer': mkdir /opt/homeseer: read-only file system.
What can be wrong? Found out what was wrong.. had to remove snap and reinstall docker from original source..

Required for airplay and chromecast plugins.
I can see other plugins wanting zeroconf along the way too.

this is what i did to get it working in a runnig container (i connected using bash process my synology docker UI can spawn)

apt-get install avahi-daemon
service dbus start
service avahi-daemon start

i have no idea what you would change in your startup script (i am really not a linux person - i poke and hope)

I think the wilki page might be read one, i have edited other wikis before but there is no edit button and clone in desktop doesn't give me anything i can edit and error with a permissions error.

Hi @marthoc,

I realise there is already a fork of this project for the HS4 beta release.

If and when HS4 makes it to GA release, are you likely to:

Update this project to use HomeSeer4?
Create your own fork for HS4?
Assist/maintain with @scyto on his HS4 fork?
Ignore HS4 and remain focused only on HS3?

I'm currently experimenting with moving from an existing HS3 setup (on a windows VM) to dockerized HS4 on top of Ubuntu 20.04. Trying to do some crystal ball gazing about how viable that approach will be long term.

Thanks for your time.

the plugin author said running homeseer from root (i assume he meant mono unpathed but i am not sure) broke his plugin. While he fixed his plugin (hsbuddy) is there any reason to not call the mono from /usr/bin/mono in the startup script? here is the link, i am not sure if the change is needed given the plugin is now working.

https://forums.homeseer.com/showpost.php?p=1369688&postcount=309

Hello, I'm running this container on an OMV5 server, using portainer and I seem to have an issue with the shutdown function in HS3. As written in the instructions I try to use the tools/system/shutdown homeseer and as far as I can tell from the container log in portainer, the homeseer software shuts down correctly. But after a few seconds it automatically starts up again. I've tried using tools/system/shutdown system but the same thing happens. I've also fiddled around with the docker restart policy settings, but of course that didn't work either. Does anyone know how to change this so that the container actually stops when the HS3 application shuts down?
Thanks in advance!