WiFi disconnects, but connects after refresh
-
DWC not responding again
![747e2eb9-e6c8-4c5b-b247-ca51fbe0f501-image.png] -
DWC stopped responding again , different error in Chrome Dev tools
Did notice at this point btncmd and plugin manager had both been stopped (not by me)
A form field element should have an id or name attribute
A form field element has neither an id nor a name attribute. This might prevent the browser from correctly autofilling the form.
To fix this issue, add a unique id or name attribute to a form field. This is not strictly needed, but still recommended even if you have an autocomplete attribute on the same element.
1 resource
Violating node -
DWC stopped responding again
-
after refesh of browser the DWC looked like this
and not like This
also btnCmd and release manager had stopped , had to restart manually
-
DWC stopped responding again very similar to the one above , btnCmd and release manager had stopped , had to restart manually.
<
-
undefined gloomyandy referenced this topic
-
Ok can you move all my other posts over to here?, i only have a few days left then im on holiday for 6 weeks so if i dont respond ill be back in April
-
@moth4017 I don't have the power to move posts on here, maybe @droftarts could move them?
-
@gloomyandy there you go
-
@jay_s_uk thamk you
-
@chrishamm Could you take a look at the debug console outputs in this thread? It seems odd that we can have a situation in which a browser refresh fixes a connection problem, any idea what may be happening?
-
@gloomyandy looking at the data on the octopus control board it says only supports 8266, which wifi module would you recommend and ill get a couple on order ?
will this be ok?
https://biqu.equipment/products/esp32u-mode-esp32e-mode -
@gloomyandy The WiFi server kills incoming connections, so DWC loses the connection to RRF (connection reset). This issue is still being investigated AFAIK. DWC is already designed to retry the same HTTP request a few times in standalone mode but if that keeps failing, the connection is eventually invalidated.
-
@chrishamm Yes but why does doing a browser "refresh" fix the problem? As far as the WiFi server is concerned it is just seeing http requests so I don't see why the refresh would fix a problem at the server side? It seems odd to me? Maybe it is just a change in the timing of requests? If we can understand why that refresh fixes things it might help us resolve the problem (if there is one) in the WiFi server.
