# \[APP\]\[Pro\] Tasmota MQTT **URL:** \ **Category:** Apps\ **Tags:** homey-pro\ **Created:** [February 20, 2020, 6:14pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164 "2020-02-20T18:14:10Z")\ **Posts on this page:** 20\ **Page:** 22
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [September 4, 2023, 4:49pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/430 "2023-09-04T16:49:56Z")
You can set it higher via Tasmota. [https://tasmota.github.io/docs/Peripherals/#update-interval](https://tasmota.github.io/docs/Peripherals/#update-interval) ---
**Author:** ![C\_Brade](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/c_brade/32/12394_2.png) [@C\_Brade](https://community.homey.app/u/C_Brade)\ **Post date:** [November 3, 2023, 2:01pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/431 "2023-11-03T14:01:27Z")
312d7bfa-ab76-4202-9f56-a286d30a08e2 Sorry for the big delay. Here is the report for not working tasmota device Best regards ---
**Author:** ![Lars\_Stryhn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lars_stryhn/32/81912_2.png) [@Lars\_Stryhn](https://community.homey.app/u/Lars_Stryhn)\ **Post date:** [February 18, 2024, 12:29am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/432 "2024-02-18T00:29:30Z")
Did you find a solution for this? ---
**Author:** ![Lars\_Stryhn](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/lars_stryhn/32/81912_2.png) [@Lars\_Stryhn](https://community.homey.app/u/Lars_Stryhn)\ **Post date:** [February 18, 2024, 12:47am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/433 "2024-02-18T00:47:15Z")
Any luck finding an answer? ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [February 18, 2024, 9:30am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/434 "2024-02-18T09:30:14Z")
> [@spkesDE](#): > > it won’t add the Sensor to the device. @spkesDE , isn’t it because of these errors (running existing instance via CLI) ? ```auto 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 ``` ```auto 2024-02-18T09:28:24.674Z [log] [TasmotaMqttApp] Unhandled Rejection at: Promise Promise { 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 { 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 { 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 ? 😉 ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [February 18, 2024, 2:08pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/435 "2024-02-18T14:08:36Z")
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. > ---
**Author:** ![Michael1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael1/32/79082_2.png) [@Michael1](https://community.homey.app/u/Michael1)\ **Post date:** [June 24, 2024, 8:12pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/436 "2024-06-24T20:12:10Z")
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 ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [June 24, 2024, 8:58pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/437 "2024-06-24T20:58:57Z")
Do you have the default group and topic? ---
**Author:** ![Michael1](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael1/32/79082_2.png) [@Michael1](https://community.homey.app/u/Michael1)\ **Post date:** [June 26, 2024, 6:51am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/438 "2024-06-26T06:51:17Z")
That was it. The topic was correct, however it seems that the groupname was not default. It worked right away after resetting the configuration. ---
**Author:** ![jsiegmund](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@jsiegmund](https://community.homey.app/u/jsiegmund)\ **Post date:** [July 23, 2024, 8:54pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/439 "2024-07-23T20:54:25Z")
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. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [July 23, 2024, 9:09pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/440 "2024-07-23T21:09:56Z")
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… ---
**Author:** ![jsiegmund](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@jsiegmund](https://community.homey.app/u/jsiegmund)\ **Post date:** [July 25, 2024, 7:12am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/441 "2024-07-25T07:12:47Z")
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 👍🏻 ---
**Author:** ![Leonardo\_Soliera](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/leonardo_soliera/32/49003_2.png) [@Leonardo\_Soliera](https://community.homey.app/u/Leonardo_Soliera)\ **Post date:** [August 9, 2024, 9:39pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/442 "2024-08-09T21:39:33Z")
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 ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [August 10, 2024, 4:21am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/443 "2024-08-10T04:21:29Z")
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. ---
**Author:** ![jsiegmund](https://avatars.discourse-cdn.com/v4/letter/j/53a042/32.png) [@jsiegmund](https://community.homey.app/u/jsiegmund)\ **Post date:** [August 16, 2024, 11:32am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/444 "2024-08-16T11:32:24Z")
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. ---
**Author:** ![Sharkys](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/sharkys/32/54029_2.png) [@Sharkys](https://community.homey.app/u/Sharkys)\ **Post date:** [August 21, 2024, 8:35am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/445 "2024-08-21T08:35:03Z")
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 ? ---
**Author:** ![Leonardo\_Soliera](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/leonardo_soliera/32/49003_2.png) [@Leonardo\_Soliera](https://community.homey.app/u/Leonardo_Soliera)\ **Post date:** [September 17, 2024, 4:09pm UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/446 "2024-09-17T16:09:23Z")
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 ---
**Author:** ![schmucke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/schmucke/32/79913_2.png) [@schmucke](https://community.homey.app/u/schmucke)\ **Post date:** [October 16, 2024, 10:42am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/447 "2024-10-16T10:42:14Z")
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 ---
**Author:** ![spkesDE](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/spkesde/32/54352_2.png) [@spkesDE](https://community.homey.app/u/spkesDE)\ **Post date:** [October 16, 2024, 11:04am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/448 "2024-10-16T11:04:16Z")
Please try the latest test version. ---
**Author:** ![schmucke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/schmucke/32/79913_2.png) [@schmucke](https://community.homey.app/u/schmucke)\ **Post date:** [October 16, 2024, 11:34am UTC](https://community.homey.app/t/app-pro-tasmota-mqtt/26164/449 "2024-10-16T11:34:22Z")
no change, the same like before. c88f4578-4b09-493d-bdc5-df901314115a Thank you [Previous page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=21) [Next page](https://community.homey.app/t/app-pro-tasmota-mqtt/26164.md?page=23)