[APP][Pro] Tasmota MQTT

Apps
430

You can set it higher via Tasmota.

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

1 Like
431

312d7bfa-ab76-4202-9f56-a286d30a08e2

Sorry for the big delay.

Here is the report for not working tasmota device

Best regards

432

Did you find a solution for this?

433

Any luck finding an answer?

434

@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 ? :wink:

435

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.

1 Like