[LINUX] Install enebular-agent on Chromebook

Before I knew it, I noticed that Linux (beta) was available on the Chromebook. Chromebooks are lightweight and have a good battery life, so when using Google services that can be done with a browser, Mbed, [micro: bit](https:: I often use it in the development of //microbit.org/ja/guide/). enebular-agent that runs on Linux machines as agent software for devices supported by enebular I tried to see if Overview.html) works on a Chromebook.

• This is a personal experiment and does not formally declare support.

Chromebook used: ASUS C101P

Examine your Linux distribution

It came out as follows.

***@penguin:/$ cat /etc/issue
Debian GNU/Linux 9 \n \l
***@penguin:/$ cat /etc/debian_version
9.9

When enebular-agent checks Supported Linux, it says Debian GNU / Linux 9 Stretch, so there is no problem. I think.

Install enebular-agent

Check How to install enebular-agent and try to install it. An AWS account or Pelion device bundle is required for installation. This time I tried it on AWS. Necessary things such as nodejs and nodeRED are installed automatically, so if you can use wget or apt-get, it's OK. In the case of Linux of Chrome book, it was OK just with the installation command.

Install command

wget -qO- https://enebular.com/agent-install | sudo -E bash -s -- --aws-iot-thing-name=*** --aws-access-key-id=*** --aws-secret-access-key=*** --aws-iot-region=***

(Please set the *** part of your account)

After a few minutes of waiting, I was able to install it successfully.

Installation log (secret part is hidden)

==========================================================================================================================
 enebular-agent installation:
   - Device name:         penguin
   - System:              Linux 4.19.60-06185-g54aa50936831 aarch64 GNU/Linux
   - Install user:        enebular
   - Install destination: /home/enebular/enebular-runtime-agent
   - Agent port:          awsiot
   - Agent version:       latest-release
==========================================================================================================================
==== Fetching updater version info ====
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100    27  100    27    0     0     33      0 --:--:-- --:--:-- --:--:--    33
OK
==== Downloading updater version 2.9.0 ====
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1482k  100 1482k    0     0   511k      0  0:00:02  0:00:02 --:--:--  511k
OK
==== Installing enebular-agent-updater to /tmp/enebular-agent-updater.dwHoIVYIl ====
OK
==== Checking node.js version ====
OK
==== Checking existing node.js v9.2.1 installation ====
OK
==== Downloading https://nodejs.org/dist/v9.2.1/node-v9.2.1-linux-arm64.tar.gz ====
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16.8M  100 16.8M    0     0  2892k      0  0:00:05  0:00:05 --:--:-- 3797k
OK
==== Checking integrity ====
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3671    0  3671    0     0   4437      0 --:--:-- --:--:-- --:--:--  4438
OK
==== Installing Node.js v9.2.1 to /home/enebular/nodejs-v9.2.1 ====
OK
==== Fetching enebular-agent ====
OK
==== Extracting enebular-agent ====
OK
==== Updating system package lists ====
OK
==== Install Debian dependencies ====
dpkg-query: no packages found matching build-essential
dpkg-query: no packages found matching python
OK
==== Building agent 2.9.0  ====
OK
==== Building Node-RED ====
OK
==== Building awsiot port ====
OK
==== Building awsiot-thing-creator ====
OK
==== Install Debian dependencies ====
OK
==== Creating Remote Maintenance User ====
Creating enebular-remote-admin using default password
OK
==== Applying file permissions ====
OK
==== Creating AWS IoT thing ====
OK
==== Registering startup service ====
OK
==========================================================================================================================
 enebular-agent has been successfully installed ✔
   - Version: 2.9.0
   - Location: /home/enebular/enebular-runtime-agent
   - User: enebular
   - Service name: enebular-agent-enebular

 AWS IoT Thing {thing name} has been created.
 enebular-agent is running as a system service.
 To check the status of agent, run the following command on the target device:
   sudo journalctl -ex -u enebular-agent-enebular.service
==========================================================================================================================
See details in full install log file: /tmp/enebular-agent-install-log.GGU8Sf

Deploy flow from enebular

I tried to deploy the flow from enebular. To deploy from enebular to a device, you need Create Connection (https://docs.enebular.com/en/Deploy/DeployFlow/AWSIoT/MakeAWSIoTConnection.html). Let's create a simple flow and deploy it.

The deployment was successful.

from now on

I tried the experiment, but I didn't think about what to use it for. For the time being, it may be easier if you want to quickly install nodeRED on your Chromebook. In the future, I'd like to do something using a node that can handle Chromebook functions. I think Raspberry-pi is better for connecting sensors, so it would be interesting if we could do something unique to Chromebooks that can easily use displays and touch panels.