-
Notifications
You must be signed in to change notification settings - Fork 638
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On clean install device stays in MODE AP #79
Comments
Original comment by Matheus Telles (Bitbucket: matheustelles, GitHub: matheustelles): I noted that when I setup on terminal a double name Wifi ssd0 like "set ssd0 Matheus Telles" it report me "-ERROR bad argument count". |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): The auto retry / connect in AP mode is also making it difficult to configure on the web since it drops your connection on every retry. |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): In platformio.ini I revert back to the 1.6.3 config .. ie removed the git version of ESPAsyncTCP, ESPAsyncWebServer cleaned the lib's rebuild and flashed and that seemed to work again. I need to do a bit more testing to confirm this. Later Ferdie |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Nope that was not it .. only way I could get the device on the network was to time the setting up of the web interface and configure static IP. All a bit weird. |
There is an issue with ESPAsyncTCP reported in Async MQTT Client, the library ESPurna uses: marvinroger/async-mqtt-client#30. It's related to the same commit in ESPAsyncTCP that fixes the MSS problem we had these last days. |
Issue #78 was marked as a duplicate of this issue. |
I think I will switch to good-old PubSubClient... |
Original comment by Matheus Telles (Bitbucket: matheustelles, GitHub: matheustelles): How can I disable the "CreateAP" when the STA falls, but keep trying to reconnect but without creating AP? I need to enter on AP mode only when the button is DoublePressed or there is no Wifi setting saved. |
@MatheusTelles You can set the AP_MODE setting to AP_MODE_OFF in the |
The dev branch now uses PubSubClient as MQTT client by default (I kept the async code as an option). I'm getting good results connecting to my local broker. If the issue is with the ESPAsyncTCP library it should be solved now. |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Had to add PubSubClient to lib_deps in platformio.ini on a git checkout dev, git pull to get it to compile without errors. Going to give it a quick flash and see what we are getting. Later Ferdie |
Wasn't it already there? |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Nope ... I typically delete my platformio.ini before I do a git clean -f and the a git pull. Also finding that I can switch from esp to domoticz, but can not switch from domoticz to the esp.
Still playing. Later Ferdie |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Ok let me try with this
|
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Done the above - complied without any issues - and can see the platformion changes look like yours. So git was a bit stuffed.
Still same same, can switch to domoticz but is does not listen to what domoticz has to say. Want to test AP quickly. Going to leave mqtt configured. Later Ferdie |
This is because the MQTT_MAX_PACKET_SIZE in the PubSubClient library is too small, edit the PubSubClient.h file and change it to:
|
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Ok, I would like to nominate myself for the darwin award. So my original reason for logging the ticket was to do with being stuck in AP mode and never seeing the light of day with STA configuration from terminal. Who would have thought that I would by thinking I was doing the correct thing actually find something that was totally unrelated - but almost true enough to be the issue.
vs
Hey now all WIFI from terminal works.
So is doing a "set ssd0" a bug or feature and what am I setting? Turns out you can set anything in the terminal - like setting a var, no validation that you are not being silly about it. Now back to mqtt. Later Ferdie |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): 100% ... made the change in PubSubClient.h cleaned up the pioenvs/sonoff-debug/lib/ removed PubSubClient_ID89 and libPubSubClient_ID89.a rebuild and upload, and the flood gates opened ;-) MQTT working to and from domoticz. Going to stick around in dev branch for a bit .. Later Ferdie |
Hahaha... well, the terminal uses Embedis which provides:
The application has no control on what config settings are created. You may as well do:
ESPurna will query the Embedis dictionary for the settings she wants to know, if there is no such setting she will use a default value or null. I wouldn't call it a bug or a feature. |
@MatheusTelles Same for the "set ssd0 Matheus Telles" issue. "set" is a built-in command that expects key and value. |
Original comment by Matheus Telles (Bitbucket: matheustelles, GitHub: matheustelles): My bad, its "set ssid0 Matheus Telles". I tried "set ssid0 Matheus_Telles" and worked, but I need to change the ssid on router with no backspace. |
@MatheusTelles You can do |
@F-Fish Does it make any difference using PubSubClient or AsyncMQTTClient? |
Original comment by f-fish (Bitbucket: f-fish, GitHub: Unknown): Not the brief time I played with it. have not moved this onto production devices. Still sitting on the bench. Later Ferdie |
I have noticed some difference between the both. On one hand PubSubClient, being synchronous, does halt execution when trying to connect, web interface is not responsive while the firmware is trying to establish an MQTT connection. On the other hand it seems more reliable and fast once the connection has been established. |
Version 1.6.5 is live using PubSubClient by default. Please read note 1 in section "Installing libraries from the Library Manager" here https://bitbucket.org/xoseperez/espurna/wiki/ArduinoIDE.md. |
Removing milestone: 1.7.0 (automated comment) |
Originally reported by: f-fish (Bitbucket: f-fish, GitHub: Unknown)
Hi all, need some validation on this please.
After a clean / new device install. The device only boots into AP MODE.
Expected behaviour:
on terminal
device connects to AP abc.
What currently happens:
Device always connects in
after a reset I can
get ssd0 and get pass0 with the correct information being retrieved.
This worked in 1.6.3 - current 1.6.4 master not working as expected.
Later Ferdie
The text was updated successfully, but these errors were encountered: