User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

05 Oct 2020, 09:02

Hi All,
I need to confess that I didn't note before the noderedrevpinodes-server option on the service tab of the RevPi web interface.

Well, even if I try to flag the "Enable" box, after pushing "SAVE ALL" button, it comes back to "Disabled"

Thanks for any help
Marco
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

07 Oct 2020, 07:22

May be of help update distro to buster?
Marco
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

13 Oct 2020, 19:14

Dear All,
time on the bench for this RevPi is finished.
Today I've tried several attempts.

Firs: I've tried to restore an image from another working RevPi. Bad idea. Probably because I've used "dd" command, even if the image was written correctly, RvPi wasn't able to boot (of course it wasn't reachable anymore over ssh).

Second: I've installed a fresh stretch release from kunbus web site as per indications both on the web site and in the release note pdf downloaded with the image file.

Once RevPi was on again, I went directly to configure Pictory, then node red but without performing any update or upgrade.

They were necessary some reboots and crosschecks between the web interface and ssh terminal.

Finally, it starts to work.

Question is still the same: why had I that error previously?

Spending dozens of hours for debugging could not be so bad but, spending hours every time this happens to refresh newly a revpi, starts to sound not so good.

Thanks,
Marco
 
jgerlach-erminas
Official 3rd Party Support Erminas
Posts: 32
Joined: 22 Jan 2020, 14:31

Re: Unable to Connect to remote AIO module with node red

22 Oct 2020, 10:43

Hi Marco,

sorry for the long delay. Have you already tried the workaround for the dependency problem? See here https://revolution.kunbus.de/forum/view ... 7703#p7809

Greetings,
Jones
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

26 Oct 2020, 08:01

Hi Jones,
thanks for your care.
Actually, while I was trying to solve this issue, yes, I also tried that workaround...
No positive results pushed me to reinstall everything by new.
Maybe I'll do some test with a new RevPi I intend to prepare in the next days but I'm a bit scared to update/upgrade os now.
Marco
 
h2oil
Posts: 10
Joined: 17 Jan 2020, 17:30

Re: Unable to Connect to remote AIO module with node red

27 Oct 2020, 17:26

Have same issue - after new flash with Stretch image all noderedrevpi server cannot be connected to

On RevPi Status unable to save Enable/Disable Node-RED RevPi Nodes Server to Status Enabled

im using Connect+ and 4 x AIO
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

03 Nov 2020, 16:47

Hi, dears,
I confirm there is a bug.

On a new RevPi I've performed the following steps:
  • I Powered on RevPi
  • I had access to web UI to activate services (at first there is not node red to activate)
  • Used Pictory to set up my configuration (RevPi core 3+ and RevPi AIO module ...same as last time)
  • I had access to web UI again to activate node-red service
  • The first node-red activated is an old version ...it has not the palette manager
  • I've updated node-red (
    bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
    )
  • Then I've installed node-red-contrib-revpi-nodes through the palette manager
In the end, the same problem. No PINs are available in the input or output nodes to be selected.

Please, check for this issue.
Marco
 
h2oil
Posts: 10
Joined: 17 Jan 2020, 17:30

Re: Unable to Connect to remote AIO module with node red

03 Nov 2020, 16:53

Hi, dears,
I confirm there is a bug.

On a new RevPi I've performed the following steps:
  • I Powered on RevPi
  • I had access to web UI to activate services (at first there is not node red to activate)
  • Used Pictory to set up my configuration (RevPi core 3+ and RevPi AIO module ...same as last time)
  • I had access to web UI again to activate node-red service
  • The first node-red activated is an old version ...it has not the palette manager
  • I've updated node-red (
    bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered)
    )
  • Then I've installed node-red-contrib-revpi-nodes through the palette manager
In the end, the same problem. No PINs are available in the input or output nodes to be selected.

Please, check for this issue.
Marco
Marco has same issue as me (I did same steps)
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

06 Nov 2020, 11:00

Hi Dears,
finally, I've found a solution.
For anybody that has this issue, it needs few simple steps
  • sudo wget http://packages.revolutionpi.de/pool/contrib/n/noderedrevpinodes-server/noderedrevpinodes-server_1.0.1_all.deb
  • sudo dpkg -i --ignore-depends=nodered /your_file_folder/noderedrevpinodes-server_1.0.1_all.deb
  •  sudo systemctl start noderedrevpinodes-server
If node red is not running
node-red-start
.
That's it.
Marco
 
User avatar
Marcos
Topic Author
Posts: 17
Joined: 09 Mar 2020, 18:42

Re: Unable to Connect to remote AIO module with node red

08 Apr 2021, 14:00

Hi Dears, here I am again.
There is the same issue again.
my previous procedure doesn't work any more after the last update.

Connecting to WS Server wss://localhost:8000
ERROR Connection to server error: Client network socket disconnected before secure TLS connection was established
Lost connection to WS Server!

Update

The new server release 1.0.3 requires some new dependencies.

proceed to install
python3-bcrypt
python3-websockets

then after having downloaded new release from github (https://github.com/erminas/noderedrevpi ... r/releases)
install it with

sudo dpkg -i noderedrevpinodes-server_1.0.3_all.deb

Now it works again.

Who is online

Users browsing this forum: No registered users and 2 guests