Replies: 7 comments 65 replies
-
Hi, the yellow warnings is nothing to worry about. It’s just telling the user of the libraries that we shouldn’t use certain old functions. To obtain the IP with the USB connected you need to start the serial monitor and it will print it in the console window. You should make the web ui work before connecting to pump because you have to select hardware config for your pump. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Yippiiii!!! It seems everything is working now!!! I'm sorry, I just typed update and forgot the "/". The ".html" part was added by the browser automatically. (But I still don't know what could be the problem...) Thanks a lot for your patient and for your persistent help! |
Beta Was this translation helpful? Give feedback.
-
Hi again,
|
Beta Was this translation helpful? Give feedback.
-
I seem to have quite similar problems. I have installed everything from scratch and after i did that, i was perfectly able to access the integrated AP, configure my WiFi and MQTT. Everything is working fine except that i can't access the WebGUI now anymore. I have a ping running to the IP of the Webgui and everytime i try to access it, the ping stops for a moment. The WebGUI is displayed sometime, but it's not beeing displayed correctly. Looks like CSS is missing, so it's just a bunch of something. I tried updating it by accessing http://myip/update/ but that doesn't seem to do anything either. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
Performed the following steps while my 8266 is laying in front of me on my table, only connected to USB, nothing else:
I have not done the hardwaretest yet, as i first have to solder the JST-SM cables. In my understanding, i have to connect them to perform the hardware test? |
Beta Was this translation helpful? Give feedback.
-
After installing Beta 1854 in order to fix the hydrojet-not-in-HA problem, i now have problems reaching the webserver again when the ESP is connected to the pump and display. It is working fine on the bench though, but sometimes needs 1-2 restarts of the board. As soon as it is connected to pump and dsp, i have the old issue with very high ping times or loosing pings completely most of the time. UI loads but is just a blank white screen. Any obvious reason for that? May i try the latest beta? WiFi signal should be fine, as i have my pump right next to my bench |
Beta Was this translation helpful? Give feedback.
-
Hi @visualapproach,
after not using our Maldives for 1,5 month, I've tried to upgrade from 3.5.1 to the latest 4.1.0 from scratch (because of big changes).
Following the newest Build instructions pdf, I did the following:
connect PCB V1 to my computer via USB cable
load the new source code in Visual Studio
build & upload firmware via USB: SUCCESS, but I received some yellow lines, see the screenshots:
build & upload Filesystem Image via USB: SUCCESS
leaving the USB connection to computer: I can see Lay-Z-Spa Module access point and can connect it with the given pw, but obtaining IP address was failured
I couldn't reach http://layzspa.local (or the fixed IP address: 192.168.0.16 which was used before): I get empy page or ERR_ADDRESS_UNREACHABLE
Then I unconnected the module from PC and connected to the pump wires:
Lay-Z-Spa Module access point is not showing in the list of APs
I still can't reach the module web UI
meanwhile Network Scanner can see and ping the module and see the ports opened:
Connecting to DSP is the same: no sound and no displaying anything.
Could you help me what can be wrong and how can I fix it?
Thanks a lot,
Attila
Beta Was this translation helpful? Give feedback.
All reactions