MQTT Publish Errors....

[ChirpyTurnip]

Hi,

I've been steadily chipping away at getting BI working with some new cameras that I've bought off EmpireTechAndy but I've got a few teething problems with BI - I'm to going to post here for some help....hopefully someone can point me in the right direction to start squashing these bugs in my setup.

The first problem I have is repeated "MQTT: Publish error 12" messages when BI wants to push a MQTT message to Home Assistant - this happens about 20 - 30 times a day and affects randomly all cameras.

Stuff you should know:

1. HA and BI are in different subnets / VLANs, access is via an OPNSense FW
2. It works 99.9% of the time with no errors
3. The MQTT setup in the global setting/options works and tests complete successfully
4. There are no errors on the HA side

An example log (as emailed out by BI) reads as follows:

3/09/2023 9:00:00 pm     Driveway:     ONVIF Event: RuleEngine/FieldDetector/ObjectsInside (IsInside="true") (91)
3/09/2023 8:59:41 pm     Driveway:     MOTION_AH (109)
3/09/2023 8:59:37 pm     Front:     MOTION_AH (87)
3/09/2023 8:59:30 pm     Rear:     MOTION_H (10)
3/09/2023 8:58:25 pm     Rear:     AI: Alert canceled [nothing found] 93ms (26)
3/09/2023 8:58:25 pm     Rear:     MOTION_AH (24)
3/09/2023 8:58:05 pm     Conservatory:     AI: Alert canceled [nothing found] 100ms (325)
3/09/2023 8:57:57 pm     Conservatory:     MOTION_CH (79)
3/09/2023 8:51:12 pm     Front:     AI: Alert canceled [nothing found] 52ms (77)
3/09/2023 8:51:11 pm     Front:     MOTION_EH (7)
3/09/2023 8:48:23 pm     local_console:     [::]: Logout, 4:24 (2)
3/09/2023 8:48:22 pm     App:     Console: disconnected (2)
3/09/2023 8:46:10 pm     Pembroke_-_Exterior:     Delete: nothing to do [3.02T/3.02T, 1.61T free] (186)
3/09/2023 8:41:09 pm     Pembroke_-_Interior:     Delete: nothing to do [167/168 hrs, 55.7G/500.0G, 1.61T free] (108)
3/09/2023 8:41:09 pm     Pembroke_-_Alerts:     Delete: nothing to do [1439/8760 hrs, 2.82G/50.0G, 998.6G free] (67)
3/09/2023 8:40:54 pm     Garage_Front:     EXTERNAL (RuleEngine/CellMotionDetector/Motion)
3/09/2023 8:40:54 pm     Garage_Front:     ONVIF Event: RuleEngine/CellMotionDetector/Motion (5)
3/09/2023 8:40:29 pm     Garage_Rear:     MQTT: Publish OK to BI/Garage_Rear/motion (9)
[B]3/09/2023 8:40:28 pm     Garage_Front:     MQTT: Publish error 12 (8)[/B]
3/09/2023 8:40:27 pm     Garage_Front:     AI: car:70% (13)
3/09/2023 8:40:26 pm     Garage_Front:     MOTION_EH
3/09/2023 8:40:15 pm     Garage_Front:     EXTERNAL (IsMotion="true")
3/09/2023 8:40:11 pm     Garage_Rear:     AI: person:76% (18)
3/09/2023 8:40:11 pm     Garage_Rear:     MOTION_BH
3/09/2023 8:39:48 pm     Garage_Rear:     MOTION_AH (2)
3/09/2023 8:39:40 pm     Garage_Front:     MOTION_BDH
3/09/2023 8:38:58 pm     Garage_Rear:     MOTION_BCH
3/09/2023 8:37:58 pm     Garage_Rear:     MOTION_DH
3/09/2023 8:37:20 pm     Driveway:     MQTT: Publish OK to BI/Driveway/motion (5)
3/09/2023 8:37:07 pm     Conservatory:     MOTION_BH (71)

Any thoughts on where to poke and prod to figure out what the issue is?

Thanks!
CP.

 

[The Automation Guy]

It seems that error 12 is related to the MQTT buffer size. The suggested fix is to increase the buffer size. mqtt_simple example: mqtt_connect error -12 - Nordic Q&A - Nordic DevZone - Nordic DevZone

 

[ChirpyTurnip]

Hmmm....I'm not so sure.....on my end I'm using Mosquitto Broker on Home Assistant (mosquitto.conf man page) and there's little reference to buffers there...and most of the limits for everything else seem pretty generous. When I'm testing it all seems to work. From the HA end I get:

2023-09-06 11:53:05: New connection from 192.168.6.2:61724 on port 1883.
2023-09-06 11:53:05: New client connected from 192.168.6.2:61724 as blue_iris (p2, c1, k20, u'mqtt_bi').
2023-09-06 11:53:07: Client blue_iris disconnected.
2023-09-06 11:53:08: New connection from 192.168.6.2:61735 on port 1883.
2023-09-06 11:53:08: New client connected from 192.168.6.2:61735 as blue_iris (p2, c1, k20, u'mqtt_bi').
2023-09-06 11:53:14: Client blue_iris disconnected.
2023-09-06 11:53:14: New connection from 192.168.6.2:61747 on port 1883.
2023-09-06 11:53:14: New client connected from 192.168.6.2:61747 as blue_iris (p2, c1, k20, u'mqtt_bi').
2023-09-06 11:53:36: Client blue_iris disconnected.
2023-09-06 11:53:36: New connection from 192.168.6.2:61782 on port 1883.
2023-09-06 11:53:36: New client connected from 192.168.6.2:61782 as blue_iris (p2, c1, k20, u'mqtt_bi').

And on the BI end I get this sort of thing:

level    time    object    message
3     6/09/2023 12:07:08.547 pm    Rear                    MOTION_D>C
0     6/09/2023 12:07:13.876 pm    Rear                    AI: [ipcam-combined] person:83% [1364,550 1515,893] 65ms
0     6/09/2023 12:07:13.877 pm    Rear                    AI: person:83%
0     6/09/2023 12:07:13.906 pm    Rear                    MQTT: Publish OK to BI/Rear/motion
0     6/09/2023 12:07:14.036 pm    Rear                    MQTT: Publish OK to BI/Rear/alert-image-b64
0     6/09/2023 12:07:14.108 pm    Rear                    MQTT: Publish OK to BI/Rear/attributes
0     6/09/2023 12:07:27.935 pm    Rear                    MQTT: Publish OK to BI/Rear/motion

So it all works...and then randomly the "publish errors"......I will keep an eye on the log....but I think it must be something else... :-(

 

[ChirpyTurnip]

I'm still getting bombarded with MQTT publish errors....20-30 emails a day....is there nothing I can do to at least diagnose the problem? Everything seems to work and yet it insists on spewing forth error messages.... :-(