MQTTAD seems to loose track on MQTT broker ???
Moderator: leecollings
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
MQTTAD seems to loose track on MQTT broker ???
Hi,
I have this strange problem.
I used to had Z2M plugin and never seen this but with MQTT AD I notice following :
When zigbee switches are added, all seems to work, I can switch the device from domoticz.
After a while, some of the switches stop responding from domoticz. I can NOT switch them anymore
I have to go to the Zigbee2MGTT screen (on port 8888 here) to switch the device and see that it is working from there...
walking over the device settings makes domoticz "remembering" that device again and all seems working again (for a couple of days)
Now I notice the same problem with some Tasmota devices.
They work OK but sending a switch command just stops working after a while. (Though the #idx is correctly and the tasmota device is working correctly from tasmoadmin and even in MQTTexplorer it looks ok.
It seems in domoticz MQTTAD looses track on what is happening in the MQTT broker ...
Anyone seen this ?
Any suggestions in how to debug this in domoticz ?
I have this strange problem.
I used to had Z2M plugin and never seen this but with MQTT AD I notice following :
When zigbee switches are added, all seems to work, I can switch the device from domoticz.
After a while, some of the switches stop responding from domoticz. I can NOT switch them anymore
I have to go to the Zigbee2MGTT screen (on port 8888 here) to switch the device and see that it is working from there...
walking over the device settings makes domoticz "remembering" that device again and all seems working again (for a couple of days)
Now I notice the same problem with some Tasmota devices.
They work OK but sending a switch command just stops working after a while. (Though the #idx is correctly and the tasmota device is working correctly from tasmoadmin and even in MQTTexplorer it looks ok.
It seems in domoticz MQTTAD looses track on what is happening in the MQTT broker ...
Anyone seen this ?
Any suggestions in how to debug this in domoticz ?
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
- heggink
- Posts: 972
- Joined: Tuesday 08 September 2015 21:44
- Target OS: Raspberry Pi / ODroid
- Domoticz version: 12451
- Location: NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
I would start by chasing the problem origin. Since you can control switches from the zb2mqtt interface, the problem either sits in your mqtt broker or at the client side interfacing with it. Use mqtt explorer to see what messages are being sent from/to the broker, try to manually insert a message using mosquitto_pub, things like that.
Docker in Truenas scale, close to latest beta
DASHTICZ π
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
DASHTICZ π
RFXCOM, zwavejs2mqtt, zigbee2mqtt,
P1 meter & solar panel
Google home, Wifi Cams motion detection
Geofence iCloud, Bluetooth & Wifi ping
Harmony hub, Nest, lots more :-)
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Hi,
I am really loosing it now.
still after a restart of domoticz about half of my zigbee devices loose connection.
In Zigbee2MQTT (port 8888) everything works fine, all devices are updated and switch commands work
In Domoticz some devices work, some do not.
can someone please point me in the direction of how to debug this ?
this is one of the switch devices this is the error in domoticz these are all the devices on that device I have several other devices not working right now, really annoying
the connection between Z2M and MQTTAD is not working properly here
I am really loosing it now.
still after a restart of domoticz about half of my zigbee devices loose connection.
In Zigbee2MQTT (port 8888) everything works fine, all devices are updated and switch commands work
In Domoticz some devices work, some do not.
can someone please point me in the direction of how to debug this ?
this is one of the switch devices this is the error in domoticz these are all the devices on that device I have several other devices not working right now, really annoying
the connection between Z2M and MQTTAD is not working properly here
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
for now, I am unable to trigger any Zigbee switch from domoticz. Other sensors from the same device seem to work
my Ikea vindstyrka is not reporting at all right now, untal latest update/reboot that worked fine for weeks
my Ikea vindstyrka is not reporting at all right now, untal latest update/reboot that worked fine for weeks
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
do you have in Zigbee2mqtt the retain enabled?
Code: Select all
device_options:
retain: true
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Where do I find that option in the :8888 interface ?
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
No idea where it it is in the GUI, I have to search like you have to.
Here it is in the manual explained: https://www.zigbee2mqtt.io/guide/config ... ce-options
You can set it per device under Device -> Settings
The one I mentioned above is for all devices set in configuration.yaml file, like I did.
Minimum is to set all battery devices to true, this way mosquitto will keep the last state in case of power down or reboot.
Here it is in the manual explained: https://www.zigbee2mqtt.io/guide/config ... ce-options
You can set it per device under Device -> Settings
The one I mentioned above is for all devices set in configuration.yaml file, like I did.
Minimum is to set all battery devices to true, this way mosquitto will keep the last state in case of power down or reboot.
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
All devices do not have retain: true
but, like I said, in Z2M all works fine, all devices and all sensors are updated and working.
but, like I said, in Z2M all works fine, all devices and all sensors are updated and working.
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
I found this error in mosquitto logging ... what does that mean ?
Code: Select all
1718701578: New client connected from 127.0.0.1 as Domoticz-MQTT-AutoDiscover740c5e22-22a4-473b-84d4-f90e87bd4c1334 (c1, k120).
1718701578: Outgoing messages are being dropped for client Domoticz-MQTT-AutoDiscover740c5e22-22a4-473b-84d4-f90e87bd4c1334.
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
So set (all) devices to retain: true and see if that solves your problem.
Retain has nothing to do with the fact that devices are working in Z2M.
It is worth a shot, it does not hurt anything.
Retain has nothing to do with the fact that devices are working in Z2M.
It is worth a shot, it does not hurt anything.
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
"Outgoing messages are being dropped for client" ---> Google it.
Your mosquitto might be mal configured.
Your mosquitto might be mal configured.
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Ok, that might have been the issue ...
restarted mosquitto and it seems to work fine now, tnx for the sugegstion
I will monitor this for the next couple of days closely
Code: Select all
cat /etc/mosquitto/conf.d/local.conf
max_queued_messages 0
I will monitor this for the next couple of days closely
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
"max_queued_messages 0" is not a good idea. The mosquitto default is 1000 and should be enough for Z2M and Domoticz.
You have to find out why there are so much messages queued.
If you add this for some time to the local.conf you might find out what is sending so much messages or is not responding.
You have to find out why there are so much messages queued.
If you add this for some time to the local.conf you might find out what is sending so much messages or is not responding.
Code: Select all
log_dest file /var/log/mosquitto.log
log_type all
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Morning,
I added the log_type all to the local.conf and now I get really a lot of logging.
So much I really have no clue where to look at.
Besides zigbee devices there are also a bunch of tasmota devices using the broker.
for now I did set max_queue_messages 5000 and that seems to work well
I added the log_type all to the local.conf and now I get really a lot of logging.
So much I really have no clue where to look at.
Besides zigbee devices there are also a bunch of tasmota devices using the broker.
for now I did set max_queue_messages 5000 and that seems to work well
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
- gizmocuz
- Posts: 2394
- Joined: Thursday 11 July 2013 18:59
- Target OS: Raspberry Pi / ODroid
- Domoticz version: beta
- Location: Top of the world
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
instead of log_type all you can add these two lines
log_type error
log_type warning
So only errors and warnings are logged
Your broker and your Domoticz system are both in your local network? And the speed between them is fast enough?
(They are connected with a cable instead of Wifi)
Also have a look at the CPU usage of both Domoticz and MQTT broker's machines
Do you connect via TLS (secure)? Does it make a difference when you make a plain connection (cpu wise)
log_type error
log_type warning
So only errors and warnings are logged
Your broker and your Domoticz system are both in your local network? And the speed between them is fast enough?
(They are connected with a cable instead of Wifi)
Also have a look at the CPU usage of both Domoticz and MQTT broker's machines
Do you connect via TLS (secure)? Does it make a difference when you make a plain connection (cpu wise)
Quality outlives Quantity!
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Broker and domoticz are both on the same RPI4
RPI connected by eth to local 1GB lan
no TLS on local machines
cpu load is normally not higher than 2, mostly under 1
RPI connected by eth to local 1GB lan
no TLS on local machines
cpu load is normally not higher than 2, mostly under 1
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
Code: Select all
2024-06-19 07:08:43 New client connected from 192.168.0.146 as DVES_452C98 (c1, k30, u'DVES_USER').
2024-06-19 07:08:43 New client connected from 192.168.0.153 as DVES_33112A (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.147 as DVES_500C91 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.150 as DVES_4FCE23 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.149 as DVES_4BF3A0 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.151 as DVES_554241 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.145 as DVES_C80778 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.152 as DVES_DAAD37 (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 192.168.0.148 as DVES_E7AF5D (c1, k30, u'DVES_USER').
2024-06-19 07:08:44 New client connected from 127.0.0.1 as mqttjs_06a0b7a1 (c1, k60).
2024-06-19 07:08:47 New client connected from 192.168.0.231 as Domoticz-MQTT-AutoDiscover04acb960-e88c-422e-9e9f-e140e27ae48b3 (c1, k120).
2024-06-19 07:08:47 New client connected from 127.0.0.1 as Domoticz-MQTT-AutoDiscover740c5e22-22a4-473b-84d4-f90e87bd4c1334 (c1, k120).
2024-06-19 07:08:48 New client connected from 192.168.0.247 as conditioner (c1, k15).
9 DVES users (Tasmota devices)
1 mqttjs (NodeRed ?)
2 MQTT-AutoDiscovery
1 conditioner (Airco unit)
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
I have a busy RPi4 but have no problems on port 1883 with the default setting on mosquitto.
It might be that some device is bursting.
Install iptraf-ng and look for traffic on port 1883
It might be that some device is bursting.
Install iptraf-ng and look for traffic on port 1883
Logic will get you from A to B. Imagination will take you everywhere.
-
- Posts: 279
- Joined: Wednesday 04 July 2018 7:48
- Target OS: Raspberry Pi / ODroid
- Domoticz version: Beta
- Location: Netherlands
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
these are the top communicators ...
all other connections to 1883 are less than 10% of these
Code: Select all
TCP Connections (Source Host:Port) βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
ββlocalhost:1883 > 41420 12365610 --A- lo
β localhost:37828 > 29423 1652544 -PA- lo
β localhost:57372 > 41134 13173332 --A- lo
β localhost:1883 > 29236 2363740 -PA- lo
Code: Select all
root@domoticz:~# netstat -aptn | grep 37828
tcp 0 0 127.0.0.1:37828 127.0.0.1:1883 ESTABLISHED 401/node-red
tcp 0 0 127.0.0.1:1883 127.0.0.1:37828 ESTABLISHED 26904/mosquitto
root@domoticz:~# netstat -aptn | grep 57372
tcp6 0 4 ::1:1883 ::1:57372 ESTABLISHED 26904/mosquitto
tcp6 28 0 ::1:57372 ::1:1883 ESTABLISHED 5848/domoticz
RPI4 Beta / Tasmota / ZigBee2MQTT / P1meter / Haier AC with Node-Red and MQTT / SolarEdge SE3500H modbus_tcp / Opentherm gateway / Plugwise Anna/Smile / ObserverIP weatherstation thru WuDirect
Feeding ADSB https://adsb.im/home
Feeding ADSB https://adsb.im/home
-
- Posts: 563
- Joined: Monday 20 March 2023 14:41
- Target OS: Raspberry Pi / ODroid
- Domoticz version:
- Location: Somewhere in NL
- Contact:
Re: MQTTAD seems to loose track on MQTT broker ???
That's a lot.
Do you have in Domoticz Hardware the MQTT Gateway "prevent loop" setting set to true?
You can investigate the Node-red flows with debug if a flow is sending too much.
With MQTT Explorer you could investigate the $SYS topic.
Do you have in Domoticz Hardware the MQTT Gateway "prevent loop" setting set to true?
You can investigate the Node-red flows with debug if a flow is sending too much.
With MQTT Explorer you could investigate the $SYS topic.
Logic will get you from A to B. Imagination will take you everywhere.
Who is online
Users browsing this forum: No registered users and 0 guests