{"id":3446,"date":"2024-09-12T20:53:50","date_gmt":"2024-09-12T19:53:50","guid":{"rendered":"https:\/\/m0aws.co.uk\/?p=3446"},"modified":"2024-10-18T19:51:13","modified_gmt":"2024-10-18T18:51:13","slug":"allstarlink-control-dashboard","status":"publish","type":"post","link":"https:\/\/m0aws.co.uk\/?p=3446","title":{"rendered":"AllStarLink Control Dashboard"},"content":{"rendered":"\n

Ever since I built my RaspberryPi\/SHARI AllStarLink node<\/a> I’ve had to manage connecting\/disconnecting to\/from other nodes using the Allmon2 or Supermon web admin interfaces. These work fairly well albeit, a bit clunky and buggy. It’s impossible to use from a mobile device though and so I have to get my Macbook out each time I want to connect\/disconnect nodes.<\/p>\n\n\n\n

Being a Node-RED fanatic I decided that I should put something together that was more portable, mobile friendly and much easier to use. A simple user interface is all that is required and can be achieved very easily using the standard Node-RED dashboard nodes.<\/p>\n\n\n\n

Initially I started investigating the Linux command-line interface for Asterisk, the VOIP system that underpins AllStarLink (ASL). I very quickly discovered that the ASL node can be very easily controlled directly from the command-line and that this would be an ideal interface to use to enable node management via a Node-RED dashboard.<\/p>\n\n\n\n

In very little time at all I had an experimental control dashboard working with the ASL node and was able to connect\/disconnect to\/from a single node. All that was required now was to extend this so that I could connect to a number of nodes with nothing more than a push of a button.<\/p>\n\n\n\n

\"AllStarLink<\/a>
Completed v1.0 AllStarLink Control Dashboard – Node-RED Flow<\/figcaption><\/figure>\n\n\n\n

The resultant flow consists of 3 sections, Connect\/Disconnect Main Flow<\/em>, Manage Node Subflow<\/em> and \/var\/log\/asterisk\/connectlog Subflow<\/em>.<\/p>\n\n\n\n

The Connect\/Disconnect Main Flow<\/em> handles all the input from the buttons on the dashboard and the communication to the underlying Asterisk VOIP system. <\/p>\n\n\n\n

The button status is denoted by 3 colours, green (Ready to connect), orange (Transitioning to\/from connect) and red (Connected). Each button is updated automatically by the button refresh function that is triggered every 2 seconds.<\/p>\n\n\n\n

The Manage Node Subflow<\/em> provides a simple interface to restart the Asterisk VOIP system, reboot the RaspberryPi and shutdown the RaspberryPi. The node status is automatically updated every 45 seconds and will show when the Asterisk subsystem is being restarted or the node is being rebooted or shutdown.<\/p>\n\n\n\n

Finally the var\/log\/asterisk\/connectlog Subflow<\/em> monitors the Asterisk connectlog looking for connect\/disconnect messages so that it can signal to update each button status.<\/p>\n\n\n

\n
\"Node-RED
Node-RED AllStarLink Dashboard<\/figcaption><\/figure>\n<\/div>\n\n\n

Each section of the dashboard can be collapsed\/opened by touching\/clicking the little blue arrows on the right of the dashboard. The dashboard works fine on Android, iOS, Windows, MacOS and Linux.<\/p>\n\n\n\n

If you’re not familiar with Node-RED and haven’t yet installed it to your PC, take a look at the Node-RED Getting Started Page<\/a>. The information takes you through installing Node-RED onto a multitude of devices including PC and RaspberryPi devices.<\/p>\n\n\n\n

Once you have Node-RED installed all you need to do is download the AllStarLink Control Dashboard Flow and import it to your Node-RED flow editor.<\/p>\n\n\n\n

AllStarLink-Dashboard-v1-2<\/a>Download<\/a><\/div>\n\n\n\n

Note: The link above is now for v1.2 of the flow which includes some critical bug fixes. You can read about the bug fixes in the v1.2 release article<\/a>.<\/p>\n\n\n\n

Once downloaded, select Import<\/em> from the burger<\/em> menu icon on the right-hand side of the flow editor as shown below and import the flow file.<\/p>\n\n\n\n

\"Node-RED
Node-RED Flow Editor import Menu Item<\/figcaption><\/figure>\n\n\n\n

Once imported you will find that some of the nodes in the flow are not available. This is because you need to add them to the flow editor palette before being able to deploy the flow.<\/p>\n\n\n\n

Drop down the same menu as shown above but, this time select Manage Palette<\/em>. This will open another window where you will need to select the Install<\/em> tab as shown below.<\/p>\n\n\n\n

\"Node-RED<\/a>
Node-RED Flow Editor Palette Install Tab<\/figcaption><\/figure>\n\n\n\n

You need to install two node sets to complete the flow, node-red-contrib-bigssh<\/em> and node-red-dashboard<\/em>. Type in the name of each package one at a time in the search bar and then click the Install<\/em> button.
Once the two packages are installed you then need to configure the credentials for logging into your RaspberryPi. This is simply done by double clicking the blue Send Command to ASL <\/em>node at the top of the main flow and then clicking the Pencil<\/em> button at the end of the Credentials field. This will open another window where you will need to type in the IP Address of your ASL RaspberryPi into the Host<\/em> field, then enter 22 into the port<\/em> field, add repeater<\/em> into the Username field (repeater is the default username, if you have changed this then you will need to add the new username name in instead) and then the password associated with the repeater login into the Password<\/em> field. (Normally allstarlink)<\/p>\n\n\n\n

Once this is done, do the same on the other blue nodes, namely “Get Node Uptime<\/em>“, “Command =>> RaspberryPi” <\/em>and “Tail ConnectLog”<\/em>.<\/p>\n\n\n\n

The final thing to setup is the dashboard size. Click on the downward pointing triangle<\/em> at the top right of the menu bar (under the burger<\/em> menu) and select dashboard<\/em>. Check that the sizes<\/em> are set the same as in the image below. For some reason, these settings aren’t always imported (Possible bug?) so, if your dashboard layout isn’t like shown above it will be because these settings failed to import.<\/p>\n\n\n\n

\"ASL
ASL Dashboard Settings<\/figcaption><\/figure>\n\n\n\n

You are now ready to deploy your AllStarLink Control Dashboard!
Press the red Deploy<\/em> button at the top of the flow editor window.<\/p>\n\n\n\n

To access the dashboard from any device, open your favourite web browser and enter the following URL: http:\/\/IP-Address-of-Node-RED-Computer:1880\/ui<\/a><\/p>\n\n\n\n

Finally, if you want to change the nodes that each button connects\/disconnects you will need to edit the set flow var’s<\/em> function at the top of the main flow. All you will need to do is replace the existing node numbers taking care not to alter the rest of the code in any way otherwise, it could stop the flow from working. <\/p>\n\n\n\n

Once you’ve edited the node numbers, double click on the associated button node and change its Label<\/em> to show the new node name.<\/p>\n\n\n\n

Once your changes are complete, Deploy<\/em> the flow again and your changes will be live.<\/p>\n\n\n\n

This is version 1 of the ASL Dashboard, I already have ideas for version 2 that will also have the ability to enter a node number into a field and connect to it without the need to program it into a button.<\/p>\n\n\n\n

More soon …<\/p>\n","protected":false},"excerpt":{"rendered":"

Ever since I built my RaspberryPi\/SHARI AllStarLink node I’ve had to manage connecting\/disconnecting to\/from other nodes using the Allmon2 or Supermon web admin interfaces. These work fairly well albeit, a bit clunky and buggy. It’s impossible to use from a mobile device though and so I have to get my Macbook out each time I … <\/p>\n

Continue reading “AllStarLink Control Dashboard”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[362,332,270,356,36,287,180,334,189,184,4,273,162,161,178,183,171,38,41,40,56,179,186,135,37,134,122,351,346,349,299,302],"tags":[],"class_list":["post-3446","post","type-post","status-publish","format-standard","hentry","category-362","category-allstarlink","category-android","category-asterisk","category-code","category-commandline","category-dashboard","category-dv","category-floweditor","category-flows","category-ham-radio","category-ios","category-ipad","category-iphone","category-javascript","category-json","category-kubuntu","category-linux","category-logging","category-logs","category-macos","category-nodered","category-nodes","category-opensource","category-programming","category-projects","category-raspberrypi","category-raspbian","category-sa818","category-shari","category-sourcecode","category-webbrowser"],"_links":{"self":[{"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/3446","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3446"}],"version-history":[{"count":42,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/3446\/revisions"}],"predecessor-version":[{"id":3557,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/3446\/revisions\/3557"}],"wp:attachment":[{"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3446"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3446"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/m0aws.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3446"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}