DynamicGroupController updating members issue

[cw-kid]

@CatmanV2 said in Struggling to setup my first Tasmota device and MQTT:

MQTT Explorer is good for troubleshooting

Thanks I will check that out.

[cw-kid]

Reading the help page it shows this example config. I don't know what this channel number does? I didn't see a setting for setting a channel number in the Tasmota web UI. However I see there is a "channel" I saw in the data stream in the terminal mine mentioned channel 10. So I tried adding that also into my config.

EDIT: Current Control Channel: 10 appears to be the current 2.4GHZ WIFI channel of my router, its set to AUTO so that channel will change or "channel" in the reactor.yaml something different?

config:
    source: "mqtt://127.0.0.1:1883/"
    entities:
      shelly1_stairway:
        name: "Stairway Light"
        topic: shelly1_43DFD2
        include: shelly_relay
        channel: 0

- id: mqtt
  enabled: true
  implementation: MQTTController
  name: Mosquitto
  config:
    source: mqtt://127.0.0.1:1883
    log_topics: ['tele','stat','tasmota']  # only for testing, disable when not in use (makes big log file)
    entities:
      tasmota_fan_controller:
      name: "Tasmota Fan Controller"
      topic: fan_controller  # matches topic configured in Tasmota
      unit: 1  # relay number on the device
      include: 
          - tasmota_generic_relay
          - tasmota_sensor_temperature_humidity
      channel: 10

Didn't help however adding Channel still no new entities appearing.

Just seen this also:

"notably Tasmota, do not have MQTT retain on by default (a poor choice for IoT devices, IMO). On Tasmota devices, you can turn it on by using the PowerRetain on, SwitchRetain on, SensorRetain on and StateRetain on commands in the Tasmota console."

I will run those commands now.

[cw-kid]

A.I. just been telling me how to control the Tasmota with HTTP commands can turn on / off the relay now via HTTP if need be. This commands shows everything about the Tasmota device.

http://192.168.0.49/cm?cmnd=Status%200

