Domoticz as container on Portainer, fail after duplicate

[njlammerts]

I have portainer running on Pi4. I Installed Domoticz using the original docker/install.
At first Domoticz seems to run ok. Ik can start/stop from portainer and also the other container seem to run ok, (Mosquitto, Zigbee2MQTT.)
As a test i stopped Domoticz, made a duplicate and started the new duplicated Domoticz. Domoticz starts ok, but is missing all the devices from the dashboard. When i look in Setup/Hardware and Setup/Devices, all the hardware and Devices are present. I refreshed/cleared browser cache but no change. Also Switches, Temperature, Utility show no devices. Restarting Domoticz, Portainer, Pi does not change it.
So i stopped the duplicate Domoticz and started the original Domoticz. Also the original Domoticz is not showing the Devices on the Dashboard, but they are Present in Setup/Hardware and Setup/Devices.
The Log file in both setting show no errors.

The reason i started using Portainer was the (told) easy way of making a copy/duplicate of Domoticz, prior to installing an update of Domoticz wich went wrong a couple of times and took lots of efford to get it running, sumtimes a complete new install loosing couple years of data

Domo1.jpg (56.3 KiB) Viewed 533 times

Domo2.jpg (136.33 KiB) Viewed 533 times

Domo3.jpg (265 KiB) Viewed 533 times

]

[waltervl]

Could be a caching issue (not likely) what happens of you open the duplicate in an incognito/private browser session?
Else check device assignment in menu Setup - Users. For an admin role the assigned devices list (right column) should be empty.

[njlammerts]

I cleaned/cleared Cache several times without succes. I tried Private Browser Session, also no succes.
Then i checked Setup/Users and saw ZigbeeMQTT API .... on the right side. It was on the Left side before the duplicate (!)
changed it back, Save and presto, there are all the devices back again. Strange thing that i dont have Zigbee device connected yet All the devices are "local" devices ....

Changed back to original Domoticz, and this works ok also. Now i will try what the effect is when i update the duplicate version to Domoticz Beta.

Domo4.jpg (140.53 KiB) Viewed 524 times

[njlammerts]

Only now i see a "limited" mesage in portainer. "Stack was created outside of Portainer" (there is no official description for installing Domoticz container inside Portainer)

Domo5.jpg (44.98 KiB) Viewed 521 times

[waltervl]

Strange that the duplicate changed the device assignments. But at least it is working.

About Portainer I have no clue. Domoticz is proposing to use docker compose. Perhaps that setup can be used into portainer. but I have no clue.

[Sjonnie2017]

Portainer only manages the docker containers and gives you the ability to do just that over a web interface. If the container starts defective it is caused by the docker settings or a malformed docker-compose yaml.

Portainer has nothing to do with this problem.

[jvdz]

When you create the container outside of portainer, with docker composer for example, you will see that message as the stack wasn't created via the Portainer webinterface.
In case you want to use portainer to create the Domoticz container, you can copy the content of the compose file and create it in portainer.
Agree there is no relation to the portainer message and any issue you see in the running docker container as docker is doing the actual work and Portainer simply a shell around it to maintain your docker environment.

[njlammerts]

Thanks for the update about portainer.
Are there more bennefits when the container is created within Portainer?

For me the main reason for using Portainer is to backup/duplicate my Domoticz enviroment before a Domoticz Update, to see if the update/new features/changes/Beta's is/are working, and after some testing, can be applied to the "production" Domoticz, to prevent a non functional Domoticz with error behaviour and loosing years of data (like my P1 energy meter and PV Solar Data)

248-1.JPG (36.57 KiB) Viewed 467 times

248-4.JPG (28.24 KiB) Viewed 467 times