New to Node-red - No initial flow

Awesome, that seemed to fix the issue. I bought another gateway and upgraded that one and it also works. Now I have another issue, I unplugged them and then moved them to our office and powered them back on and now I cannot login into them, Everytime I try login to either I get the message, that the GW is starting up. I can SSH into the devices so I know they are online and working

Hello @buddellk Sure, can you open PowerShell on your computer, then enter:

ssh ncdio@ncd-xxxx.local

Enter ncdB3ast for the password.

Once logged in enter:

pm2 status

Share the output you see there please. We need to see if atrium-ap and atrium-ingest are both running as they should on this Atrium.
Thank you.

Hello @buddellk Thank you for the information, It looks like it did not save the pm2 state as default start up, please follow this:

While SSH’d into the gateway run this command:
pm2 start atrium-api atrium-ingest

That will start the services and you should be able to log in. Now we need to retain that state for power up. Run this command:
pm2 save

Now run this command to confirm the saved list now records the services as online:
python3 -c 'import json;[print(p["name"],p["status"]) for p in json.load(open("/home/ncdio/.pm2/dump.pm2"))]'

Lastly confirm systemd owns pm2 at boot. It should print enabled and active:
systemctl is-enabled pm2-ncdio; systemctl is-active pm2-ncdio

After all that you can power cycle the Atrium to ensure it starts up properly. Please try this and share your results.

Thank you.

1 Like

That worked on both devices thank you

1 Like

We apologize for that inconvenience. There was a bug in the update that did not retain the pm2 script states after update. It has been corrected so you should not need to do this after future updates.

I would recommend testing a power cycle of the Atrium Gateway for now just to make sure everything is retained properly. If Atrium starts up fine after a power cycle you are good to go.

That worked thank you for that. I do have another issue now. On one of the two devices seems to stop responding after some period of time. I can no longer access it via the browser or SSH. If I reboot it I can. I wanted to try to enable Ping to see when it become unresponsive, or is there anything you can point me too, to look at?

Ping is disabled by default. To turn it on navigate to ncd-0363.local:8080 log in with your username and password. Then open Network/Firewall/ETH0_Client Edit button to the right. In the pop up window scroll to the bottom and you will see Ping Enable. Switch that on, click submit at the bottom of the pop up window, submit at the bottom of the Firewall page, then the red check mark at the top of the page. Ping response should now be enabled.

Let us know what you find.

Thank you,
Travis Elliott

Awesome that worked, thank you for all the assistance so far, I have deployed one set so far and am trying to hone in the vibration side and am getting close. I did have one more question on the ability to reset the counters and uptime based on time of day. Am I not doing something correctly? This is what is currently configured adn today it reset the counters at 3:00PM est??

I’m not super familiar with resetting the counters on these devices. @Bhaskar can you provide some insight on this?