Synology - guide to switch from Jadahl package to official docker (domoticz-docker)

[smaus]

How can you run a lua script in docker.

[Gravityz]

ehhh

put it in setup-more options-events-+ button-lua

am i missing something

How can you run a lua script in docker.

[smaus]

I try to add a ZigBee CC2531 stick, but i get this error.



2021-04-26 20:00:35.139 zigbee: (zigbee) Connected to MQTT Server: 127.0.0.1:1883
2021-04-26 20:00:35.140 Error: UNHANDLED PACKET TYPE: FS20 24

[Rick1212]

Hi,
Is there anybody who can help me at the post: Domoticz Install and update results in Error

I'm stuck in it and its probably something easily to solve

With regards, Rick(1212)

[Gravityz]

are you trying to update from the running docker image(so from domoticz)
do not know that will work.

updating docker containers can be done way easier and without the loss of your previous(working) container

from the synology user interface goto docker-container and
select the domoticz container
stop it
rename it to domoticz-old
goto register
find domoticz/domoticz image
download it(it will replace the current image with the new one)
go back to the old container domoticz-old
choose settings duplicate
name it domoticz
start the container

voila you have the latest domoticz running.
you can always go back to your old container because you have that one as well

[Chris12]

Thanks for this step-by-step guide to get domoticz running inside a docker container.
Just managed to install the domoticz docker besides my domoticz package (just use another port), so now running 2 seperate domoticz on my NAS.

Some thing noticed in the logfile:

3 of my scripts are showing this error:

Code: Select all

2021-05-05 20:56:07.398 Error: EventSystem: problem writing file: /opt/domoticz/userdata/scripts/dzVents/generated_scripts/Monit-status-data.lua
2021-05-05 20:56:07.398 Error: EventSystem: problem writing file: /opt/domoticz/userdata/scripts/dzVents/generated_scripts/VPN Status.lua
2021-05-05 20:56:07.398 Error: EventSystem: problem writing file: /opt/domoticz/userdata/scripts/dzVents/generated_scripts/Luftdaten.lua 

These script are restored as part of the backup. Do they need to be changed permissions or something?

Also some of my inside LAN devices are not updated:
- daikin Airconditioning with LAN (HTTP) interface (port 80)
- luftdaten sensor (maybe caused by the above script issue as well? The script is just an GET of the data.json of the sensor)

Is this because I have port 80 not defined in the ports of docker? (I use port 8085 for domoticz)
I checked but I cannot define the port mappings any more ("port settings are not required when using the same network as Docker host" message is shown at the port settings tab, maybe caused by selecting the checkbox in the network tab when installing the docker?)

[Chris12]

Solved the script write errors with some help on this forum
(just create the directory inside the created docker: /volume1/docker/domoticz/scripts/dzVents/generated_scripts, and restart the container)

The only thing not working (yet) is the Daikin airconditioning, which is using the domoticz plugin found in the list.

[WimR]

Great Guide.

Got my install working (RFX, Zwave, Easywave) + Plugins and scripts.

Thx for the Guide

[ArjenvM]

are you trying to update from the running docker image(so from domoticz)
do not know that will work.

updating docker containers can be done way easier and without the loss of your previous(working) container

from the synology user interface goto docker-container and
select the domoticz container
stop it
rename it to domoticz-old
goto register
find domoticz/domoticz image
download it(it will replace the current image with the new one)
go back to the old container domoticz-old
choose settings duplicate
name it domoticz
start the container

voila you have the latest domoticz running.
you can always go back to your old container because you have that one as well

Thanks for the update guide. Worked great. Never did a domoticz update went that fast.

[Gravityz]

thanks.
this is the reason i love docker so much.
you can play around testing things without the risk of screwing things up.

one important thing to mention.
I know domoticz sometimes updates it's database version to a new version.
if this happened and you go back from a new version to an older version domoticz might complain about it and things do not work.
if this is the case you need to replace the database with a version which was used at the time before you upgraded it.
This is where you thank yourself that you enabled automatic backup's

