Domoticz Community Forum - Support & Discussion

ferrosk

The issue is fixed in the plugin version 0.9.7

ferrosk

Hi,

I encountered the same issue after upgrading to Domoticz 2026.2 (using the official Docker image):

2026-06-21 11:15:09.943 Status: iDetect: Entering work loop.
2026-06-21 11:15:09.943 Status: iDetect: Started.
2026-06-21 11:15:09.998 Status: iDetect: Initialized version 2.4, author 'ESCape ...

ferrosk

Hi,

Version: Domoticz 2026.1 and above
Platform: any
Plugin/Hardware: Domoticz Volumio Plugin
Description:

I developed a Volumio plugin approximately four years ago. Since Domoticz version 2022.1, the icon state behavior for switch devices—displaying a grey icon when not connected to the Volumio ...

ferrosk

If you use Zigbee2MQTT, you can find information about both type of adapters in section for supported adapters . E version (with EFR32MG21 chip) should work too but still has experimental support in Zigbee2MQTT only. I use recommended P version (based on CC2652P chip) without issues. You can still ...

ferrosk

You can enable syslog driver for your domoticz container (add the options to docker run command or configure it in docker compose file), see https://docs.docker.com/config/containers/logging/syslog/

I use the following configuration in my docker compose file to send logs from Domoticz container to ...

ferrosk

I found it available as snap package too so very easy to install i.e. on Ubuntu

ferrosk

Hello,

for using host mode, update your docker compose files with:

add:

Code: Select all

...
services:
  <service-name>:
    ...
    network_mode: host
    ...

and remove

Code: Select all

    ...
    networks:
      - <network>
    ...
    ports:
      - '<port>:<port>'
     ...

ferrosk

Just for reference. We fixed the problem via teamviewer.

When tried to start without using config file (default config):
sudo -u mosquitto /usr/sbin/mosquitto
it started OK.

When tried to start with using config file:
sudo -u mosquitto /usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf

it ...

ferrosk

The log is gone, nohting in there.
I can give you teamviewer access?

ok you can send me ID/pass in Private Message

ferrosk

do you have config file /etc/mosquitto/mosquitto.conf present?

What if you you start it manually with default config (without using above config file):

sudo -u mosquitto /usr/sbin/mosquitto

ferrosk

according to timestamp (1671284340), the logs from last run are the following:

1671284340: mosquitto version 2.0.12 starting
1671284340: Config loaded from /etc/mosquitto/mosquitto.conf.

looks like no errors... strange

try stop / remove the log / start again and check status/logs:

sudo systemctl ...

ferrosk

as I can see now it fails with return code 3 which is different as before:

Process: 824 ExecStart=/usr/sbin/mosquitto -c /etc/mosquitto/mosquitto.conf (code=exited, status=3)

so check the log file /var/log/mosquitto/mosquitto.log what is the error now

ferrosk

hello,

Check the content of /etc/rc.local file. Maybe you have a command to start mosquitto in it. In that case system tries to start one mosquitto by rc-local.service and another mosquitto by mosquitto.service. If it mosquitto command is present in /etc/rc.local comment it out or remove the line ...

ferrosk

hello,

Apparently you have other mosquitto process already started/running and using port 1883 when you try to start mosquitto.service in parallel and fails because the port is already in use. Try to identify service which started the process using port 1883:

find PID of the process which is using ...

ferrosk

Do you have this log file /var/log/mosquitto/mosquitto.log? Check if there are any errors...

ferrosk

these messages:

1671219391: Opening ipv4 listen socket on port 1883.
1671219391: Error: Address already in use
1671219391: Opening ipv6 listen socket on port 1883.
1671219391: Error: Address already in use

means that some other service is already using port 1883 on your system so mosquitto cannot ...

ferrosk

If you read my previous posts you should understand the file is generated automatically. You should not create it manually (you cannot just guess its content). Maybe you missed some step or previous step did not complete successfully and you didn't notice...

ferrosk

after that i preform:
$ ./domoticz
but do not see my changes i have added at the log line.
I think i am missing a step.

It should work like that. When you start re-built domoticz, in startup logs, do you see "-modified" flag added in "Build Hash:" message? It indicates that you really started ...

ferrosk

the second think is, OZW works perfekt on my setup. no any kind of problems, why i need to switch do other solution and risk that not all wil work like now ?

You can still use it while is available in Domoticz 2022.2 but it may be removed in future Domoticz releases because OZW is no longer ...

ferrosk

if domoticz is running as root and you need execute the command as 'pi' user you can try modify the script:

Code: Select all

#!/bin/bash
sudo -u pi miiocli roborockvacuum --model rockrobo.vacuum.v1 --ip 192.168.1.32 --token 5061---------------------366f start

Domoticz Community Forum - Support & Discussion

Search found 47 matches

Re: Volumio plugin - icons issue since 2026.1

Re: Python plugin: Presence detection from wireless router

Volumio plugin - icons issue since 2026.1

Re: sonoff dongle -P vs -E?

Re: Domoticz, docker and syslog

Re: MQTT Explorer docker image available

Re: zwavejsui -> mosquitto

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: MQTT: Failed to start, return code: 14/Connection refused (Check IP/Port)

Re: problems with mqtt

Re: 2022.2 Domoticz sources not compiling

Re: Change Hardware .cpp file

Re: Easiest way to migrate Openzwave to ZWave-JS-UI

Re: python-miio sh script did not execute in domoticz