# RFXtrx node not working on one Pi after upgrade

**URL:** https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805
**Category:** General
**Created:** [9 July 2020 18:31 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805 "2020-07-09T18:31:30Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Mastiff](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@Mastiff](https://discourse.nodered.org/u/Mastiff)
#### Post date: [9 July 2020 18:31 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/1 "2020-07-09T18:31:30Z")

</div>

I did the regular upgrade process that I always use on two identical Pis:

```auto
bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)

```

But on one of them I updated Python as well, to 20.1.1. with:

```auto
sudo pip install --upgrade pip

```

That seems to have broken Node-red-contrib-rfxcom, it's stuck on the same stuff as in this thread:

> [@Node-red-contrib-rfxcom not working after noder-red upgrade](https://discourse.nodered.org/t/node-red-contrib-rfxcom-not-working-after-noder-red-upgrade/1027):
>
> Hi I have problem with node-red-contrib-rfxcom after node-red upgrade to version 0.1.12. I get error: Flows stopped due to missing node types. rfxtrx-port PT2262-device-list rfx-PT2262-in rfx-lights-in rfx-lights-out

But the commands at the bottom there are not working for me, probably because that's another Linux distro (I am hopeless with Linux, I can follow instructions but mess up roally if I try to do anything outside of that). Can I revert to a version of Python that's supported by the node, or is there something else I can do?

---

<div class="post-metadata">

### Author: ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [9 July 2020 18:33 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/2 "2020-07-09T18:33:42Z")

</div>

> [@Mastiff](#):
>
> Python as well, to 20.1.1

Hey Mastiff,  
You must have received a far future pre-release, Python does not have that versioning numbers (yet). Maybe sometime 2099....

---

<div class="post-metadata">

### Author: ![Mastiff](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@Mastiff](https://discourse.nodered.org/u/Mastiff)
#### Post date: [9 July 2020 18:35 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/3 "2020-07-09T18:35:41Z")

</div>

Hi, Walter! 🙂 Nice to see you! And you're quick... I edited my post. So it's probably not the version, but I get this:

```auto
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already up-to-date: pip in /usr/local/lib/python3.5/dist-packages (20.1.1)

```

---

<div class="post-metadata">

### Author: ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)
#### Post date: [9 July 2020 18:42 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/4 "2020-07-09T18:42:32Z")

</div>

Hi there,  
I think that just tells you that you have pip version 20.1.1. Pip is used for installing python packages and I don't think that has anything to do with the RFXtrx part. I think instead it might be that you have problem with the serial port? Could that be the case? Once happened to me long time ago, I fixed it by running the upgrade/install script one more time

---

<div class="post-metadata">

### Author: ![Mastiff](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@Mastiff](https://discourse.nodered.org/u/Mastiff)
#### Post date: [9 July 2020 18:50 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/5 "2020-07-09T18:50:33Z")

</div>

I see! 😉 Thats why the version was so strange. According to the post I linked to above it needed the correct version of Python to work. But I have now tried the script again, and it still says "Waiting for the missing types to be registered". Luckily this isn't the most critical Pi in the house, so I can leave it like this until tomorrow at least.

---

<div class="post-metadata">

### Author: ![Mastiff](https://avatars.discourse-cdn.com/v4/letter/m/ee7513/32.png) [@Mastiff](https://discourse.nodered.org/u/Mastiff)
#### Post date: [9 July 2020 18:57 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/6 "2020-07-09T18:57:17Z")

</div>

Oh, I see that Pi's still on Stretch... I must have forgotten to upgrade it to Buster last fall, when I thought I did them all. I'll do that and see if that doesn't help. 😊

---

<div class="post-metadata">

### Author: ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)
#### Post date: [9 July 2020 21:56 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/7 "2020-07-09T21:56:40Z")

</div>

I think that Python is used to help compile some C dependencies? Certainly not needed by the RFX node itself.

Watch out for Python version changes though since Python 2.x is no longer supported and depending on how you have things set up, you might need to use pip3 rather than pip to update Python dependencies.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [7 September 2020 21:56 UTC](https://discourse.nodered.org/t/rfxtrx-node-not-working-on-one-pi-after-upgrade/29805/8 "2020-09-07T21:56:42Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
