New 6.1 device bought from elecrow has protected wifi

[Spancii]

Hi Daniel,

I bought an adapter from elecrow but this device has wifi password. I have been tried reset the device but unfortunately i can't. Do you have any idea what is the password or why i can't reset the device to default.

Many thanks!

[AndrevdG]

@danielkucera, I have tried with DIO but it does not make difference, same error.

Actually, the reason that the flash exe tool did not work was my mistake... If I select the correct board, the exe tool also flashes the adapter fine. Still no AP though

[danielkucera]

Please try the firmware form the artifacts.zip here: https://github.com/danielkucera/esp8266-arduino-ebus/actions/runs/7742664315

[sergius18100]

I had the problem of not seeing the wifi at all, as mentioned by keithwithnall and AndrevdG. Flashed the device several times with the latest firmware, tried with a charger and with a computer. In the end, it turns out that the device actually works somehow, but the wifi shows very late some minutes after boot, which creates the impression it does not initiate. Having found out this, got several root problems that lead to these symptoms.

• The device apparently would not connect to a WPA3 network, neither would it connect to a non-broadcasted SSID. I had to create a separate WPA2 network with broadcasted SSID, after which the device connected.
• Once configured, it reboots after exactly three minutes of being on line. This is different from two minutes that AndrevdG has, but seems to be the same behaviour. Once rebooted, it remains silent for a few minutes, but connects to wifi after that, lives for another three minutes and reboots again. The wifi signal is good, access point just next to the device, so it cannot explain the reboots. What can be done?

[danielkucera]

@sergius18100 , the firmware in artifact has enabled some logging to USB serial port. Can you try that and capture the logs so we can see what is happening there?

[PiotrHab]

@danielkucera , I have some other use case which could help with wifi response. I'm playing with the device very occasionally (when i have time) and i observed that after long time of no ebusd connection, the device becomes very slow at wifi response (status page takes up to 3-4 seconds to show, ebusd reports device connection lost and reconnection). I figured out that is because of wifi modem sleep. After WiFi.begin(); , i've added esp_wifi_set_ps(WIFI_PS_NONE); And that problem seems to be gone. I'm aware this makes device power hungry but on the other hand it's more wifi responsive. So maybe that could solve some issues reported here...

[AndrevdG]

With the updated firmware: From the logging it appears to start the AP, but as you can see from the windows Wifi manager, no esp-eBus ssid is visible.

I checked this with two (be it win11) devices and my mobile (android) to be sure, but no AP shows up

[AndrevdG]

Don't know if it helps, but I saw it attempting to connect to a default AP, so I tried to set my mobile hotspot in Windows to it. It does also not connect to that AP.

[danielkucera]

Please try again: https://github.com/danielkucera/esp8266-arduino-ebus/actions/runs/7752846735

the default password is: ebusebus

[AndrevdG]

Well, that definitely did something. With that firmware the AP shows up in the SSID list and I can successfully connect to it.

It starts with:

after I update the settings:

It did not reconnect to my WIFI immediately. However, after disconnecting / reconnecting the adapter:

and also mDNS:

I'll attach it to ebus and see if I get some actual data

[AndrevdG]

Actually, it appears that http://esp-ebus.local/param this (from the quickstart) does not work, so not sure how to adjust the PWM value (it is unset currently). Going to http://esp-ebus.local asks for a login

[AndrevdG]

Ok, going over your code it appears the correct url is http://esp-ebus.local/config.

I found the login on the IotWebConf usermanual (user:admin, pw: \<whatever the AP password was>), so I managed to connect. Port 3333 and 3334 appear to be working, presuming the expected output is something like this:

Telnetting (or using a browser) to port 3335 or 5555 does not work however, this immediately disconnects putty and the browser just does:

[danielkucera]

Yes, this I moved from wifimanager to iotwebconfig so some aspects are different. However, the ports 3335 and 5555 should still work with telnet, I haven't done any changes there. Can you please check again?

[AndrevdG]

Just tried again, with putty the session is disconnected immediately (I can see putty pop up, but no error message and the window just disappears). However, I have added the adapter to Home Assistant now and the ebusd add-on appears to be able to read 3335, so it appears to be working.

I guess it is an issue with putty (it may be an older version). Using telnet in a commanline window appears to work. 3335 gives garbage (as I suppose is expected) and 5555 gives a status and exits (that may also be expected):

[danielkucera]

Yes, that is correct

[AndrevdG]

As a follow up, the adapter has been running for several hours now connected to ebus and providing data to home assistant.

Thank you for your quick responses and help to get the adapter functional!