wireguard VPN doesn't connect

[jo-mueller]

Hi all,

I tried quite a few things and I'm kind of lost. I want to use an ESP8266 as a smart reader for my power meter. My house's fusebox is unfortunately far too far away from my wifi router, so I figured I'd need to log the ESP8266 into a neighbor's WIFI and provide the mqtt data into my network through a wireguard VPN tunnel.

I think I have everything set up correctly (tasmota compiles correctly with ufs enabled). I then upload my wireguard.conf file...and nothing happens. I have checked that the conf file is accurate by opening it with my local wireguard client.

According to the documentation, adding the wireguard.conf file through the ufs uploader should enable a few commands (i.e, WGConnect and WGStop, none of which work in the console:

22:10:10.392 CMD: WGConnect
22:10:10.400 MQT: stat/tasmota_EF83BA/RESULT = {"Command":"Unknown","Input":"WGCONNECT"}

I previously also added this bit to the conf

[Tasmota]
Netmask = 0.0.0.0
AutoConnect = 1

but no difference. There's probably something simple I'm missing. Any help is appreciated!

[sfromis]

Getting {"Command":"Unknown","Input":"WGCONNECT"} indicates that the driver is not active. You can verify that your build includes the driver using command Status 4. In the long output line there is a field "Drivers" where number 80 is the Wireguard driver.

[jo-mueller]

Hi @sfromis ,

ok, I also realized I'm dumb - I hadn't added the #define USE_WIREGUARD statement to my config file. That being said, I'm running into some new issues. First off, one needs to edit the script before activating the VPN, because the webUI won't work once the VPN is activated. But that's entirely possible to figure out by reading the documentation carefully 🙄 So far, so good.

But it seems like I'm running into more VPN-related problems:

• Connecting to the ESP8266 via the webUI through VPN seems to freeze the device? If rebooted, it connects reliably (and stays so), but once I access the webUI, I cannot get information from the mqtt client on the device anymore.
• Once rebooted, I suspect that the uploaded SML script becomes deactivated by default? At least I don't get any sensor readings anymore. Is there a way to check via the http/mqtt CLI whether the script is active or even there, to begin with?

Edit: Since the problem is more the upload/redout of an sml script through the CLI I think this issue fits better under the SML category. Thanks anyway for the help!

[s-hadinger]

We definitely need logs. Is the device serial attached so you can get logs before and after wireguard connects?

[jo-mueller]

Is the device serial attached so you can get logs before and after wireguard connects?

How do I get the serial? 😬 Sorry, not really a power user here.

[sfromis]

Serial is with wires (including USB) attached, and a terminal program.

Since you have a file system, you can also use the command FileLog to set up Tasmota saving log files, like FileLog 4 for the most detailed level, or FileLog 14 for also deleting old log files first.

[jo-mueller]

Follwed up in #24219