Can't connect Sensesp to SignalK
I have both setup on the network with the Sensesp at 192.168.4.1 and SignalK at 192.168.4.211 but I don't see an access request in SignalK. SSL is off, mdns is enabled. The two devices are sitting right next to each other. SignalK is on a Pi5 running OpenPlotter. I even tried making sure that both were using 2.4Ghz, but that didn't make any differnence.
7 Replies
Do you have login enabled? Pretty sure that is required to use mdns. Some other things to try:
Connect the debugger to your IDE and you should see log entries for access request
Also go to the esp32 web admin and you can always enter the SK IP and port directly into config.
I did setup the IP and port in the esp32 admin and it says “authorizing with SignalK”, but I don’t see the access request in SignalK.
Where do I enable login?
It’s under Security in the left navigation
Hi, I got the exact same issue. Did you understand or solve your problem? Here is my log as well. I wont get an Access Request in signalK. As it concludes it doesn't have a prior authorization I presume it find the SignalK server. Thankful for any help! SSLoff, mDNS on as well
Dont bother! I had a signalK test server on my windows machine to understand if I'll make it work on the boat... Firewall settings solved it... 😬
Can I ask what you did to fix this - have the same issue
I have identical debug output as @Henrik with a fresh clone (3.1.0) and build of the project.
The same SignalK server (2.14.0 on rpi5) and ESP32 hardware works fine with the sensesp 2.7 based code. Also, using curl to manually request a token works. Any help is greatly appreciated The root cause of the issue (in my case) is the failure to make a TCP connection to the server.
When the ESP32 Wifi is configured for AP+STA in order to support the config captive portal, the connection fails (despite mDNS being able to discover the server). The problem goes away if you disable the captive portal (which puts the wifi in STA mode). I verified this with the Lolin D32 and D1 Mini boards both using SenESP and a minimal stand-alone test sketch.
I will dig deeper when i have time, but for now, I hope this will help someone.
The same SignalK server (2.14.0 on rpi5) and ESP32 hardware works fine with the sensesp 2.7 based code. Also, using curl to manually request a token works. Any help is greatly appreciated The root cause of the issue (in my case) is the failure to make a TCP connection to the server.
When the ESP32 Wifi is configured for AP+STA in order to support the config captive portal, the connection fails (despite mDNS being able to discover the server). The problem goes away if you disable the captive portal (which puts the wifi in STA mode). I verified this with the Lolin D32 and D1 Mini boards both using SenESP and a minimal stand-alone test sketch.
I will dig deeper when i have time, but for now, I hope this will help someone.