avenmia / quantum-lamps Goto Github PK

Currently the lamp states are given as strings:

• "SetLight"
• "IDLE"
• "IDLENotConnected"
• "NOTIDLE"

These should be an ENUM instead of strings. Also "IDLENotConnected" is not necessary.

Make sure there are no differences between the code that is deployed on each pi and the code that is on github.

The pi should be come preinstalled with software that makes connecting to the user's internet connection simple. Currently, the user's networking info is hard coded in.

Add typescript logger to server side code and replace the console.log statements.

Currently there are a lot of todo statements, print outs, and trial code. There should be a clean working version of the client code That can be deployed to the pis for testing.

• Create new client branch
• Clean up client branch
• Merge that branch with Master

When the server receives a websocket connection, it should keep track of a list of client objects.

Deploy the master branch to both raspberry pis for manual testing.

Add unit tests to test server side code event handlers and error handling.

TSLint has been deprecated in favor of ESLint. Please see palantir/tslint#4534 for more information.

Source: https://www.npmjs.com/package/tslint

Add a logger to the application. Logger should only print if user enters the debug flag when running the program.

When the lamp sends or receives data, it should give some sort of visual feedback as a confirmation of the action. There are several functions that could be used (rainbow_circle) or making a new one as some sort of strobe.

• Add feedback for sending data
• Add feedback for receiving data

Debug why initial startup triggers a set light. This could have something to do with the idle and not connected state.

Timing issues are timing events related to when the lamp is changing state. For example, it takes 3 seconds to determine whether or not the lamp is idle. The process of determining whether it should send the current data could be 6 seconds if the lamp goes from not idle to idle. Ideally, this should be much lower. The lamp should also include a "cool down period" when the color is set. This allows the user to reorient the lamp back to its sitting position.

• Change time to determine idle or not idle
• Add a "pause" feature when the lamp color is set

Remove any unnecessary print statements and todos

Deploy the web server to Azure. Make sure it is accessible from different networks.

The server should not crash when receiving invalid messages.

Create a function that keeps the light the same color. This needs to:

• Take in light data (This could come from an incoming websocket message or from the current state)
• Change the light color to the current state
• Maintain that color until either a new websocket message comes in or the lamp is no longer idle

Every client should have an ID that just the server assigns to the socket. Usernames should not be hard coded in the application.

Create a strategy for deploying updates to the raspberry pi's.

Bharat's idea:
Allow the pi's on boot to connect to vpn that I can access

Things to consider:

• Backwards compatibility
  • Version numbers
• Auto Deployment

Currently there is a locahost:8080 hardcoded in. The urls should be in environment variables.

The lamp works with a web socket connection, but should be able to work as a regular lamp if it is not connected to the web server for whatever reason. This task is about making sure the lamp still works if it is not connected to the server as well as adding functionality to check if the server is back up every x minutes or so.