Unable to register Node Red device

[Gareth Fuller]

Hi there,

I recently removed a Node Red device and am trying to re-add it. The logs are showing it cannot be added as it has the same IP.

I have entirely uninstalled the Join node from the pallete and restarted Node Red / Server but the same error occurs.

I found the following forum entry which referred to delete the pallete data but do you know where this is stored?

Thanks

[João Dias]

Do you maybe have another device on the same network that's already registered? Only 1 device per public IP is allowed...

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[Gareth Fuller]

Thanks João, is there a way to clear this?

This Node Red instance sits on a Raspberry Pi within my network. Other than Chrome devices and a Mobile - I'm not aware of any other devices which would exist.

Would I be able to register a new account with Join and add the Node Red Join instance to that account - just brain storming alternatives in case there is no means of clearing this data on my existing account...

Thanks again for the support! Blows my mind the art of the possible with your suite of tools.

[João Dias]

Check here if you have any other Node-RED devices that could come from your home: http://joinjoaomgcd.appspot.com/

If so, simply delete them and restart Node-RED :)

If not, it's possible that your global context in Node-RED is being saved persistently instead of being reset on restart, which will also make that happen. You have to clear the global context in Node-RED.

Hope this helps!

[Gareth Fuller]

That would be it, I do save my global contexts to the file system to avoid loosing states of devices after restarts.

Appreciate the nudge and thanks again for the support!

[João Dias]

No problem! :) Glad to help!

[Gareth Fuller]

Just in case someone else encounters the issue.

I navigated to  ~/.node-red/context/global and removed global.json (I'm happy to do that as my flows would automatically repopulate the file). Restarted the server hosting Node Red and then reconfigured the Join device in Node Red.

The device became available again in https://joinjoaomgcd.appspot.com/

I have tried to send a commend from the same page but I get a time out message, would this be firewall related? I have the Chrome forwarding enabled so wondering why it would be timing out...

[Gareth Fuller]

Having reinstated the device, and now seeing the entries - these global contexts can be updated with a Change node...

[João Dias]

Just to clarify, is everything working now? :)

[Gareth Fuller]

Hi  João 

I have the device appearing on my account however I'm unable to receive messages to this device.

I'm able to push message out from Node Red but unable to receive. When pushing from my mobile I get a timeout message appear.

Does any rules need to be applied to my firewall or should the Chrome forwarding cover this?

Thanks

[João Dias]

Oh, if you have Chrome you have to send messages to Chrome, so that it can redirect them to Node-RED :) Otherwise you need to setup your firewall to receive the messages directly...

[Gareth Fuller]

Okay, I'm clear now. So you send to the Chrome device with the command and it will forward it. I have tested this and its working as expected.

Thanks so much for coming back on this query! Super helpful! Excited for what this opens up...

[João Dias]

No problem! :) Glad to help!