{"Status":{"Module":1,"DeviceName":"Tasmota","FriendlyName":["Tasmota"],"Topic":"fan_controller","ButtonTopic":"0","Power":"0","PowerLock":"0","PowerOnState":3,"LedState":1,"LedMask":"FFFF","SaveData":1,"SaveState":1,"SwitchTopic":"0","SwitchMode":[1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ButtonRetain":0,"SwitchRetain":1,"SensorRetain":1,"PowerRetain":1,"InfoRetain":0,"StateRetain":1,"StatusRetain":0},"StatusPRM":{"Baudrate":115200,"SerialConfig":"8N1","GroupTopic":"tasmotas","OtaUrl":"http://ota.tasmota.com/tasmota32/release/tasmota32.bin","RestartReason":"Software reset CPU","Uptime":"0T15:23:32","StartupUTC":"2026-02-14T20:46:23","Sleep":50,"CfgHolder":4617,"BootCount":8,"BCResetTime":"2026-02-14T20:26:13","SaveCount":48},"StatusFWR":{"Version":"15.2.0(release-tasmota32)","BuildDateTime":"2025-12-12T10:58:29","Core":"3.3.4","SDK":"5.3.4.251205","CpuFrequency":160,"Hardware":"ESP32-D0WD-V3 v3.0","CR":"430/699"},"StatusLOG":{"SerialLog":2,"WebLog":2,"MqttLog":0,"FileLog":0,"SysLog":0,"LogHost":"","LogPort":514,"SSId":["ASUS_86_2G",""],"TelePeriod":60,"Resolution":"558180C0","SetOption":["000082AB","2805C80000000600003C5A0A192800000000","00000080","00006000","00004080","00000000"]},"StatusMEM":{"ProgramSize":2086,"Free":793,"Heap":112,"StackLowMark":3,"PsrMax":0,"PsrFree":0,"ProgramFlashSize":4096,"FlashSize":4096,"FlashChipId":"16405E","FlashFrequency":80,"FlashMode":"DIO","Features":["0809","9F9AD7DF","0015A001","B7F7BFCF","05DA9BC4","E0360DC7","480840D2","20200000","D4BC482D","810A80F1","00000814"],"Drivers":"1,2,!3,!4,!5,7,!8,9,10,11,12,!14,!16,!17,!20,!21,!24,26,!27,29,!34,!35,38,50,52,!59,!60,62,!63,!66,!67,!68,!73,!75,82,!86,!87,!88,!91,!121","Sensors":"1,2,3,5,6,7,8,9,10,11,12,13,14,15,17,18,19,20,21,22,26,31,34,37,39,40,42,43,45,51,52,55,56,58,59,64,66,67,74,85,92,95,98,103,105,109,127","I2CDriver":"7,8,9,10,11,12,13,14,15,17,18,20,24,29,31,36,41,42,44,46,48,58,62,65,69,76,77,82,89"},"StatusNET":{"Hostname":"fan-controller-7192","IPAddress":"192.168.0.49","Gateway":"192.168.0.1","Subnetmask":"255.255.255.0","DNSServer1":"192.168.0.1","DNSServer2":"0.0.0.0","Mac":"7C:87:CE:2D:3C:18","IP6Global":"","IP6Local":"fe80::7e87:ceff:fe2d:3c18%st1","Ethernet":{"Hostname":"","IPAddress":"0.0.0.0","Gateway":"0.0.0.0","Subnetmask":"0.0.0.0","DNSServer1":"192.168.0.1","DNSServer2":"0.0.0.0","Mac":"00:00:00:00:00:00","IP6Global":"","IP6Local":""},"Webserver":2,"HTTP_API":1,"WifiConfig":4,"WifiPower":16.0},"StatusMQT":{"MqttHost":"192.168.0.4","MqttPort":1883,"MqttClientMask":"DVES_%06X","MqttClient":"DVES_2D3C18","MqttUser":"DVES_USER","MqttCount":3,"MqttTLS":0,"MAX_PACKET_SIZE":1200,"KEEPALIVE":30,"SOCKET_TIMEOUT":4},"StatusTIM":{"UTC":"2026-02-15T12:09:55Z","Local":"2026-02-15T13:09:55","StartDST":"2026-03-29T02:00:00","EndDST":"2026-10-25T03:00:00","Timezone":"+01:00","Sunrise":"07:58","Sunset":"18:10"},"StatusSNS":{"Time":"2026-02-15T13:09:55","AM2301":{"Temperature":15.0,"Humidity":62.2,"DewPoint":7.8},"TempUnit":"C"},"StatusSTS":{"Time":"2026-02-15T13:09:55","Uptime":"0T15:23:32","UptimeSec":55412,"Heap":112,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":3,"Berry":{"HeapUsed":4,"Objects":50},"POWER":"OFF","Wifi":{"AP":1,"SSId":"ASUS_86_2G","BSSId":"04:D9:F5:74:C5:E0","Channel":10,"Mode":"HT40","RSSI":100,"Signal":-48,"LinkCount":2,"Downtime":"0T00:00:04"},"Hostname":"fan-controller-7192","IPAddress":"192.168.0.49"}}

[therealdb]

When asking AI, be sure to send the docs, the exact page. It will be more precise. All that said, here's my config

controllers:
  - id: mqtt
    name: MQTT
    enabled: true
    implementation: MQTTController
    config:
      # omitted...
      entities:
        # dehum
        tasmota_dehumidifier:
          name: "Dehum - sensors"
          include: tasmota_sensor_temperature_humidity
          topic: "tasmota-dehum"
          source: SI7021
        tasmota_dehumidifier_switch:
          name: "Dehum - switch"
          include: tasmota_generic_relay
          topic: "tasmota-dehum"
          unit: ""

You could probably consolidate them, but I prefer to have the switch and the sensors separated: it's easier to start and to manage them.

In you case, as per the post, topic: "tasmota-dehum" should be topic: "fan_controller", while sourceshould beAM2301`.

[toggledbits]

@cw_kid in your post here the configuration you posted is incorrect -- the indenting is invalid, and that will prevent anything from working for that entity.

Honestly, I can't at this stage really get a read on where you are. Between you jumping in with random AI changes and others commenting, your config is a moving target and I can't follow it. If you want my help, I will send you a link so you can upload your config and I can look at it and potentially fix it. Otherwise, I'll let you continue to learn on your own and seek help from others.

[cw-kid]

Clearly the problem is I don't know how to structure or write the required yaml code. Following @therealdb example above, I changed mine to this:

- id: mqtt
  name: Mosquitto
  enabled: true
  implementation: MQTTController
  config:
    entities:
      tasmota_fan_controller_temp:
        name: "Stairs Cupboard Temp"
        include: tasmota_sensor_temperature_humidity
        topic: "fan_controller"
        source: AM2301   

I could then finally see an Entity for it in MSR for the Temp sensor. But with no data values as yet its null.

That obviously only imported the DHT22 (AM230) Temp sensor part.

I then tried to add this to also include the 1 channel Relay part.

- id: mqtt
  name: Mosquitto
  enabled: true
  implementation: MQTTController
  config:
    entities:
      tasmota_fan_controller_temp:
        name: "Stairs Cupboard Temp"
        include: tasmota_sensor_temperature_humidity
        topic: "fan_controller"
        source: AM2301
      tasmota_fan_controller_relay:
        name: "Stairs Cupboard Fan"
        include: tasmota_generic_relay
        topic: "fan_controller"
        source:
        unit: "1"  

The relay part seems to be working! I pressed the "Perform" button and was able to turn on and off the relay / fan OK.

Seems I didn't need a "Source:" for the relay portion, I left that blank as I didn't know what to put in there anyway.

So just not sure why I have no data from the Temp sensor currently.

[therealdb]

@cw-kid post some screenshots from mqtt explorer. It’s easier to follow, if you want my advice.

[cw-kid]

Its working now, a wire came off the ESP board for the DHT22 which is why it was null. I connected the wire again and now I see data in MSR.

So this seems to be the now working yaml code:

- id: mqtt
  name: Mosquitto
  enabled: true
  implementation: MQTTController
  config:
    entities:
      tasmota_fan_controller_temp:
        name: "Stairs Cupboard Temp"
        include: tasmota_sensor_temperature_humidity
        topic: "fan_controller"
        source: AM2301
      tasmota_fan_controller_relay:
        name: "Stairs Cupboard Fan"
        include: tasmota_generic_relay
        topic: "fan_controller"
        unit: "1" 

And I did just install MQTT Explorer so a screen shot of that:

Thanks for everyone help, I just needed a nudge in the right direction with the MSR yaml code.

[cw-kid]

What else can I build! I have loads of spare ESP boards and sensors laying around the place, what I was using when trying out "EzloPi" but I am gonna switch to Tasmota / MSR and eventually Home Assistant when I retire my Vera Plus for Z-Wave duties.

[cw-kid]

Sweet everything appears to be working now, I created some virtual devices in Vera for the Temp and Humidity and some new MSR rules to push those values to them in Vera if they change.

Updated my Home Remote dashboard and I can see them on my phone now and also have a switch to turn the Fan on and off..

!

!

[therealdb]

@cw-kid I have them with lux, barometric, distance, and temp/humidity sensors, while also using a couple as Bluetooth bridges. in this regard, your fantasy is the real limit.

I've recently moved everything I could to ZWave, because it is better in terms of stability, but ATM there's no equivalent for fancy sensors, even if ZigBee has a denter offer.

[cw-kid]

Actually I do have one issue: power_switch.state=null

It seems MSR is not seeing what the state of the relay currently is? Which is causing me an issue now in a rule I am trying to create.

If I run this command in terminal on the MSR / MQTT broker box

:~mosquitto_sub -v -t 'tele/fan_controller/#' -t 'stat/fan_controller/#'

I see this:

tele/fan_controller/LWT Online
tele/fan_controller/STATE {"Time":"2026-02-16T18:38:48","Uptime":"0T03:13:09","UptimeSec":11589,"Heap":113,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":4,"Objects":50},"POWER":"OFF","Wifi":{"AP":1,"SSId":"ASUS_86_2G","BSSId":"04:D9:F5:74:C5:E0","Channel":3,"Mode":"HT40","RSSI":100,"Signal":-20,"LinkCount":1,"Downtime":"0T00:00:04"},"Hostname":"Stairs-Cupboard-Fan-ESP32","IPAddress":"192.168.0.49"}
tele/fan_controller/SENSOR {"Time":"2026-02-16T18:38:48","AM2301":{"Temperature":21.2,"Humidity":47.9,"DewPoint":9.7},"TempUnit":"C"}
stat/fan_controller/POWER OFF

stat/fan_controller/POWER OFF

Which is correct, the fan is currently off.

So maybe the yaml code is not quite right if its not seeing the state of the relay.

I can turn on / off the relay however via MSR so it is talking to it somewhat.

This is what is in the reactor.yaml file currently.

- id: mqtt
  name: Mosquitto
  enabled: true
  implementation: MQTTController
  config:
    entities:
      tasmota_fan_controller_temp:
        name: "Stairs Cupboard Temp"
        include: tasmota_sensor_temperature_humidity
        topic: "fan_controller"
        source: AM2301
      tasmota_fan_controller_relay:
        name: "Stairs Cupboard Fan"
        include: tasmota_generic_relay
        topic: "fan_controller"
        unit: "1"  

[cw-kid]

Looking at the HTTP output for everything from the Tasmota, I see these snippets.

"StatusSTS" - seems to contain the state of the relay e.g. "POWER":"ON"

"StatusSTS":{"Time":"2026-02-16T18:58:25","Uptime":"0T03:32:46","UptimeSec":12766,"Heap":106,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"MqttCount":1,"Berry":{"HeapUsed":4,"Objects":50},"POWER":"ON","Wifi":{"AP":1,"SSId":"ASUS_86_2G","BSSId":"04:D9:F5:74:C5:E0","Channel":3,"Mode":"HT40","RSSI":100,"Signal":-19,"LinkCount":1,"Downtime":"0T00:00:04"},"Hostname":"Stairs-Cupboard-Fan-ESP32","IPAddress":"192.168.0.49"}}

Where as "StatusSNS" contains the Temp data.

"StatusSNS":{"Time":"2026-02-16T18:58:25","AM2301":{"Temperature":19.8,"Humidity":50.3,"DewPoint":9.1},"TempUnit":"C"},

So it seems MSR doesn't know where to find the relay status / state currently? and I am not sure how to fix it.

As a guess I tried adding source "POWER" to the relay section of the yaml but didn't seem to work and bring in the "ON" or "OFF" value.

tasmota_fan_controller_relay:
        name: "Stairs Cupboard Fan"
        include: tasmota_generic_relay
        topic: "fan_controller"
        source: "POWER"
        unit: "1"

I was poking around the file system to find these Tasmota default templates. I see this folder but its empty.

/home/stuart/reactor/config/mqtt_templates

I do see a file called tasmota.yaml however in this folder.

/home/stuart/reactor/ext/MQTTController/templates

EDIT: I just fixed it by changing unit: "1" to unit: "" in the reactor.yaml.
It now say "false" for power state in the Entites area. I thought I had to put a 1 in unit because in Tasmota somewhere, I saw the Relay was number 1.

[toggledbits]

Tasmota has this inconsistency where if there's only one relay configured, it does not include the relay number; if more than one, then it adds it. There's no way for the template to know how many relays are configured, so you found the correct fix.

[cw-kid]

@toggledbits I plan to add a second relay or replace it with a dual relay board, so will see how that works out with these Unit numbers.