so
ALWAYS enable automatic backups
ALWAYS make a backup of the database(from domoticz) BEFORE you upgrade anything

This has nothing to do with docker but because docker makes life so much easier people tend to forget that they still can get into trouble.

i still did not switch from the Jadahl package (because the current package is running great) but instead i am ironing out every possible bug i find (like the paths outside docker, making copies of docker images/containers etc)

commands to make a copy of your current domoticz image
• docker ps -a
• make copy with new image name
• docker commit [CONTAINER_ID] [new_image_name]
• example docker commit a94eb9694608 domoticz-curl-nmap:13188

commands to make a copy of your working domoticz container(create the path /volume1/docker/images or other path)
• docker save domoticz/domoticz:latest | gzip >/volume1/docker/images/domoticz13149-curl-nmap.tar.gz
advantages of making a copy of the container are that it preserves the :latest tag.
this way you can restore a container from your backup and still use the procedure to upgrade it later

are you trying to update from the running docker image(so from domoticz)
do not know that will work.

updating docker containers can be done way easier and without the loss of your previous(working) container

from the synology user interface goto docker-container and
select the domoticz container
stop it
rename it to domoticz-old
goto register
find domoticz/domoticz image
download it(it will replace the current image with the new one)
go back to the old container domoticz-old
choose settings duplicate
name it domoticz
start the container

voila you have the latest domoticz running.
you can always go back to your old container because you have that one as well

Thanks for the update guide. Worked great. Never did a domoticz update went that fast.

[GJKNL]

Works great! Thanks. Zwave and rfx recognized. How to use the Conbee2 (deConz) with domoticz in Docker-container?

I don't know Docker, but probably will be better to use another docker just for deconz ? https://github.com/marthoc/docker-deconz
Take care, never update the firwmare using docker.

I have both Domoticz and deCONZ running in two seperate containers. But, I cannot get the deCONZ-plugin running in Domoticz. Please, who can give me some help? Containers are running on Synology 218+

[Thorgal789]

I have both Domoticz and deCONZ running in two seperate containers. But, I cannot get the deCONZ-plugin running in Domoticz. Please, who can give me some help? Containers are running on Synology 218+

It s a container issue, a plugin issue, or a domoticz issue ?

[GJKNL]

I have both Domoticz and deCONZ running in two seperate containers. But, I cannot get the deCONZ-plugin running in Domoticz. Please, who can give me some help? Containers are running on Synology 218+

It s a container issue, a plugin issue, or a domoticz issue ?

I do not see deCONZ plugin in Domoticz, But it is in the plugin folder. So, what do I miss to communicate between Domoticz and deConz which both are running in their container? In other words, how to install the plugin in Domoticz on docker?

[Thorgal789]

what do I miss to communicate between Domoticz and deConz which both are running in their container

You are not here yet, you need first to install the deconz plugin, and after that configure the plugin to connect to deconz.

I do not see deCONZ plugin in Domoticz

Unfortunately, I don't know how to install plugin in docker installation, can be from python, but I don't think it s the problem on docker container. For me it s more a folder issue, on docker, folders paths are more "exotic" than on classic OS.
Take a look on domotics logs on startup, can be usefull.

[GJKNL]

what do I miss to communicate between Domoticz and deConz which both are running in their container

You are not here yet, you need first to install the deconz plugin, and after that configure the plugin to connect to deconz.

I do not see deCONZ plugin in Domoticz

Unfortunately, I don't know how to install plugin in docker installation, can be from python, but I don't think it s the problem on docker container. For me it s more a folder issue, on docker, folders paths are more "exotic" than on classic OS.
Take a look on domotics logs on startup, can be usefull.

Domoticz log says: Error: deCONZ: (deCONZ) failed to load 'plugin.py', Python Path used was ':/usr/lib/python37.zip:/usr/lib/python3.7:/usr/lib/python3.7/lib-dynload:/usr/local/lib/python3.7/dist-packages:/usr/lib/python3/dist-packages:/usr/lib/python3.7/dist-packages'.
2021-05-28 09:33:42.200 Error: deCONZ: (deCONZ) Module Import failed, exception: 'ModuleNotFoundError'
2021-05-28 09:33:42.200 Error: deCONZ: (deCONZ) Module Import failed: ' Name: plugin'
2021-05-28 09:33:42.200 Error: deCONZ: (deCONZ) Error Line details not available.

[Thorgal789]

Perhaps viewtopic.php?t=21157
When you have

2021-05-28 09:33:42.200 Error: deCONZ: (deCONZ) Module Import failed: ' Name: LIBS'

The problem is from the python library LIBS but for yours

2021-05-28 09:33:42.200 Error: deCONZ: (deCONZ) Module Import failed: ' Name: plugin'

I think it s something generic

Try to check used libs

Code: Select all

sudo -H pip3 install requests
sudo -H pip3 install json

[smaus]

Unfortunately I have this problem, when I want to change something in my settings or turn something on or off on my hardware, I get the following message Problem Update Hardware en docker domotics stops en start again

Does anyone know how I can remedy this?

Thank you very much for any help.

[waltervl]

From instructions in first topic: Did you do:

- Check 'run as admin' (or something similar, in dutch it is 'Uitvoeren met hoge machtiging)

If yes, what does the log file show on errors?

[eddieb]

Hey guys,
I am running this docker image for a while on my test environment. No big problems so far.
mounting userdata worked and gives persistant data and auto upgrading with watchtower !

BUT, I want to enable logging to a file, I noticed that domoticz.sh is in /opt/domoticz/domoticz.sh AND in userdata/domoticz.sh
the one in userdata seems ignored..

Do I need to enable logging in /opt/domoticz/domoticz.sh or should the userdata version work ?

[smaus]

From instructions in first topic: Did you do:

- Check 'run as admin' (or something similar, in dutch it is 'Uitvoeren met hoge machtiging)

If yes, what does the log file show on errors?

run as admin is on

in my domoticz log stands this:

Code: Select all

2021-06-05 11:23:26.365 Sunrise: 05:20:00 SunSet: 21:57:00
2021-06-05 11:23:26.365 Day length: 16:37:00 Sun at south: 13:39:00
2021-06-05 11:23:26.365 Civil twilight start: 04:32:00 Civil twilight end: 22:46:00
2021-06-05 11:23:26.365 Nautical twilight start: 03:15:00 Nautical twilight end: 00:02:00
2021-06-05 11:23:26.365 There is no astronomical twilight in the space of 24 hours
2021-06-05 11:23:26.383 Active notification Subsystems: (0/13)
2021-06-05 11:23:26.387 Starting shared server on: :::6144
2021-06-05 11:23:26.360 Status: Domoticz V2021.1 (build 13277) (c)2012-2021 GizMoCuz
2021-06-05 11:23:26.360 Status: Build Hash: 16492be90, Date: 2021-05-25 07:52:07
2021-06-05 11:23:26.360 Status: Startup Path: /opt/domoticz/
2021-06-05 11:23:26.382 Status: PluginSystem: Started, Python version '3.7.3'.
2021-06-05 11:23:26.384 Status: WebServer(HTTP) started on address: :: with port 8085
2021-06-05 11:23:26.387 Status: RxQueue: queue worker started...
2021-06-05 11:23:26.387 Status: TCPServer: shared server started...
2021-06-05 11:23:26.387 Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Address already in use
2021-06-05 11:23:26.387 Error: WebServer(SSL) check privileges for opening ports below 1024
2021-06-05 11:23:28.388 Status: NotificationSystem: thread started...
2021-06-05 11:23:28.389 Status: EventSystem: reset all events...
2021-06-05 11:23:28.389 Status: EventSystem: reset all device statuses...
2021-06-05 11:23:28.402 Status: Python EventSystem: Initializing event module.
2021-06-05 11:23:28.402 Status: EventSystem: Started
2021-06-05 11:23:28.402 Status: EventSystem: Queue thread started...

and in my docker domoticz log:

domoticz-domoticz_2
date,stream,content

Code: Select all

2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.429  Status: EventSystem: Queue thread started...
2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.429  Status: EventSystem: Started
2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.428  Status: Python EventSystem: Initializing event module.
2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.416  Status: EventSystem: reset all device statuses...
2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.416  Status: EventSystem: reset all events...
2021-06-05 09:12:37,stdout,2021-06-05 11:12:37.415  Status: NotificationSystem: thread started...
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.415  Status: RxQueue: queue worker started...
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.415  Status: TCPServer: shared server started...
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.415  Starting shared server on: :::6144
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.414  [1;31mError: WebServer(SSL) check privileges for opening ports below 1024[0;0m
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.414  [1;31mError: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Address already in use[0;0m
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.411  Status: WebServer(HTTP) started on address: :: with port 8085
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.411  Active notification Subsystems: (0/13)
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.408  Status: PluginSystem: Started, Python version '3.7.3'.
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.392  There is no astronomical twilight in the space of 24 hours
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.392  Nautical twilight start: 03:15:00 Nautical twilight end: 00:02:00
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.392  Civil twilight start: 04:32:00 Civil twilight end: 22:46:00
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.392  Day length: 16:37:00 Sun at south: 13:39:00
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.392  Sunrise: 05:20:00 SunSet: 21:57:00
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.381  Status: Startup Path: /opt/domoticz/
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.380  Status: Build Hash: 16492be90, Date: 2021-05-25 07:52:07
2021-06-05 09:12:35,stdout,2021-06-05 11:12:35.380  Status: Domoticz V2021.1 (build 13277) (c)2012-2021 GizMoCuz
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #16 /lib/x86_64-linux-gnu/libc.so.6 : clone + 0x3f [0x7f2ae10ea4cf][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #15 /lib/x86_64-linux-gnu/libpthread.so.0 :  + 0x7fa3 [0x7f2ae1365fa3][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #14 /opt/domoticz/domoticz :  + 0xa039df [0x559b25ad99df][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #13 /opt/domoticz/domoticz :  + 0x3f4c98 [0x559b254cac98][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #12 /opt/domoticz/domoticz : http::server::server_base::run() + 0x52 [0x559b258ee3c2][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #11 /opt/domoticz/domoticz : boost::asio::detail::scheduler::run(boost::system::error_code&) + 0x4e8 [0x559b255c2c78][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #10 /opt/domoticz/domoticz :  + 0x7e371e [0x559b258b971e][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #9  /opt/domoticz/domoticz : http::server::connection::handle_read(boost::system::error_code const&, unsigned long) + 0x619 [0x559b258b4b89][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.056  [1;31mError: #8  /opt/domoticz/domoticz : http::server::cWebemRequestHandler::handle_request(http::server::request const&, http::server::reply&) + 0x9b6 [0x559b258c5ab6][0;0m"
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #7  /opt/domoticz/domoticz : http::server::cWebem::CheckForPageOverride(http::server::_tWebEmSession&, http::server::request&, http::server::reply&) + 0xaf6 [0x559b258bfdb6][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #6  /opt/domoticz/domoticz : http::server::CWebServer::PostSettings(http::server::_tWebEmSession&, http::server::request const&, http::server::reply&) + 0x91a [0x559b254f9b1a][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #5  /opt/domoticz/domoticz : http::server::CWebServerHelper::LoadUsers() + 0x24 [0x559b2556a534][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #4  /opt/domoticz/domoticz : http::server::CWebServer::LoadUsers() + 0x80 [0x559b25501d00][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #3  /opt/domoticz/domoticz : http::server::cWebem::ClearUserPasswords() + 0xd [0x559b258bd9ad][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #2  /lib/x86_64-linux-gnu/libpthread.so.0 :  + 0x12730 [0x7f2ae1370730][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #1  /opt/domoticz/domoticz : signal_handler(int, siginfo_t*, void*) + 0x205 [0x559b25488115][0;0m
2021-06-05 09:12:34,stdout,2021-06-05 11:12:34.055  [1;31mError: #0  /opt/domoticz/domoticz :  + 0x3b16b3