# Tasmota node not working after Tasmota 8.30 firmware update?

**URL:** <https://discourse.nodered.org/t/tasmota-node-not-working-after-tasmota-8-30-firmware-update/26740>\
**Category:** General\
**Created:** [16 May 2020 08:45 UTC](https://discourse.nodered.org/t/tasmota-node-not-working-after-tasmota-8-30-firmware-update/26740 "2020-05-16T08:45:14Z")\
**Posts on this page:** 1\
**Showing post:** 21

<div class="post-metadata">

**Author:** ![stefan24](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/stefan24/32/23075_2.png) [@stefan24](https://discourse.nodered.org/u/stefan24)\
**Post date:** [18 May 2020 14:26 UTC](https://discourse.nodered.org/t/tasmota-node-not-working-after-tasmota-8-30-firmware-update/26740/21 "2020-05-18T14:26:31Z")

</div>

I deinstalled and installed Node-RED with all nodes and settings several times now and get the errors described above with tasmota AND zigbee2mqtt, as soon as I install the node `node-red-contrib-enocean`.

But this combination has worked for 4-5 days. I was able to check the state of my Enocean based Hoppe door handle together with all other nodes.

Is there an alternative to use my Enocean USB300 stick with Node-RED?

---

_[View the full topic](https://discourse.nodered.org/t/tasmota-node-not-working-after-tasmota-8-30-firmware-update/26740)._