Telemetry uses faradaybasicproxyio.py which uses fixed loopback addresses #137
Description
Summary
Telemetry example assumes radio is on the local network. I don't think this needs to be changed at this point, as telemetry is an example application. I think to close this problem, only a small README file could be created, outlining where the programmer should modify the program, if they offshore the proxy.
Problem Explanation
Telemetry uses Faraday_Proxy_Tools/FaradayIO/faradaybasicproxyio.py to make the connection to port 8000 on the proxy. But if the Proxy is on another computer embedded and offshore perhaps then faradaybasicproxyio.py fails, and then Telemetry fails.
The new users have no clue where to go, so a simple README hint should suffice.
Environment
Linux Ubuntu connected to Raspberry Pi Zero wireless serving as the Proxy for the Hardware.
Software
These lines would be modified in faradaybasicproxyio.py
Hardware
N/A
Supporting Information
N/A
README.md
ATTENTION:
In program:
Faraday_Proxy_Tools/FaradayIO/faradaybasicproxyio.py
Methods GET and POST use a fixed loopback address (127.0.0.1)
Faraday_Proxy_Tools/FaradayIO/faradaybasicproxyio.py Line 90
Faraday_Proxy_Tools/FaradayIO/faradaybasicproxyio.py Line 121
If the user has set up a remote computer to do the proxy, and the localhost is not used,
then for now, change the 127.0.0.1 to your computers IP address where the proxy resides.