I have the following issue and maybe some of you have experienced the same.
I have a TRB246 running the latest FW. My goal is to use Event Juggler with the event ‘digital input 2’ = HIGH and the action ‘MQTT’. My mqtt Broker is hiveMQ. I have the correct credentials for the connection and also included the broker certificate for the TLS connection.
Now my issue is, that when triggering the event, no mqtt message is sent to the broker. I tried many things to get this working and at some point I found this in the logs:
546 Tue Aug 19 10:47:38 2025 daemon.err event_juggler: Unable to parse section ‘2’. Dependency error ‘mqtt_certfile’
So something seems to be wrong with my certificate.
However, if I use the very same information to set up ‘data to server’, it is working perfectly fine.
On an TRB245 I have running the I/O juggler with the same configuration and that is also running fine.
So what seems to be the problem here, is it my configuration or can it be a bug in the new Firmware?
Thank you for your inquiry. Your request is currently under review and analysis. Once the evaluation is complete, I will get back to you with further information, findings, or suggestions.
In the meantime, could you clarify how you are testing the digital input (2) state change?
In addition, could you check whether other actions (for example, SMS sending) work correctly with the same event setup?
The input change is visible for me in the I/O status page and it is working fine.
The sms action does not work for me right now, I think due to an issue with my sim card provider, I am also investigating that right now.
What I had done for a test was using the DI(2) as an input and trigger for another action to set DO(3) as HIGH for 15 sec. and that was working fine, also the logread command showed the trigger and action in that case.
Thank you very much for looking into that case, I am hoping for a larger order of a customer and need to figure this out until then.
If you need any more input from me, please give me a message.
Thank you for the update. I’ve tried reproducing the described issue, but I didn’t manage to recreate it. In this case, to assist and troubleshoot this matter effectively, we’ll need to continue this process privately, because sensitive/publicly unshareable information, such as the configuration/troubleshoot file, public IP addresses, serial numbers, etc., needs to be gathered.
You should find a support request form in the inbox of the email address you used for your forum registration. Kindly fill out the form, and please reference Ticket ID: 15169 when submitting it. Once the form is completed, we’ll contact you directly via email to investigate the issue in detail and help work towards a solution.