A way to interact with IoT Devices
This webpage allows users to interact with various IoT devices through AWS IoTCore via MQTT. It utilizes AWS Amplify to handle secure authentication and PubSub capabilities. This is intended to be the front-facing display for Project Neo.
From this page, users are able to view available IoT operations (for example, running a stock ticker on an LED board) as well as see current device status and connection logs.
A while ago, I was trying to write code for my Raspberry Pi to have it be an IoT "hub" of sorts, querying and displaying some local state (internet speed, temperature/humidity, etc). I decided to name the device "Hubble" (like the Hubble Space Telescope). I thought it would be cool to have some naming cohesion by having everything somewhat related to astronomy. When this project was first created, the big thing going on was a comet that hasn't been seen since the time of the Neanderthals. I thought it would be neat to name this after that, however that comet didn't have a very fun name. I started thinking about what comets I knew the name of and the first thing that popped into mind was the movie Don't Look Up, which centers around Comet Dibiasky.
This project was bootstrapped with Create React App.
In the project directory, you can run:
npm startRuns the app in the development mode.\ Open http://localhost:3000 to view it in your browser.
The page will reload when you make changes.\ You may also see any lint errors in the console.
npm testLaunches the test runner in the interactive watch mode.\ See the section about running tests for more information.
npm run buildBuilds the app for production to the build folder.\
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes.\ Your app is ready to be deployed!
See the section about deployment for more information.
npm run ejectNote: this is a one-way operation. Once you eject, you can't go back!
If you aren't satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you're on your own.
You don't have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn't feel obligated to use this feature. However we understand that this tool wouldn't be useful if you couldn't customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.
This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting
This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size
This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app
This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration
This section has moved here: https://facebook.github.io/create-react-app/docs/deployment
npm run build fails to minifyThis section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify