MQTT: not every channel gets subscribed

Add-ons Bindings
,
1

running OH5.0.2 on docker.

I’m using node-RED for connecting Amazon Echo-devices to openHAB as a work-around currently and my Echos. So i linked my old items to the additional mqtt-channels.
But I don’t understand the following:

  1. I added all commandTopics (which work all)
  2. I added all stateTopics for lastVoiceCommand (which work on only one channel?)

So, my things-config is like that:

UID: mqtt:topic:synology:OH2Alexa
label: MQTT openHAB2Alexa
thingTypeUID: mqtt:topic
configuration: {}
bridgeUID: mqtt:broker:synology
channels:
  - id: speakBadezimmer
    channelTypeUID: mqtt:string
    label: Sprich Badezimmer
    description: ""
    configuration:
      qos: 2
      commandTopic: services/OH2Alexa/Echo Badezimmer/speak
  - id: speakvolumeBadezimmer
    channelTypeUID: mqtt:dimmer
    label: Lautstärke TTS Badezimmer
    configuration:
      qos: 2
      commandTopic: services/OH2Alexa/Echo Badezimmer/speakvolume
  - id: lastVoiceCommandBadezimmer
    channelTypeUID: mqtt:string
    label: letzter Sprachbefehl Badezimmer
    configuration:
      stateTopic: services/OH2Alexa/Echo Badezimmer/state/lastVoice
  - id: speakArbeiten
    channelTypeUID: mqtt:string
    label: Sprich Arbeiten
    configuration:
      qos: 2
      commandTopic: services/OH2Alexa/Echo Arbeiten/speak
  - id: speakvolumeArbeiten
    channelTypeUID: mqtt:dimmer
    label: Lautstärke TTS Arbeiten
    configuration:
      qos: 2
      commandTopic: services/OH2Alexa/Echo Arbeiten/speakvolume
  - id: lastVoiceCommandArbeiten
    channelTypeUID: mqtt:string
    label: letzter Sprachbefehl Arbeiten
    configuration:
      stateTopic: services/OH2Alexa/Echo Arbeiten/state/lastvoice
...

In DEBUG, the logs tell me:

2025-11-17 17:19:34.610 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:speakBadezimmer
2025-11-17 17:19:34.612 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:speakvolumeBadezimmer
2025-11-17 17:19:34.612 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:lastVoiceCommandBadezimmer
2025-11-17 17:19:34.613 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:speakArbeiten
2025-11-17 17:19:34.614 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:speakvolumeArbeiten
2025-11-17 17:19:34.615 [DEBUG] [.MqttChannelStateDescriptionProvider] - Adding state description for channel mqtt:topic:synology:OH2Alexa:lastVoiceCommandArbeiten
...
2025-11-17 17:19:34.632 [DEBUG] [ab.binding.mqtt.generic.ChannelState] - Subscribed channel mqtt:topic:synology:OH2Alexa:lastVoiceCommandArbeiten to topic: services/OH2Alexa/Echo Arbeiten/state/lastvoice
2025-11-17 17:19:34.632 [DEBUG] [ab.binding.mqtt.generic.ChannelState] - Subscribed channel mqtt:topic:synology:OH2Alexa:lastVoiceCommandBadezimmer to topic: services/OH2Alexa/Echo Badezimmer/state/lastVoice
...

What I can’t solve is, that a payload to the “Echo Arbeiten” comes through, but for all others not?
I did change the bindings log-level to TRACE, but still, there’s only:

2025-11-17 17:26:19.896 [INFO ] [openhab.event.ItemStateChangedEvent ] - Item 'AMZ_EchoOffice_LetzterSprachbefehl' changed from tortilla auf die liste to just a test
...
2025-11-17 17:34:28.624 [TRACE] [.MqttChannelStateDescriptionProvider] - Providing state description for channel mqtt:topic:synology:kostal:totalPVPower

I also don’t understand all those “TRACE”-entries: “Providing state description for channel mqtt:…”?

I know, that adding spaces to topics isn’t ideal, but should work… MQTT Explorer gets it?

2

Bindings push state description information to the Items when they are linked. This is why, for some bindings, the Item already has command options for something like a remote controller or a HVAC mode Item.

I kind of hate this feature because it’s so hidden from the end users. But binding authors love it because it saves end users some configuration steps. In this case it’s not really doing anything because you’ve not configured the properties on the Channel where there would be something to push (e.g. unit).

If you get messages on “Echo Arbeiten” the space isn’t an issue. That one has a space too.

I do notice though that the topic for Echo Arbeiten is “lastvoice” but the “Echo Badezimmer” is “lastVoice”. MQTT topics are case sensitive.

1 Like
3

wow! I did copy all echos… somehow I must’ve changed! :wink:
thanks. works now, of course. :blush: