# Node-red-contrib-s7 broken after 3.0.0 update

**URL:** <https://discourse.nodered.org/t/node-red-contrib-s7-broken-after-3-0-0-update/36855>\
**Category:** Industrial\
**Created:** [2 December 2020 09:57 UTC](https://discourse.nodered.org/t/node-red-contrib-s7-broken-after-3-0-0-update/36855 "2020-12-02T09:57:34Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [2 December 2020 10:13 UTC](https://discourse.nodered.org/t/node-red-contrib-s7-broken-after-3-0-0-update/36855/2 "2020-12-02T10:13:12Z")

</div>

it has been mentioned

I suspect you are using the IoT boxes that Siemens have not updated beyond node v8? If so, you essentially have an obsolescence issue (node 8 is EOL)

[See this](https://github.com/st-one-io/node-red-contrib-s7/issues/82#issuecomment-735520400)

If you can, move to Raspberry PI (much cheaper + up-to-date) (or any of the industrialised boxes based on RPi)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-contrib-s7-broken-after-3-0-0-update/36855)._