[APP][Pro] Tasmota MQTT

spkesDE · September 4, 2023, 4:49pm

You can set it higher via Tasmota.

https://tasmota.github.io/docs/Peripherals/#update-interval

C_Brade · November 3, 2023, 2:01pm

312d7bfa-ab76-4202-9f56-a286d30a08e2

Sorry for the big delay.

Here is the report for not working tasmota device

Best regards

Lars_Stryhn · February 18, 2024, 12:29am

Did you find a solution for this?

Lars_Stryhn · February 18, 2024, 12:47am

Any luck finding an answer?

Sharkys · February 18, 2024, 9:30am

@spkesDE , isn’t it because of these errors (running existing instance via CLI) ?

2024-02-18T09:28:24.415Z [log] [ManagerDrivers] [Driver:tasmota_mqtt] [Device:1249f68e-6a25-4893-8889-5d9dccb1afa7] sensorTrigger is undefined
2024-02-18T09:28:24.416Z [log] [ManagerDrivers] [Driver:tasmota_mqtt] [Device:7feb8d12-50c8-421f-98bc-b65cb196ee45] sensorTrigger is undefined
2024-02-18T09:28:24.417Z [log] [ManagerDrivers] [Driver:tasmota_mqtt] [Device:9f797077-5212-4e25-8224-3057c38314c4] sensorTrigger is undefined

2024-02-18T09:28:24.674Z [log] [TasmotaMqttApp] Unhandled Rejection at: Promise Promise {
  <rejected> TypeError: Cannot read properties of undefined (reading 'trigger')
      at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
} reason: TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-02-18T09:28:24.676Z [log] [TasmotaMqttApp] Unhandled Rejection at: Promise Promise {
  <rejected> TypeError: Cannot read properties of undefined (reading 'trigger')
      at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
} reason: TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-02-18T09:28:24.677Z [log] [TasmotaMqttApp] Unhandled Rejection at: Promise Promise {
  <rejected> TypeError: Cannot read properties of undefined (reading 'trigger')
      at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
} reason: TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
unhandledRejection:
TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
unhandledRejection:
TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
unhandledRejection:
TypeError: Cannot read properties of undefined (reading 'trigger')
    at TasmotaDevice.checkSensorCapability (/app/drivers/tasmota_mqtt/device.js:491:38)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

As it’s loading the drivers dynamically, it’s something out of my reach/capabilities but maybe it would provide you some insights ?

spkesDE · February 18, 2024, 2:08pm

it won’t create the this.sensorTrigger flow object since in the devices settings additional_sensors is false

See line 13, 35-39. This app is so messy in its writing. As we talked already on slack. I would to rewrite this app to make it more understandably for me. As of right now I’m not sure why settings.additional_sensors isn’t populated by the pairing process. MQTT is still a big riddle to me.

Also why the pairing keeps on loading and won’t show any devices is properly the fact that the app didnt registered any new MQTT events in this time and therefore no devices are shown.

On my local system using Tasmota Wall Plugs the pairing is working fine.

github.com

