The system was tested successfully by the technician who assembled it, but when I tried it at home, the servos didn’t move, even though:
Stellarium’s remote control plugin is running (http://localhost:8090).
The website version (localhost:8090/api/objects/info?format=json) receives data when I change planet positions in Stellarium.
Wireshark shows no connection to port 8090 from the ESP8266.
Setup:
All devices (PC, ESP8266) are connected via Android hotspot.
The technician programmed the ESP8266 to work with this setup.
Problem:
Data reaches the web interface, but the servos don’t respond.
No communication detected between ESP8266 and Stellarium via port 8090.
Has anyone faced a similar issue? Could it be a network configuration problem (e.g., localhost not accessible from ESP8266)? Any debugging tips?
I am an astronomer and I can tell you that you need pics of hand drawn wiring, photos, all the code and an explanation your mother will understand. You are assuming too much.
In simple language tell us what you expect, then tell us what actually happens.
All we know for sure from your comments is that Stellarium is talking to the webserver, but what is the webserver software that you are using and where is it running?
You also say that you are using an Android hotspot. Are both devices showing as connected to it, getting an IP address from the hotspot, and can you ping the hotspot and the ESP8266 from the PC? I am assuming that the ESP8266 is running in STAtion (connect to a home router) mode rather than AP (be its own hostspot) mode? Might something have caused it to default back to AP mode, e.g. such as the Hotspot not being available yet, being out of range or some other issue? Have you tried restarting the ESP8266 with the hotspot on and in range?
It would appear that the Mega is driving the servos, but you don't mention any kind of driver board? Is there one, or are the servos connected directly to the Mega?
Presumably the ESP8266 also connects to and communicates with the Mega? How exactly?
How are you testing this?
A diagram showing the interconnection of devices would be helpful, even if drawn by hand.
jremmington is correct. Even though I and others might understand how such a setup might work, there is not enough information in your post to do anything but guess at this stage. It might indeed be easier to ask the technician who set it up, but by all means if you or they can provide further information, that would certainly help.
BTW, localhost is not accessible from any device remotely because it is, well, "local" and its address is not route-able over a network. Any service (e.g. webserver or application) running on localhost can only be accessed from the machine it is running on. To access it remotely would require an IP address or a resolvable host name. Could it be a network configuration problem? Yes, quite possibly, but again, not enough information provided to make that determination.
Technicians have more pressing issues than to test a hobby kit. Read the sketch, match the sketch hardware to the circuit diagram, wire it pin for pin. You can do it.