Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream

sdetweil

@wishmaster270 i’ve come to the conclusion

the doorbell itself does not publish to mqtt
MqttBridge did not get any message from its subscribe

he is going to try to build a HomeAssistant automation, as it CAN see the doorbell button thru its integration

Cr4z33

@wishmaster270 thanks for spending some time on my issue although you’re busy.
As sdetweil said he’s already helping me into this. 🙂

@sdetweil my bad, my bad and again my bad! 😓

I was going to tryout your method when I realized I actually never checked deeply what was outputting npm start… There’s A LOT of doorbell data being captured by MMM-MQTTbridge indeed! 🤦🏼

You can see here the output.

Can you see at this point (maybe) some additional data that needs to be added to mqttDictionary.js or do you still believe I should go your way (HA, automation, etc.)?

While waiting for your kind reply I will play at trying your method. 😁

rkorell

@Cr4z33 Good afternoon,
I do not have the time to dig too deep into MMM-MQTTbridge …
But what I see checking your console logfile and compare this to your first posting:
You obviously had managed that the MQQT message arrives and is acknowledged.

.
The message you receive is:

{
    "Action": "Pulse",
    "Code": "Invite",
    "Data": {
        "CallID": "5",
        "IsEncryptedStream": false,
        "LocaleTime": "2025-04-30 10:40:43",
        "LockNum": 2,
        "RealUTC": 1746002443,
        "SupportPaas": false,
        "TCPPort": 37777,
        "UTC": 1746006043.0,
        "UserID": "101"
    },
    "Index": 0,
    "deviceType": "DHI-VTO3311Q-WP",
    "serialNumber": "****"
}

This is what you trying to capture in your mqttDisctionary.js
I’m not 100% sure if you

catch the right data-value : - is your jsonpath correct?
is “notiID” the right place for the module name you try to reach?

Just spontaneous thoughts about your issue - maybe misleading …

Regards,
Ralf

Cr4z33

@rkorell hi it’s a good question indeed.

However too bad that I am not skilled enough to know the answer lol that’s why I am posting here asking for help! 😂

Let’s see if @sdetweil or someone else can find out.

sdetweil

@Cr4z33 woohoo, i see the data, now its MQTTBridge configuration, and that part i dont know (yet)

rkorell

@Cr4z33 OK, I guess you have to dig a little bit deeper into MMM-MQTTbridge …
You may give MQTTbind a try - this seems to be easier and more straightforward…

In addition: I’m not really sure if your RTSP-play module is able to react on notification - had you double-checked this? (If it does not react on notification, you cannot be successful…).

Regards,
Ralf

rkorell

@rkorell @Cr4z33 with writing the above I’ve just noticed:
Your RTSP module is NOT “RTSP-play” but "MMM-RTSPStream" !
This should be your first trial then in your mqttDisctionary.js …

sdetweil

@rkorell MMM-MPlayer should work for displaying on notification

rkorell

@sdetweil cool.
had played around with this and it was frickling to position - but worth a try … :-)

rkorell

@rkorell said in Need help with MMM-MQTTbridge not "communicating" with MMM-RTSPStream:

@rkorell @Cr4z33 with writing the above I’ve just noticed:
Your RTSP module is NOT “RTSP-play” but "MMM-RTSPStream" !
This should be your first trial then in your mqttDisctionary.js …

@Cr4z33 just found “source” : you have copied this configuration .
But I bet you have to place the module name as “notiID” …
this is not “RTSP-play” but “MMM-RTSPStream” …
Regards,
Ralf

(Pay attention : it is highly probably case-sensitive …)