Page 1 of 1

MQTT Messages not considered as "Status" messages

Posted: Sunday 18 December 2022 21:46
by GooRoo
Hello,

I am relatively new to domoticz.
I am using domoticz to subscribe to MQTT events on thethings network, and once received, a notification is sent using Pushsafer.
On my first domoticz instance, it works fine.
On my second domoticz instance, domoticz is able to see the messages, but does not send the notification to pushsafer.

On the first instance, the MQTT logs are highlighted in green as status messages.
On my second instance, the MQTT logs appear, but are not highlighted as "status" messages
What could be causing this difference in behaviour? and how do I fix it?

Re: MQTT Messages not considered as "Status" messages

Posted: Monday 19 December 2022 10:27
by waltervl
What is the difference between those 2 domoticz instances with regard to MQTT implementation?

Re: MQTT Messages not considered as "Status" messages

Posted: Wednesday 21 December 2022 0:31
by GooRoo
Hello,
In domoticz, the configurations are the same.
I am not sure if there is any difference at the OS level.
I have attached screenshots from each instance.
Both are subscribed to the same event in thethingsnetwork.

Re: MQTT Messages not considered as "Status" messages

Posted: Wednesday 21 December 2022 0:56
by waltervl
Strange. And also the same Domoticz versions and same hardware (RPi 32, RPi 64, windows orLinux X86)?

Re: MQTT Messages not considered as "Status" messages

Posted: Wednesday 21 December 2022 1:05
by GooRoo
The only visible difference is the domoticz version. "2022,1" for the working version and "2022,2" for the one that is not working.
Is there a way to define/configure what messages domoticz considers as a "status" message?

Re: MQTT Messages not considered as "Status" messages

Posted: Wednesday 21 December 2022 1:21
by waltervl
I don't think so. There have been some changes in MQTT between those versions so perhaps you ran into an issue.
As I do not use MQTT and definitely not TTN-MQTT it is better you make an issue on the GitHub repository. Best with an example mqtt payload that should reproduce your issue.

Re: MQTT Messages not considered as "Status" messages

Posted: Thursday 22 December 2022 11:02
by GooRoo
waltervl wrote: Monday 19 December 2022 10:27 What is the difference between those 2 domoticz instances with regard to MQTT implementation?
I forgot to respond to part of this question:
Working system: raspberry pi 4, buster
Other systems I set up that do not work: ubuntu 20.04 vm with domoticz 2022.2, fedora 37 vm with domoticz 2022.1, anothe raspberry pi 4 (buster).

All the devices see the MQTT events and report them in the domoticz log.
Only the first raspberry reports the MQTT events as "STATUS" messages. I cannot remember what I did when I installed the first machine and I have been unable to replicate it.

How does domoticz decide what is an "info" message and what is a "status" message? Is there a setting/config for this?

Re: MQTT Messages not considered as "Status" messages

Posted: Thursday 22 December 2022 18:56
by waltervl
As far as I know there is no setting for this.
I think it is a difference in usage between 2022.1 and 2022.
The status is only a log implementation, it should not differ in interpretation of the mqtt payload.

Perhaps you can try to send a payload manually with mosquitto_pub to check behavior in switch command between the domoticz environment.

It is strange that pushsafer is not triggered on the other environments. Is pushsafer implemented the same? Are the devices updated on all systems based on the mqtt messages?