You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 10, 2024. It is now read-only.
Websocket can already start commands to power off/reboot a machine.
This could be used to start custom commands and enable to:
Start client remotely
Use Raspberry Pi/Computer applications and get return state
For example:
Start a temperature logger that connect to the websocket to get the data and save it in a database
Get state of the temperature logger.
Start samba file sharing to get database
Stop samba file sharing/ssh when not needed.
Get state of connectors.exe
We should create a directory for each devices and put scripts in it, when connector started with the argument --commands [DIR] , it will get all the scripts name and generate a list of commands that can be started using the websocket.
For example :
--> {"command":"start_sensorlogger"}
<-- {"out:"[string]","err","errorlevel"}
Of course, this could be used without an arduino.
If no serial is defined it should default to only custom commands mode.
The text was updated successfully, but these errors were encountered:
Websocket can already start commands to power off/reboot a machine.
This could be used to start custom commands and enable to:
For example:
We should create a directory for each devices and put scripts in it, when connector started with the argument --commands [DIR] , it will get all the scripts name and generate a list of commands that can be started using the websocket.
For example :
Of course, this could be used without an arduino.
If no serial is defined it should default to only custom commands mode.
The text was updated successfully, but these errors were encountered: