SK
Signal K12mo ago
Gaston

Gaston - I succesfully build and uploaded to an...

I succesfuly build and uploaded to an ESP, was able to connect to the AP, to add it to the wifi network (on the boat) and SignalK. I took the ESP back home to add extra sensors and I wanted to access the AP again to see if the new config was shown. But now it says that the AP password is wrong. I don't think the password has changed (or even can be changed), but nevertheless I tried all the passwords I know. I'm a little bit lost: what am I missing? (edit) I took the sensor to the boat today, and it did connect to the wifi. I opened the wifi AP settings on the SensESP web page, and retyped the AP password. Away from the wifi network, I tried to connect to the SensESP AP, but the response was again that the password was incorrect.
8 Replies
tobi42
tobi4212mo ago
i'm having trouble following... which wifi are you trying to connect to when you say "I took the ESP back home to add extra sensors and I wanted to access the AP again to see if the new config was shown."? the AP created by the SensESP device when it can't find the boat wifi? i think there's two different wifi networks at play here: your "boat wifi" and the "esp wifi". the "boat wifi" is whatever you have on your boat, either a raspi in AP mode, or a dedicated wifi router, or whatever. and the wifi name (SSID) and password for that will be whatever you set it to when configuring the wifi access point on your boat. and then there's the "esp wifi": when your ESP32 board with SensESP can't find the boat wifi or you don't have the boat wifi configured yet, it creates its own wifi access point, usually "Configure whatever-your-project-is-called". The default password for this network is "thisisfine" (see https://signalk.org/SensESP/pages/getting_started/#wifi-configuration )
Gaston
GastonOP12mo ago
Hi Tobias, I have two networks at home (where I normally build the SensESP with instruments and code, so you could say the testserver) at the boat (where I test and use the SenseESP, so you could say the production server) I understand that there is a SensESP AP. To be honest: I am just having troubles connecting a SensESP to a wifi network. And when I am not within range of a wifi network, I thought I would still be able to connect to the AP. To start with the last one: once I have been able to connect an SensESP to a wifi network, I am no longer able to access the AP. I can find it, but it always says that the password is wrong. I use the 'thisisfine' password, but also tried the wifi passwords, since I can't get in. The password of the AP is remembered by my phone, so I would expect I am not even able to make an error, but I still can't get in. Btw, I am using 3.0.0 b2 Beside that, or maybe it is related, I am having troubles with mDNS E (808967) signalk_ws_client.cpp: No Signal K server found in network when using mDNS service! D (808968) signalk_ws_client.cpp: Websocket is not connecting to Signal K server because host and port are not defined. I (808980) signalk_ws_client.cpp: Initiating websocket connection with server... I have to put the SignalK IP address and port number in the SensESP configuration. But still it doesn't show the access request in SignalK.
Gaston
GastonOP12mo ago
No description
Gaston
GastonOP12mo ago
No description
tobi42
tobi4212mo ago
i think there were some changes to the wifi handling in 3.0, so my guess might have been wrong is it normal that the server address is empty and the port is set to 80, not 3000 ?
Gaston
GastonOP12mo ago
Btw, when switching from and to the SensESP signal K configuration tab, the webpage component 'automatic server discovery' falls open even when on automatic. It's a bit confusing. Probably an easy fix in the code.
No description
No description
Gaston
GastonOP12mo ago
The server address and port are correct. I have SensESP modules that are working ok. But it might be possible that mDNS is not configured correctly on my RPi. Ok, I managed to connect to Signal K. When using the IP address of the server and unchecking 'Automatic server' discovery it worked. I think the webui fouled me a few times when I wrote the hostname and port, but the 'automatic server discovery' was also checked. So I have this SensESP connected. But it took me an hour. I probably do some things wrong, but I think there are some issues too. Can't really put my finger on it. I will build a new SensESP soon, and I will try to write down the steps and problems I have.
Unknown User
Unknown User5mo ago
Message Not Public
Sign In & Join Server To View

Did you find this page helpful?