spkesDE/com.paveld.tasmota/blob/master/drivers/tasmota_mqtt/device.js#L38


      
              }
          }
          if (!this.hasCapability('onoff') && (this.relaysCount > 0))
              await this.addCapability('onoff');
          
          for (let socketIndex = 1; socketIndex <= this.relaysCount; socketIndex++)
              this.socketsList.push({name: 'socket ' + socketIndex.toString()});
          if (this.additionalSensors) {
              if (!this.hasCapability('additional_sensors'))
                  await this.addCapability('additional_sensors');
              this.sensorTrigger = this.homey.flow.getDeviceTriggerCard('sensor_value_changed');
          }
          this.onOffList = this.getCapabilities().filter(cap => cap.startsWith('switch.'));
          if (this.onOffList.length > 0) {
              this.registerMultipleCapabilityListener(this.onOffList, (valueObj, optsObj) => {
                  let capName = Object.keys(valueObj)[0];
                  let value = valueObj[capName] ? 'ON' : 'OFF';
                  let index = capName.slice(-1);
                  this.sockets[parseInt(index) - 1] = value
                  this.sendTasmotaPowerCommand(index, value);
                  return Promise.resolve();

Michael1 · June 24, 2024, 8:12pm

Whenever I try to add a device it prompts “No new devices found”. This happens when I try to add a new device and when I toggle the device on/off during the scan.

If i don’t toggle the device, it prompts that no MQTT messages were seen during the scan.

Does this mean that the device I am trying to add it somehow known? How can I add this device now?

Debug log 32a411f0-ed3d-423a-aef4-bed0eff7c055

spkesDE · June 24, 2024, 8:58pm

Do you have the default group and topic?

Michael1 · June 26, 2024, 6:51am

That was it. The topic was correct, however it seems that the groupname was not default.
It worked right away after resetting the configuration.

jsiegmund · July 23, 2024, 8:54pm

Hi there. I’m using the Tasmota app for Homey to control 4 Sonoff devices flashed with Tasmota. Works great apart from the fact that for some reason the devices sometimes become listed as unreachable. My workaround is to restart the app, after which all is fine again. I have no real clue as to when this happens, it seems quite random but it always takes a while. Running this on a Homey Pro 2023. Is this any known issue?

I’ve created a flow to restart the app every night but that’s a rather ugly workaround I’d rather get rid of.

Sharkys · July 23, 2024, 9:09pm

Have you shared diag. log by any chance ? But I don’t have this problem, only that the signal strength is not getting updating after while…

jsiegmund · July 25, 2024, 7:12am

Not yet, no. I’ll stop the daily restart flow for now and wait until it happens again and then I’ll share the diagnostics

Leonardo_Soliera · August 9, 2024, 9:39pm

I’ve had the same problem for a long time now, but I can’t understand the reason, as you say, it’s quite random, if there is a solution to this I’d be happy. I restarted the app this morning due to this problem, as soon as it happens again I will share the logs

spkesDE · August 10, 2024, 4:21am

The problem with this app is that the backend is quite a mess. In my opinion, it would require a complete rewrite to ensure flawless performance. However, this is a significant task that would necessitate a larger MQTT network, which I simply don’t have. Additionally, it would demand a lot of time—something I lack in my day-to-day life.

Also I don‘t know the issue/cause of the crashing.

jsiegmund · August 16, 2024, 11:32am

In the meantime I’ve switched to using the MQTT device powered by the MQTT hub app. It’s a bit early to tell but for now all seems well. This eliminated my use for the Tasmota app so I ended up removing it.

Sharkys · August 21, 2024, 8:35am

Thank you for letting us know, I just wonder what is the memory requirement of MQTT HUB vs. Tasmota, I guess it’s more then Double ?

Leonardo_Soliera · September 17, 2024, 4:09pm

Hi, I discovered that the main problem occurs when homey is restarted, once it is turned back on all the devices are unavailable by restarting the app the problem is solved. I attach the code of the report made in the app: d80bb917-
d32d-4cd3-9bc4-e0e7cc9a0be1

schmucke · October 16, 2024, 10:42am

Since yesterday or the day before, i have a problem with tasmota plugs in flows.
If in turn a device on by hand (in app by pressing the button) all works fine. If i use a Flow like

if "huemotion detects a motion" then "turn tasmota plug on"

the plug does nothing. Other, like zigbee2mqtt apps are working fine.
Appversion v0.13.2

I have create a report:
41a77c44-4dc2-4374-a878-3241232bce76

spkesDE · October 16, 2024, 11:04am

Please try the latest test version.

schmucke · October 16, 2024, 11:34am

no change, the same like before.

c88f4578-4b09-493d-bdc5-df901314115a

Thank you

Topic		Replies	Views
[APP][PRO] Zigbee2MQTT Apps app , zigbee , tools , homey-pro	464	18835	December 5, 2025
[APP][Pro] Tuya Zigbee App Apps	1074	167192	December 6, 2025
[APP][Pro] TuyAPI / Neo Coolcam wall plug WIFI app Apps app , wifi , homey-pro	330	30740	October 19, 2025
ITEAD Sonoff Apps app	301	26841	October 20, 2024
[APP][Pro] Universal TUYA Zigbee Device App - test Apps app , zigbee	583	6981	December 6, 2025

[APP][Pro] Tasmota MQTT

Related topics