@Cr4z33
MMM-RTSPStream is quite old and the author himself doesn’t use it anymore and recommend indeed other modules.
So it a a wise advice from Sam (@sdetweil ) to use MMM-Mplayer …
This one still have an active discussion here .

Ralf

@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 …)

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

@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 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

@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

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

Just spontaneous thoughts about your issue - maybe misleading …

Regards,
Ralf

@chris47803 :-)

@kusselin said

One question: Do you have Netatmo installed and running at home as hardware and searching in MM…?

Nope, Netatmo not used by me …

Regards,
Ralf

@kusselin
Sorry I‘m out here because I do not have any experience with proxmox containers.

But in general, what Sam means is that your last log-output indicates that you had tried to start a seond instance of MagicMirror -which fails.
So I guess it is necessary to identify the primary instance and look for logs there .
What I have seen in addition but cannot justify: Your above output looks like you‘re working with root permission.

root@magicmirror-live:/opt/magicmirror# npm run server

As far as I remember correctly, this may causes difficulties as well - at least I remember to read something like this - context was different and it‘s possible that this doesn‘t apply to container-environments …

Good luck!
Regards,
Ralf

@kusselin Are there any error messages?
Check log as well as dev-console …
“Netatmo load” could be an indicator that module stucks in the middle of nowhere…

Regards,
Ralf