Your valuename field seems empty in task settings. Its printed after the "/" but blank...chrille wrote:I have tested this with the OpenHAB MQTT protocol and there's a cosmetical issueMartinus wrote:R65 is available on github:
Added a simple plugin device to send single values to the controller.
Notice the trailing / after memory.Code: Select all
/ESP008364/dsw3/Temperature 21.25 /ESP008364/adc3/Analog 120.00 /ESP008364/memory/ 29936.00
- Jan
ESP Easy Releases
Moderators: grovkillen, Stuntteam, TD-er
Re: ESP Easy Releases
Re: ESP Easy Releases
Stupid mistake in the padding routine, R66 should fix this. Just pushed it on github.chrille wrote:This does not work for me (tested in R65 and with LCD2004)Martinus wrote: Added padding to LCD/OLED display
Fixes a 'bug'
See this photo http://sandkasse.chrillesen.dk/forum/IMG_2381.JPG for the issue (I have a DHT-22 that sometimes reports NaN for humidity and this causes the position of the C to change)
- Jan
Hope it's the final one...
Re: ESP Easy Releases
My fault... sorry - it works perfectly fine nowMartinus wrote:Your valuename field seems empty in task settings. Its printed after the "/" but blank...
Code: Select all
/ESP008364/sysinfo/memory 30120.00
/ESP008364/sysinfo/uptime 197.00
Jan Chrillesen, Denmark
Re: ESP Easy Releases
R67 is available on github.
Added support for BME280 sensor. This brings a new 3-value sensor type so all controllers needed an update for this. Succesfully tested on Domoticz using HTTP. Other controllers are updated but not tested.
Added support for BME280 sensor. This brings a new 3-value sensor type so all controllers needed an update for this. Succesfully tested on Domoticz using HTTP. Other controllers are updated but not tested.
Re: ESP Easy Releases
I had a NodeMCU 1.0 with R64 and it seemed to work more or less okay. There were one or two resets the past 24 hours, but that is not very special.
After putting R67 on it I started to get a continuous reboot with
Exception (0):
epc1=0x4022cce2 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
Now, with R64 back on it again, this behavior remains the same. A perpetual reset.
After putting R67 on it I started to get a continuous reboot with
Exception (0):
epc1=0x4022cce2 epc2=0x00000000 epc3=0x00000000 excvaddr=0x00000000 depc=0x00000000
Now, with R64 back on it again, this behavior remains the same. A perpetual reset.
Re: ESP Easy Releases
I think this has to do with my new Horizon box. It has a very strong Wifi signal on the same channel.
Re: ESP Easy Releases
how we can send plugin system info uptime to domoticz?
anybody get it?
thanks
anybody get it?
thanks
Re: ESP Easy Releases
@maluku
Just create a dummy device type Counter in Domoticz. Note its ID
Then, in ESPEasy devices, create a task with a device tyoe System Info
fill in name, ID (the one of the counter in Domoticz), the type of indicator and do not forget to tick the Send Data check box.
That should do it.
Just create a dummy device type Counter in Domoticz. Note its ID
Then, in ESPEasy devices, create a task with a device tyoe System Info
fill in name, ID (the one of the counter in Domoticz), the type of indicator and do not forget to tick the Send Data check box.
That should do it.
Re: ESP Easy Releases
With respect to my earlier problems, R67 is running ok now. I managed to switch off the AP of my Horizon box.
I looks like the ESP has a problem when a WiFi Chanel is disturbed.
I looks like the ESP has a problem when a WiFi Chanel is disturbed.
Re: ESP Easy Releases
Thanks Bert, my doubt was what virtual sensor choose on domóticz.
Re: ESP Easy Releases
Very nice feature.Martinus wrote:R64 is available for download on github,
.....................
Added support for local button to turn on LCD/OLED display with configurable timeout
For "maluko's" project... But others are also allowed to use it.
...
This opens the possibility to have more than one screen output, walking through the different screens with the local button. Default would be screen 1, pushing the button brings you to screen 2, pushing again goes to the next screen or the first screen like in a loop. When the screen turns off pushing the button would bring on the light again without going to the next screen.
Would be specially usefull for LCD screens with 2 or 4 lines, but also on OLED screens could this be usefull sometimes.
There are already so many system variables like %ip%, %systime%, %uptime%, %sysname% and maybe I forget some. If you have more than one screen one can use a screen for only system variables and another screen for the device variables.
The question is if this would not use too much resources of the ESP and would cause instabilities, than it is a bad idea.
Last edited by costo on 17 Jan 2016, 15:23, edited 1 time in total.
Re: ESP Easy Releases
Is there an overview what is possible at the Moment ?There are already so many system variables like %ip%, %systime%, %uptime%, %sysname% and maybe I forget some
Re: ESP Easy Releases
R68 is available on github:
- Fixes the CSS upload feature
- Adds OTA update using bin file upload through the ESP Easy webgui (NOT from arduino IDE):
ONLY for ESP modules with more than 512k Flash like the ESP12E on the NodeMCU V1 boards!
So you can export the binary from IDE and use the ESP Easy webgui to upload the file:
- Fixes the CSS upload feature
- Adds OTA update using bin file upload through the ESP Easy webgui (NOT from arduino IDE):
ONLY for ESP modules with more than 512k Flash like the ESP12E on the NodeMCU V1 boards!
So you can export the binary from IDE and use the ESP Easy webgui to upload the file:
- Attachments
-
- BINfile.png (5.42 KiB) Viewed 43920 times
Re: ESP Easy Releases
good work
I am wondering if it is possible work esp easy only on AP mode, i try to put on standalone but dont stay, i think its because sidd and password not field.
i think that i has post this doubt on past, but i will descrived.
i have a gate that dont have any internet connetion but my idea are to put one android phone (app tasker) and espeasy with relay(connect each other with wifi by esp), so when i call to the phone the tasker will trigger the rule and ativated by http get the relay by http://<ESP IP address>/control?cmd=GPIO,<pin>,0
i have tested with this last release and work well but after hours this stop the dhcp server and crash.
there are any change to put this feature working?
thanks
I am wondering if it is possible work esp easy only on AP mode, i try to put on standalone but dont stay, i think its because sidd and password not field.
i think that i has post this doubt on past, but i will descrived.
i have a gate that dont have any internet connetion but my idea are to put one android phone (app tasker) and espeasy with relay(connect each other with wifi by esp), so when i call to the phone the tasker will trigger the rule and ativated by http get the relay by http://<ESP IP address>/control?cmd=GPIO,<pin>,0
i have tested with this last release and work well but after hours this stop the dhcp server and crash.
there are any change to put this feature working?
thanks
Re: ESP Easy Releases
As i had to pause playing with the ESP for 2 weeks, what are the following new Settings/ Features ?
- Config / Main Settings / Controller Hostname ? (Could i use Name instead of IP ? )
- Advanced Settings / DST - i guess daylight saving time, is it set automatically, or do i have to Change it twice a year ?
- Advanced Settings / WD I2C Address ?
- Config / Main Settings / Controller Hostname ? (Could i use Name instead of IP ? )
- Advanced Settings / DST - i guess daylight saving time, is it set automatically, or do i have to Change it twice a year ?
- Advanced Settings / WD I2C Address ?
Re: ESP Easy Releases
This is a great addition - OTA makes it so much easier to update modules - especially those installed around the house!Martinus wrote:R68 is available on github:
- Fixes the CSS upload feature
- Adds OTA update using bin file upload through the ESP Easy webgui (NOT from arduino IDE):
- Jan
Jan Chrillesen, Denmark
Re: ESP Easy Releases
You are right. I'm currently running a total of 15 modules (production and test lab), being a mixture of ESP-01 and NodeMCU V1 modules. I have updated and tested them all using OTA and it's much faster and easier than serial update.chrille wrote:This is a great addition - OTA makes it so much easier to update modules - especially those installed around the house!
- Jan
Why didn't I add this earlier?
(to answer my own question: I thought we would need Arduino 1.6.7. and a lot of extra code, but it doesn't matter for bin file uploads. The feature came with ESP core 2.0.0. It's needs a webgui, but that was easy because we already had it running...)
I think in the future we can provide bin files for download so most people could skip all the hassle with Arduino IDE, libraries, ESP core etc etc.
Of course the initial build has to get uploaded the first time, but you can use the simple flash tools for that, so the whole process could be just 3 steps:
- Attachments
-
- FlashTool1.png (13.36 KiB) Viewed 43868 times
-
- FlashTool2.png (21.21 KiB) Viewed 43868 times
-
- FlashTool3.png (11.55 KiB) Viewed 43868 times
Re: ESP Easy Releases
I am also very happy about software OTA upload. One question though - normally, Arduino IDE sketches contain initial configuration of device name, etc. What should be put there in order for the device to keep configuration after upload?
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
I have been using OTA on several ESP8266 modules for some time - both the russian IOT software from http://www.wifi-iot.ru/ and ESPlink (https://github.com/jeelabs/esp-link) have support for this. This is much more simple - especially if have modules that are in enclosures and/or in remote locations (like server rooms or the green house)Martinus wrote:You are right. I'm currently running a total of 15 modules (production and test lab), being a mixture of ESP-01 and NodeMCU V1 modules. I have updated and tested them all using OTA and it's much faster and easier than serial update.
For various reasons I have been using this approach all the time. Compiling the software with the Arduino IDE on my Mac and programming the ESP8266 from a Raspberry Pi. Moving forward you could even put the latest image on a webserver and users could simple upgrade from "the cloud" without needing to download the software locally firstMartinus wrote: I think in the future we can provide bin files for download so most people could skip all the hassle with Arduino IDE, libraries, ESP core etc etc.
Of course the initial build has to get uploaded the first time, but you can use the simple flash tools for that, so the whole process could be just 3 steps:
- Jan
Jan Chrillesen, Denmark
Re: ESP Easy Releases
The settings you define in espeasy.ino are the default values - this is different from what is saved on flash. Uploading a .bin file that is compiled with different settings will not overwrite your current settings.mkotek wrote:I am also very happy about software OTA upload. One question though - normally, Arduino IDE sketches contain initial configuration of device name, etc. What should be put there in order for the device to keep configuration after upload?
- Jan
Jan Chrillesen, Denmark
Re: ESP Easy Releases
Perfect, thank you. I was not sure about it.chrille wrote:The settings you define in espeasy.ino are the default values - this is different from what is saved on flash. Uploading a .bin file that is compiled with different settings will not overwrite your current settings.mkotek wrote:I am also very happy about software OTA upload. One question though - normally, Arduino IDE sketches contain initial configuration of device name, etc. What should be put there in order for the device to keep configuration after upload?
- Jan
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
I am so happy! Seems to work like a charmMartinus wrote:R68 is available on github:
- Adds OTA update using bin file upload through the ESP Easy webgui (NOT from arduino IDE):
So you can export the binary from IDE and use the ESP Easy webgui to upload the file:
Re: ESP Easy Releases
I see the name of the bin is different from mine, which is ESPEasy.cpp.nodemcu.bin. is there also an actual difference in content?Martinus wrote: You are right. I'm currently running a total of 15 modules (production and test lab), being a mixture of ESP-01 and NodeMCU V1 modules. I have updated and tested them all using OTA and it's much faster and easier than serial update.
Why didn't I add this earlier?
(to answer my own question: I thought we would need Arduino 1.6.7. and a lot of extra code, but it doesn't matter for bin file uploads. The feature came with ESP core 2.0.0. It's needs a webgui, but that was easy because we already had it running...)
I think in the future we can provide bin files for download so most people could skip all the hassle with Arduino IDE, libraries, ESP core etc etc.
Of course the initial build has to get uploaded the first time, but you can use the simple flash tools for that, so the whole process could be just 3 steps:
Re: ESP Easy Releases
I was just playing around with different versions, mainly to see the difference after OTA flashing. If you flash the same version, would be hard to tell if it was actually replaced...BertB wrote:I see the name of the bin is different from mine, which is ESPEasy.cpp.nodemcu.bin. is there also an actual difference in content?
Re: ESP Easy Releases
On an ESP 8266-201 version first erased and then flashed with version 68.
Standard settings as they come from github.
Only change SSID and Password and controller IP to 192.168.1.19.
After reboot about 1,5 minute later I see the DHCP address and log in to the ESP EASY UI.
I see the Contoller IP is 192.168.1.19.
I change the IP adress of the ESP to 192.168.1.87 netmask to 255.255.255 and the gateway to 192.168.1.254
Thats all I change.
Then click submit.
browser screen refreshes and makes controller IP to 0.0.0.0 !
It accepts all other setting as I have to log in now on 192.168.1.87
I try to change the controller IP to 192.168.1.19 again and click submit.
Dang 0.0.0.0 again.
Do a reboot and try again but same issue.
Other 201 modul same problem.
To bug or not to bug that is the question.
Paco
Standard settings as they come from github.
Only change SSID and Password and controller IP to 192.168.1.19.
After reboot about 1,5 minute later I see the DHCP address and log in to the ESP EASY UI.
I see the Contoller IP is 192.168.1.19.
I change the IP adress of the ESP to 192.168.1.87 netmask to 255.255.255 and the gateway to 192.168.1.254
Thats all I change.
Then click submit.
browser screen refreshes and makes controller IP to 0.0.0.0 !
It accepts all other setting as I have to log in now on 192.168.1.87
I try to change the controller IP to 192.168.1.19 again and click submit.
Dang 0.0.0.0 again.
Do a reboot and try again but same issue.
Other 201 modul same problem.
To bug or not to bug that is the question.
Paco
Re: ESP Easy Releases
Just tested with upgrade from R68 to R69 - worked flawlessly!Martinus wrote:- Adds OTA update using bin file upload through the ESP Easy webgui (NOT from arduino IDE):
- Jan
Jan Chrillesen, Denmark
Re: ESP Easy Releases
The first I tried to upgrade ended up with blanked identity and does not want to be programmed anymore.
This is what I see:
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
INIT : Boot OK
INIT : Normal boot
ets Jan 8 2013,rst cause:4, boot mode:(3,7)
wdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
system param error
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
etc.
This is what I see:
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
INIT : Boot OK
INIT : Normal boot
ets Jan 8 2013,rst cause:4, boot mode:(3,7)
wdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
system param error
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
etc.
Re: ESP Easy Releases
This is what happens when you select the wrong deviceBertB wrote:The first I tried to upgrade ended up with blanked identity and does not want to be programmed anymore.
This is what I see:
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
INIT : Boot OK
INIT : Normal boot
ets Jan 8 2013,rst cause:4, boot mode:(3,7)
wdt reset
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
~ld
system param error
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Second try with another NodeMCY worked just fine.
Now I have to restore the NodeMCU with confused identity ... new occupation, ESP shrink
OTA R068 to 069
Hi Bert,
could u be so kind and explain the steps who would be made.
I had more ESP-12E and not one will accept OTA.
What had to set in arduino IDE NodeMCU 1.0 regarding Flash size? 4M-3M or 4M-1M,
both ended in a failure messsage.
And had I flash some files first using the NodeMCU Firmware Programmer to bring the "normal" ESP-12E to a NodeMCU,
and if yes: which files at which address?
best wishes and thx for yr help.
BerndJ
could u be so kind and explain the steps who would be made.
I had more ESP-12E and not one will accept OTA.
What had to set in arduino IDE NodeMCU 1.0 regarding Flash size? 4M-3M or 4M-1M,
both ended in a failure messsage.
And had I flash some files first using the NodeMCU Firmware Programmer to bring the "normal" ESP-12E to a NodeMCU,
and if yes: which files at which address?
best wishes and thx for yr help.
BerndJ
Re: ESP Easy Releases
Hi Bernd,
Do you have NodeMCU with ESP-12E? You probably have 4M flash.
In Arduino select NodeMCU 1.0 with Flash Size 4M(3M SPIFFS).
Did you succeed to load R068 on the board?
Do you have NodeMCU with ESP-12E? You probably have 4M flash.
In Arduino select NodeMCU 1.0 with Flash Size 4M(3M SPIFFS).
Did you succeed to load R068 on the board?
Re: ESP Easy Releases
Hi Bert,
"Did you succeed to load R068 on the board?"
No, i´ve got problems. One NodeMCUV2.0 and round about 9 pcs with own PCB with module 12E.
On 5 boards V068 is running but OTA is not possible, failure.
Also direct via serial line programming to V069 are making problems, mostly i got these message: entered Rescue Mode!
Meanwhile i tested 3 NodeMCU 0.9 with ESP-12.
Nice: these parts are making no problems progging to V068 and then via OTA to V069; it´s running; but i had no ESP-12 for my own pcb´s.
Thinking that there are problems regarding NodeMCU1.0 in Arduino or
there are existing some charges of the ESP-12E Modules with different memory programming outside the 0x00000
Tomorrow i will test 3 ESP-12F, hopeful that they are doing their job.
Any ideas to set up the 12E Modules to NodeMCU1.0
best wishes
Bernd
"Did you succeed to load R068 on the board?"
No, i´ve got problems. One NodeMCUV2.0 and round about 9 pcs with own PCB with module 12E.
On 5 boards V068 is running but OTA is not possible, failure.
Also direct via serial line programming to V069 are making problems, mostly i got these message: entered Rescue Mode!
Meanwhile i tested 3 NodeMCU 0.9 with ESP-12.
Nice: these parts are making no problems progging to V068 and then via OTA to V069; it´s running; but i had no ESP-12 for my own pcb´s.
Thinking that there are problems regarding NodeMCU1.0 in Arduino or
there are existing some charges of the ESP-12E Modules with different memory programming outside the 0x00000
Tomorrow i will test 3 ESP-12F, hopeful that they are doing their job.
Any ideas to set up the 12E Modules to NodeMCU1.0
best wishes
Bernd
Re: ESP Easy Releases
Hi,
supplement: until V068 i had all my ESP-12E flashed via "Generic ESP 8266 Module" and Flash Size "512KB (64KB SPIFFS)",
that´s the only and one way it´s running and compiling.
Now with OTA these generatet .bin files are not accepted.
Hope it helps.
Bernd
supplement: until V068 i had all my ESP-12E flashed via "Generic ESP 8266 Module" and Flash Size "512KB (64KB SPIFFS)",
that´s the only and one way it´s running and compiling.
Now with OTA these generatet .bin files are not accepted.
Hope it helps.
Bernd
Re: ESP Easy Releases
Remember OTA is working only on modules with >512KB. But that does not explain issues with uploading R68 via Arduino, unless there is some routine depending on Flash size.BerndJ wrote:Hi,
supplement: until V068 i had all my ESP-12E flashed via "Generic ESP 8266 Module" and Flash Size "512KB (64KB SPIFFS)",
that´s the only and one way it´s running and compiling.
Now with OTA these generatet .bin files are not accepted.
Hope it helps.
Bernd
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
I have loaded R70 onto my bare ESP 12E without any issues from Arduino IDE. Then I wanted to upload the very same R70 onto it using OTA.
The process went fine, ok has been shown, but the ESP has not rebooted itself. After waiting about 3 min, I have rebooted it manually and it is not running. I have connected COM port to see what is going on and at 74800 I can see the following:
That's it - OLED connected stays blank, ESP is not visible on the netwoerk (either regular or own AP).
I will repeat the test from the start, but for now, unknown failure.
UPDATE: Second upload has been succesful (first via Arduino IDE, then OTA) and ESP restarted on it's own without any delay, although loading same version, I was unable to confirm any changes. Will see with slightly changed R70 or next release .
The process went fine, ok has been shown, but the ESP has not rebooted itself. After waiting about 3 min, I have rebooted it manually and it is not running. I have connected COM port to see what is going on and at 74800 I can see the following:
Code: Select all
ets Jan 8 2013,rst cause:2, boot mode:(3,3)
ets_main.c
I will repeat the test from the start, but for now, unknown failure.
UPDATE: Second upload has been succesful (first via Arduino IDE, then OTA) and ESP restarted on it's own without any delay, although loading same version, I was unable to confirm any changes. Will see with slightly changed R70 or next release .
Last edited by mkotek on 22 Jan 2016, 16:17, edited 1 time in total.
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
Correct, but the problem here is, I think, that initially in some cases the wrong profile was used. Generic in stead of NodeMCU.mkotek wrote:Remember OTA is working only on modules with >512KB. But that does not explain issues with uploading R68 via Arduino, unless there is some routine depending on Flash size.BerndJ wrote:Hi,
supplement: until V068 i had all my ESP-12E flashed via "Generic ESP 8266 Module" and Flash Size "512KB (64KB SPIFFS)",
that´s the only and one way it´s running and compiling.
Now with OTA these generatet .bin files are not accepted.
Hope it helps.
Bernd
I had the same problem myself and could overcome this only by first loading an older release. I used R54. I think it is best to back to R20, then R39, then %48 and then R68. It is a long road and I do not understand the dynamics, but it helped. I first tried it with ESP8266Flahser.exe, with blank.bin, as described here http://internetofhomethings.com/homethings/?p=396, but it was no great success.
Re: ESP Easy Releases
Hi Bert,
could it be that we´re writing the settings to false adresses in mode 4M(3M SPIFFS).
It seems so, because when something went wrong i can see on the serial line that only the first two writings are succesfull, all others had failures.
Meanwhile I create the binfile under generic and 4M(3MB SPIFFS) because my own PCB´s did´nt had an USB Port and the mechanisn to set the progmode via NodeMCU. This runs, but only on the ones who are willing.
Idea: could the problem the flashing to 512KB on 4M Modules?
BTW: There are changes in SPIFFS, u need to format it, but that solves not the problem.
To my situation, very confused.
Found a next NodeMCU 1.0 and everything is running fine, the other one no chance
ESP-12E on own PCB´s:
2 running fine, one accept serial Flashing to V070, but FAIL at OTA, 2 with no chance.
ESP-01: 4 pieces progged serial with V070 in mode 512KB(64KB SPIFFS), running fine but OTA not possible.
Try yr way.
best wishes
Bernd
could it be that we´re writing the settings to false adresses in mode 4M(3M SPIFFS).
It seems so, because when something went wrong i can see on the serial line that only the first two writings are succesfull, all others had failures.
Meanwhile I create the binfile under generic and 4M(3MB SPIFFS) because my own PCB´s did´nt had an USB Port and the mechanisn to set the progmode via NodeMCU. This runs, but only on the ones who are willing.
Idea: could the problem the flashing to 512KB on 4M Modules?
BTW: There are changes in SPIFFS, u need to format it, but that solves not the problem.
To my situation, very confused.
Found a next NodeMCU 1.0 and everything is running fine, the other one no chance
ESP-12E on own PCB´s:
2 running fine, one accept serial Flashing to V070, but FAIL at OTA, 2 with no chance.
ESP-01: 4 pieces progged serial with V070 in mode 512KB(64KB SPIFFS), running fine but OTA not possible.
Try yr way.
best wishes
Bernd
Re: ESP Easy Releases
Hi,
Bert´s tips are checked and here is the result:
ESP-12E on own PCB´s
4M(3MB SPIFFS)
R020 OK
R039 Fail
R029 OK
R034 OK
R036 OK
R038 OK
R039 OK ??
R048 OK
R068 OK
OTA to R069, OTA to 070: OK
next one:
R020 OK
R038 Fail
R034 Fail
R029 OK
R048 OK
R068 OK
OTA to 070, need a hardware reset or loss of power!, not the best way for a unit in the wall.
NodeMCU 1.0
DevKit1
R029 no IP, but network OK, Hardwarereset --> get IP
R068 OK
OTA to 069, running fine
OTA to 070, also, perfect
Bert´s tips are checked and here is the result:
ESP-12E on own PCB´s
4M(3MB SPIFFS)
R020 OK
R039 Fail
R029 OK
R034 OK
R036 OK
R038 OK
R039 OK ??
R048 OK
R068 OK
OTA to R069, OTA to 070: OK
next one:
R020 OK
R038 Fail
R034 Fail
R029 OK
R048 OK
R068 OK
OTA to 070, need a hardware reset or loss of power!, not the best way for a unit in the wall.
NodeMCU 1.0
DevKit1
R029 no IP, but network OK, Hardwarereset --> get IP
R068 OK
OTA to 069, running fine
OTA to 070, also, perfect
Re: ESP Easy Releases
So ... something is weird, but in the end it works?BerndJ wrote:Hi,
OTA to 070, need a hardware reset or loss of power!, not the best way for a unit in the wall.
Re: ESP Easy Releases
Hi Bert,
this happens only if u prog directly from V068 to V070 via OTA.
u can avoid it by prog 068 to 069 to 070, this is running fine.
this happens only if u prog directly from V068 to V070 via OTA.
u can avoid it by prog 068 to 069 to 070, this is running fine.
Re: ESP Easy Releases
I have the same issue today with a fresh esp-12.BerndJ wrote:Hi Bert,
this happens only if u prog directly from V068 to V070 via OTA.
u can avoid it by prog 068 to 069 to 070, this is running fine.
Re: ESP Easy Releases
Hi Bert,
it seems Martinus has solved these problem.
just R070 via OTA direct to R072 flashed on 3 boards without problems, great work!
Thx a lot.
it seems Martinus has solved these problem.
just R070 via OTA direct to R072 flashed on 3 boards without problems, great work!
Thx a lot.
Re: ESP Easy Releases
Where can i find R072 i like to test..
Re: ESP Easy Releases
github, as always for non stable releases.Dylantje wrote:Where can i find R072 i like to test..
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
We’ve found 7,085 repository results:mkotek wrote:github, as always for non stable releases.Dylantje wrote:Where can i find R072 i like to test..
https://github.com/search?utf8=%E2%9C%9 ... rchresults
What is the good one?
Re: ESP Easy Releases
https://github.com/ESP8266nu/ESPEasyDylantje wrote:We’ve found 7,085 repository results:mkotek wrote:github, as always for non stable releases.Dylantje wrote:Where can i find R072 i like to test..
https://github.com/search?utf8=%E2%9C%9 ... rchresults
What is the good one?
But I suppose, you should start with http://esp8266.nu website, which will give you this link and introduce to a lot of other c9ncepts,including examples for different sensors/tasks. Good luck.
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
Thanks i did new the different between stable and developBerndJ wrote:https://github.com/ESP8266nu/ESPEasy
click on "download ZIP"
I download the library from the R048, and copy to library in my arduino setup
I did download espeasy-master, set this in my project map
open the easpeasy.ino
change my settings.
Get this error by compilation:
Code: Select all
ESPEasy.ino:178:37: fatal error: ESP8266HTTPUpdateServer.h: No such file or directory
compilation terminated.
Fout bij compileren.
What can i do
Re: ESP Easy Releases
Please open a new thread for your issue. This one is for info on new Releases of Easy ESP.Dylantje wrote:Thanks i did new the different between stable and developBerndJ wrote:https://github.com/ESP8266nu/ESPEasy
click on "download ZIP"
I download the library from the R048, and copy to library in my arduino setup
I did download espeasy-master, set this in my project map
open the easpeasy.ino
change my settings.
Get this error by compilation:Only the webserver is in my sketch: I did not have this error on my stable easpeasy version..Code: Select all
ESPEasy.ino:178:37: fatal error: ESP8266HTTPUpdateServer.h: No such file or directory compilation terminated. Fout bij compileren.
What can i do
You should download the ZIP file from hithub, unpack it where your Arduino files are and rename it to ESPEASY (that means no -master at the end). Next, you need to make sure, tour libraries are up to date (using core 2.0.0 stable) and open the espeasy,ino file from this folder. It should work fine then.
Please open a new thread and respond there, quoting this post if you still have an issue.
Michal 'Kotek', greetings from Poland. Zapraszam na mój blog o automatyce domowej po polsku: http://www.ukotka.com.
Re: ESP Easy Releases
It's time to get a new ESP Easy build out on SourceForge to replace R48. Assuming that R72 is better than it's predecessor.
So feature development will be stopped until this is accomplished.
We're currently at build R72 and this will be the starting point. We may have to do some bugfix builds and then update SourceForge. In the mean time, we should work on the Wiki pages to reflect the recent developments. Regarding bug reports on R72, we will only focus on "showstoppers".
At the same time, we're thinking of providing the bin files instead of source-code on SourceForge and maybe also as download file on esp8266.nu.
I guess many ESP8266 users just want to get the firmware loaded the easy way instead of all the hassle with Arduino IDE, libraries, board settings, etc..
With this step, we're aiming at making things even more 'Easy'.
So feature development will be stopped until this is accomplished.
We're currently at build R72 and this will be the starting point. We may have to do some bugfix builds and then update SourceForge. In the mean time, we should work on the Wiki pages to reflect the recent developments. Regarding bug reports on R72, we will only focus on "showstoppers".
At the same time, we're thinking of providing the bin files instead of source-code on SourceForge and maybe also as download file on esp8266.nu.
I guess many ESP8266 users just want to get the firmware loaded the easy way instead of all the hassle with Arduino IDE, libraries, board settings, etc..
With this step, we're aiming at making things even more 'Easy'.
Who is online
Users browsing this forum: No registered users and 3 guests