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
After updating a HM EPW6 receiver from v3.3.0 to v3.4.0 the captive portal often does not work.
Most of my receivers are flashed using Betaflight Passthrough method.
Except my pwm receivers inside planks without a flight controller.
So I normally build a .gz file with the Configurator and save it to my Desktop.
Close the Configurator and power up the rx.
Wait for it to go in wifi mode and connect my laptop to the ExpressLRS RX access point.
The above screenshot is when v3.3.0 is installed.
After the connect it automatically opens a Chrome browser and uses msftconnecttest.com/redirect to automatically go to 10.0.0.1
Handy.
After flashing v3.4.0 this often does not work.
Above screenshot is when v3.4.0 is installed.
Notice the "Open browser and connect" line is not visible.
(Also connecting to a v3.4 rx AP is much slower vs a v3.3 rx AP.)
It does not open my Chrome browser and use the redirect to automatically go to 10.0.0.1
If I do this manually all is OK and I can configure the RX if needed.
Just wanted to point this out as a possible bug.
I can reproduce this on my laptop going up and down from v3.3.0 <--> v3.4.0
Sometimes the redirect works on v3.4.0 but often it does not.
I hate it when bugs are intermittent, but it seems the case here.
Not a big issue, just pointing out what I've seen during my pwm rx update process.
Thx for all the hard work!
The text was updated successfully, but these errors were encountered:
After updating a HM EPW6 receiver from v3.3.0 to v3.4.0 the captive portal often does not work.
Most of my receivers are flashed using Betaflight Passthrough method.
Except my pwm receivers inside planks without a flight controller.
So I normally build a .gz file with the Configurator and save it to my Desktop.
Close the Configurator and power up the rx.
Wait for it to go in wifi mode and connect my laptop to the ExpressLRS RX access point.
The above screenshot is when v3.3.0 is installed.
After the connect it automatically opens a Chrome browser and uses msftconnecttest.com/redirect to automatically go to 10.0.0.1
Handy.
After flashing v3.4.0 this often does not work.
Above screenshot is when v3.4.0 is installed.
Notice the "Open browser and connect" line is not visible.
(Also connecting to a v3.4 rx AP is much slower vs a v3.3 rx AP.)
It does not open my Chrome browser and use the redirect to automatically go to 10.0.0.1
If I do this manually all is OK and I can configure the RX if needed.
Just wanted to point this out as a possible bug.
I can reproduce this on my laptop going up and down from v3.3.0 <--> v3.4.0
Sometimes the redirect works on v3.4.0 but often it does not.
I hate it when bugs are intermittent, but it seems the case here.
Not a big issue, just pointing out what I've seen during my pwm rx update process.
Thx for all the hard work!
The text was updated successfully, but these errors were encountered: