You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I intended to have the ap enabled with the capative_portal enabled.
Unfortunetly I only found the issue and the implementation of it, but no documentation.
Reference feature request: https://github.com/esphome/feature-requests/issues/86
Reference implementation: #624
Issue:
When connecting to the accesspoint "p3gosund_Fallback_AP" it is often not getting connected and when it connects, the IP: 192.168.4.1 is not accessible.
After some seconds the connection to the AP is lost and I have to reconnect.
1.) Is the documentation about "captive portal" already somewhere?
2.) Does this work with the ESP8266 or is it only for ESP32?
3.) Unfortunately I am not aware how to get the logs, I have a serial connector here for the plug, but how can I get the logs of it?
I use ESPHome (dev) in HASS: Version 1.13.6
Here is my test config for the Gosund SP111 Tuya Plug:
Hi,
I intended to have the ap enabled with the capative_portal enabled.
Unfortunetly I only found the issue and the implementation of it, but no documentation.
Reference feature request: https://github.com/esphome/feature-requests/issues/86
Reference implementation: #624
Issue:
When connecting to the accesspoint "p3gosund_Fallback_AP" it is often not getting connected and when it connects, the IP: 192.168.4.1 is not accessible.
After some seconds the connection to the AP is lost and I have to reconnect.
1.) Is the documentation about "captive portal" already somewhere?
2.) Does this work with the ESP8266 or is it only for ESP32?
3.) Unfortunately I am not aware how to get the logs, I have a serial connector here for the plug, but how can I get the logs of it?
I use ESPHome (dev) in HASS: Version 1.13.6
Here is my test config for the Gosund SP111 Tuya Plug:
Any help is highly appreciated.
Many thanks! 👍
The text was updated successfully, but these errors were encountered: