[MQTT Exporter] No longer working even if uninstalled and reinstalled

🧰 Built-In Apps and Drivers
1

I have been experimenting with the MQTT Exporter app. I had it working with Influxdb3 to export all device data. I found that there was a issue with one of the devices and went in to remove it. The page froze in the UI and i ended up having to reboot the hub. After doing it appears that MQTT isn't working at all. I am using the built in MQTT Service option

The error messages from logs are

app:24162026-03-30 07:47:30.025 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:47:15.012 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:47:07.492 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method main within 120 seconds (main)
app:24162026-03-30 07:47:00.216 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:46:45.013 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:46:30.029 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:46:15.046 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:46:00.363 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:45:45.011 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:45:37.856 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method main within 120 seconds (main)
app:24162026-03-30 07:45:30.030 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:45:15.082 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:45:00.190 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:44:45.012 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:44:30.080 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:44:15.014 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:44:00.119 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:43:45.012 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:43:30.040 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:43:15.049 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:43:00.116 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:42:45.012 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:42:39.062 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method main within 120 seconds (main)
app:24162026-03-30 07:42:30.062 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:42:15.028 PMerrorjava.lang.RuntimeException: Failed to acquire semaphore for method checkMQTTConnection within 120 seconds (checkMQTTConnection)
app:24162026-03-30 07:39:15.010 PMwarnMQTT export integration disconnected from broker.

I have tried making addtional changes and saving it. I have disabled and then re-enabled the integration. I have removed the app and then reinstalled it. I have rebooted the hub with the option to rebuild the DB. I have confirmed the user id and password

As a test i attempted a telnet from the Influxdb3 host making the MQTT call. I was able to connect to my dev hub which is still working on port 1883, but the hub i am having issues with that has the significant number of devices is just refusing the connection. It just seems like it is completely Borked non functional. Intereseting the integation is reported as running on the hub from the Integration UI.

Anyone else seen this or have any suggestions. @gopher.ny or @bobbyD do you have any ideas?

1 Like
2

I have now tried reverting to a previous backup from before i first the intalled MQTT Exporter, I reverted the Firmware to a previous version of 2.4.4. I tried both of those tasks with MQTT Exporter removed.

It just doesn't seem to want to make itself avaliable. When i try to telnet to the hub on port 1883 to test the connectivity i just get connection refused so the hub is actively not listing on that port. This is strange as it says the MQTT service is running.

I believe the only thing i haven't done is a full reset and restore from cloud backup.

3

Yes. But perhaps it is bound to port 1883 at just the loopback address. I've had weird things like that happen with other Java servers running elsewhere. And I'm presuming this is a Java MQTT daemon.

4

That seems reasonable but no way to know.

I am at a loss at this point. This is ofocurse on my C8 Pro so is the main one driving my home. The two dev hubs are still chugging away and responding. Hopefully @gopher.ny or @bobbyD can provide some advice on a way to regain functionality for this as i am out of ideas beyond a full reset.

I am not even sure that will do it. If you guys need to get into my hub let me know i will send you my hub id.

2 Likes
5

Don't do a full reset :slight_smile:
Can you PM me the hub id? I'll take a look.

3 Likes
6

You should have the Hub ID now.

No worries about the full reset, in my book that is something that only comes after you or bobby tell me it is needed :stuck_out_tongue:

I look forward to hearing what you find.

1 Like
7

Following as I'm looking at the new MQTT functionality for integrating another home controller. Super excited Hubitat is doing this.