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

[sdetweil]

@mumblebaj AND with release 2.30 or higher a message will be sent to the stderr stream that this module will not be loaded

good catch

[sdetweil]

@mumblebaj WELL… it turns out this is a false warning as _ is treated as _ in js…

I changed the position middle_center1 and got

41:01.108] [ERROR] This module configuration contains errors:
{
  "module": "MMM-RTSPStream",
  "classes": "page1",
  "position": "middle_center1",
  "disabled": false,
  "config": {
    "autoStart": false,
    "rotateStreams": true,
    "rotateStreamTimeout": 10,
    "moduleWidth": 500,
    "moduleHeight": 281,
    "localPlayer": "vlc",
    "moduleOffset": {
      "left": -170,
      "top": -125
    },
    "remotePlayer": "ffmpeg",
    "showSnapWhenPaused": false,
    "remoteSnaps": false,
    "shutdownDelay": 12,
    "stream1": {
      "name": "Videocitofono",
      "url": "rtsp://username:password@doorbellip/cam/realmonitor?channel=1&subtype=1#backchannel=0",
      "frameRate": "undefined",
      "width": 500,
      "height": 281,
      "muted": true,
      "ffmpegPort": 9999
    }
  }
}
position: must be equal to one of the allowed values

  "fullscreen_below",
  "top_bar",
  "top_left",
  "top_center",
  "top_right",
  "upper_third",
  "middle_center",
  "lower_third",
  "bottom_bar",
  "bottom_left",
  "bottom_center",
  "bottom_right",
  "fullscreen_above"
 
[2025-04-23 14:41:01.109] [WARN]  Invalid module position found for this configuration:
{
  "module": "MMM-RTSPStream",
  "classes": "page1",
  "position": "middle_center1",
  "disabled": false,
  "config": {
    "autoStart": false,
    "rotateStreams": true,
    "rotateStreamTimeout": 10,
    "moduleWidth": 500,
    "moduleHeight": 281,
    "localPlayer": "vlc",
    "moduleOffset": {
      "left": -170,
      "top": -125
    },
    "remotePlayer": "ffmpeg",
    "showSnapWhenPaused": false,
    "remoteSnaps": false,
    "shutdownDelay": 12,
    "stream1": {
      "name": "Videocitofono",
      "url": "rtsp://username:password@doorbellip/cam/realmonitor?channel=1&subtype=1#backchannel=0",
      "frameRate": "undefined",
      "width": 500,
      "height": 281,
      "muted": true,
      "ffmpegPort": 9999
    }
  }
} 

[Cr4z33]

@sdetweil sorry for being gone for so long time, but I’ve been out of town more than scheduled. 😅

So back in topic… the typo for the MMM-RTSPStream config section was done in this forum post only.

Where did you get all those warnings from?
Looking at npm start output nothing like that was displayed (on my side).

On the other hand I could see this when I launched that command with MQTTbridge log set to true:

[29.04.2025 09:57.21.030] [LOG]   [MQTT bridge] Subscribed to the topic: DahuaVTO/Invite/Event

So the module is somehow doing something, but then as I said nothing happens at button press.

[sdetweil]

@Cr4z33 as i said the \- in the position is ok,
i made the position invalid by adding a 1 at the end, then the bad position output is shown from npm start

still no activity from the button
two things

1. the event is not triggering to mqtt
2. the action in mqttbridge is not what you expected

i dont know how to debug either one

[Cr4z33]

@sdetweil it’s OK mate and thanks for having tried to help me. :)

Let’s hope someone can come up with a working solution soon.

[sdetweil]

@Cr4z33 looking further at mqttbridge it also logs receipt of the notification from the subscription

so that tells me it did not receive info from mqtt

[Cr4z33]

@sdetweil I am not quite sure that I understood.

Are you saying it’s a module’s bug or is it needed further coding I should add (somewhere)?

[sdetweil]

@Cr4z33 im saying the module will report when it receives the mqtt info. it did not report. sooooo it did not receive the info

why i do not know

[Cr4z33]

@sdetweil hmmm I see.

I wonder if there’s actually another way to see the doorbell stream when the button is pressed?

There’s a button sensor entity for it in Home Assistant.

[sdetweil]

@Cr4z33 i dont know, but MQTTBridge was not informed of the button press as you expected

is your other bridge code running? you mentioned you had some app talking to the doorbell and publishing the mqtt message

is the doorbell an mqtt device , fed thru zigbee2mqtt for homeassistant?
or is there a native integration?
i would expect the doorbell to NOT publish to mqtt directly
it would be a tiny market to add and support that code IN the doorbell firmware