ESP Easy Releases
Moderators: grovkillen, Stuntteam, TD-er
Re: ESP Easy Releases
Bug in the ExtPulse command. R82, R83, R84.
The ExtPulse command behaves unpredictable.
This newly added command can let the I2C bus freeze, resulting in a ESP which cannot communicate with sensors, PME or display over I2C.
It only happens when the duration of the pulse is set to zero '0' and only with the ExtPulse and not with the ExtLongPulse command.
When giving the command http ://<ESPAddress>/control?cmd=EXTPulse,<pin>,<state>,0 the I2C bus hangs. This does not happen every time when launching the ExtPulse command with duration zero but only about one in three times.
To free the I2C bus again the PME Pro-Mini board needs a push on the reset button, so it seems the PME ls frozen and blocking the I2C bus.
It must be easy to prevent this blocking by making it impossible to accept a pulse-duration of zero milliseconds.
The ExtPulse command behaves unpredictable.
This newly added command can let the I2C bus freeze, resulting in a ESP which cannot communicate with sensors, PME or display over I2C.
It only happens when the duration of the pulse is set to zero '0' and only with the ExtPulse and not with the ExtLongPulse command.
When giving the command http ://<ESPAddress>/control?cmd=EXTPulse,<pin>,<state>,0 the I2C bus hangs. This does not happen every time when launching the ExtPulse command with duration zero but only about one in three times.
To free the I2C bus again the PME Pro-Mini board needs a push on the reset button, so it seems the PME ls frozen and blocking the I2C bus.
It must be easy to prevent this blocking by making it impossible to accept a pulse-duration of zero milliseconds.
Re: ESP Easy Releases
ESP8266.ru team create functions parser for ForwardDeclaration and try buld r82 with new UI and Arduino 1.6.7
- Attachments
-
- forward_declarations.zip
- (21.94 KiB) Downloaded 493 times
Re: ESP Easy Releases
Arduino 1.6.8 is out now. The workaround for prototyping functions is no longer needed and ESP Easy compiles again without issues.
Re: ESP Easy Releases
Currently test-driving ESP Easy R85 on core 2.1.0 in the test lab. So far looking good, although the newer Servo library has issues.
I replaced this library with the 2.0.0. version and that fixes the exception crashes.
I replaced this library with the 2.0.0. version and that fixes the exception crashes.
Re: ESP Easy Releases
Hey, wonderful to hear.
Maybe the PN532 RFID Reader improves, too?
Keep on good Work, if you can..
Maybe the PN532 RFID Reader improves, too?
Keep on good Work, if you can..
Re: ESP Easy Releases
i am testing this last update with 1 ds18b20 to send with auth for a outdoor domoticz (hostname) and pass 1300 minutes without problems.
thanks martinus
thanks martinus
Re: ESP Easy Releases
Initially, I had a lot of problems to get arduino 1.6.8 working, but they all vanished after I created a separate portable version of it.
So, now it seems to compile.
So, now it seems to compile.
Re: ESP Easy Releases
@martinus,
what is this feature for? : // base64 encoding for HTTP authentication in C001
what is this feature for? : // base64 encoding for HTTP authentication in C001
Re: ESP Easy Releases
Congratulations to the latest version, I think on the authentication to Domoticz server,works flawlessly.
Re: ESP Easy Releases
When I start arduino 1.6.8 in a portable environment, with ESP_Core 210, it sometimes says that there is an update for libraries.
When I let arduino to update them (in this case PubSubClient and LiquidCrystal_I2C) I get errors during compilation.
How can I be sure that un update proposed by arduino is ok for our ESPEasy?
When I let arduino to update them (in this case PubSubClient and LiquidCrystal_I2C) I get errors during compilation.
How can I be sure that un update proposed by arduino is ok for our ESPEasy?
Re: ESP Easy Releases
You can't. Automatic updates can be a really bad idea if the library looses backwards compatibility while evolving. Some times you will get a 'deprecated' compiler warning so at least you know that someday it will stop working...BertB wrote:When I start arduino 1.6.8 in a portable environment, with ESP_Core 210, it sometimes says that there is an update for libraries.
When I let arduino to update them (in this case PubSubClient and LiquidCrystal_I2C) I get errors during compilation.
How can I be sure that un update proposed by arduino is ok for our ESPEasy?
Re: ESP Easy Releases
Not really a roadmap, but the wish list summary has been updated with some status information.
The green items will be available in the next ESP Easy edition that will also start to use Arduino Core 2.1.0.
It can be build without compiler errors in Arduino 1.6.8. (do NOT use Arduino 1.6.7.)
Wish list summary/status:
http://www.esp8266.nu/forum/viewtopic.php?f=2&t=736
I'd like to encourage some beta testers to have a go with R88.
Important note: Internal data storage structure has changed. The new firmware should migrate the settings, so you should not notice the difference. But restoring settings from file from pre R88 versions will not work properly. Best to save these settings again after moving to R88.
The green items will be available in the next ESP Easy edition that will also start to use Arduino Core 2.1.0.
It can be build without compiler errors in Arduino 1.6.8. (do NOT use Arduino 1.6.7.)
Wish list summary/status:
http://www.esp8266.nu/forum/viewtopic.php?f=2&t=736
I'd like to encourage some beta testers to have a go with R88.
Important note: Internal data storage structure has changed. The new firmware should migrate the settings, so you should not notice the difference. But restoring settings from file from pre R88 versions will not work properly. Best to save these settings again after moving to R88.
Re: ESP Easy Releases
I tried R88, and I get an error compiling.
ESPEasy.ino:203:22: fatal error: Base64.h: No such file or directory
Am I doing something wrong?
ESPEasy.ino:203:22: fatal error: Base64.h: No such file or directory
Am I doing something wrong?
Re: ESP Easy Releases
@Martinus
I got this:
WD : Uptime 0 ConnectFailures 0 FreeMem 27544
ADC : Analog value: 51
Update: ESPEasy.ino.nodemcu_088.bin
sleep disable
.............................................................................................................................LmacRxBlk:1
and many more :
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
Then I did a rst the ESP-12 and this happened:
INIT : Booting Build nr:87
IP : Static IP :192.168.0.64
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
MQTT : Connected to broker
Subscribed to: domoticz/out
INIT : Boot OK
INIT : Normal boot
Update: ESPEasy.ino.nodemcu_088.bin
sleep disable
..................................................................................................................................................................................................Update Success: 396592
Rebooting...
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
@cp:0
ld
ªU
Build changed!
Fix extratasksettings
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
INIT : Booting Build nr:88
IP : Static IP :192.168.0.64
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
MQTT : Connected to broker
Subscribed to: domoticz/out
INIT : Boot OK
INIT : Cold Boot
WD : Uptime 0 ConnectFailures 0 FreeMem 27368
ADC : Analog value: 64
Seems okay now.
After that, I did two others without problems.
In total, I loaded R88 to 8 ESPs among them:
3 NodeMCU
1 Wemos D1 mini
3 Plain ESP-12
1 Plain ESP-12-F
I needed to reset 3 of them.
I got this:
WD : Uptime 0 ConnectFailures 0 FreeMem 27544
ADC : Analog value: 51
Update: ESPEasy.ino.nodemcu_088.bin
sleep disable
.............................................................................................................................LmacRxBlk:1
and many more :
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
LmacRxBlk:1
Then I did a rst the ESP-12 and this happened:
INIT : Booting Build nr:87
IP : Static IP :192.168.0.64
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
MQTT : Connected to broker
Subscribed to: domoticz/out
INIT : Boot OK
INIT : Normal boot
Update: ESPEasy.ino.nodemcu_088.bin
sleep disable
..................................................................................................................................................................................................Update Success: 396592
Rebooting...
ets Jan 8 2013,rst cause:2, boot mode:(3,7)
load 0x4010f000, len 1264, room 16
tail 0
chksum 0x42
csum 0x42
@cp:0
ld
ªU
Build changed!
Fix extratasksettings
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
FLASH: Settings saved
INIT : Booting Build nr:88
IP : Static IP :192.168.0.64
WIFI : Connecting... 1
WIFI : Connected!
INIT : I2C
MQTT : Connected to broker
Subscribed to: domoticz/out
INIT : Boot OK
INIT : Cold Boot
WD : Uptime 0 ConnectFailures 0 FreeMem 27368
ADC : Analog value: 64
Seems okay now.
After that, I did two others without problems.
In total, I loaded R88 to 8 ESPs among them:
3 NodeMCU
1 Wemos D1 mini
3 Plain ESP-12
1 Plain ESP-12-F
I needed to reset 3 of them.
Re: ESP Easy Releases
It seems that Gloabl sync checkbox does not appear for al devices. At least DS18B20 lacks one.
Re: ESP Easy Releases
I'm trying to build R90 with Arduino 1.6.8 and ESP Core 2.1.0 rc2
Code: Select all
Arduino: 1.6.8 (Windows 8.1), Board:"Generic ESP8266 Module, Serial, 80 MHz, 40MHz, DIO, 115200, 1M (256K SPIFFS), ck, Disabled, None"
Build-opties gewijzigd, alles wordt opnieuw gebuild
C:\Users\Philippe\Documents\Arduino\ESPEasyR90\Hardware.ino: In function 'void hardwareInit()':
Hardware:41: error: 'class TwoWire' has no member named 'setClockStretchLimit'
Wire.setClockStretchLimit(Settings.WireClockStretchLimit);
^
C:\Users\Philippe\Documents\Arduino\ESPEasyR90\_P020_Ser2Net.ino: In function 'boolean Plugin_020(byte, EventStruct*, String&)':
_P020_Ser2Net:116: error: 'SerialConfig' was not declared in this scope
Serial.begin(ExtraTaskSettings.TaskDevicePluginConfigLong[1], (SerialConfig)serialconfig);
^
exit status 1
'class TwoWire' has no member named 'setClockStretchLimit'
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Re: ESP Easy Releases
I was using the staging versions, using the 2.1.0 stable tree everything compiled just fine.
Is there documentation regarding the rules. Can one make rules like "if GPIO0 = 1 then GPIO14 = 1 else GPIO14 = 0" ?
Is there documentation regarding the rules. Can one make rules like "if GPIO0 = 1 then GPIO14 = 1 else GPIO14 = 0" ?
Re: ESP Easy Releases
Hij. I AM werking on that. Hope to put some initial stuff in a wiki today.
Re: ESP Easy Releases
Great! Keen to try it out.
Re: ESP Easy Releases
Well ... did you?
Try it, I mean.
Try it, I mean.
Re: ESP Easy Releases
I posted this in the Sonoff hardware threadBertB wrote:Well ... did you?
Try it, I mean.
It's working fine, thanks for the docfluppie wrote:I used the new R91 release with rules to control the Sonoff relay with the button and get feedback from the led:
Code: Select all
on SW_1#Switch do if [SW_1#Switch]=0 gpio,12,0 gpio,13,1 else gpio,12,1 gpio,13,0 endif endon
Re: ESP Easy Releases
BertB, where can i find that Wiki? I can't find it or i missed in the WikiBertB wrote:Hij. I AM werking on that. Hope to put some initial stuff in a wiki today.
Re: ESP Easy Releases
Thanks, fluppie. Make a bookmark of itfluppie wrote:http://www.esp8266.nu/index.php/Tutorial_Rules
Re: ESP Easy Releases
Trying to compile R92 using instructions here http://www.esp8266.nu/index.php/Tutoria ... are_Upload and get the following error.
1.6.8 Portable with 2.10 and board NodeMCU 1.0 (ESP-12E Module)
Am I missing something obvious?
Code: Select all
sketch\TinyI2CWatchdog\TinyWireS_Custom\usiTwiSlave.c:41:20: fatal error: avr/io.h: No such file or directory
#include <avr/io.h>
Am I missing something obvious?
Numerous Sonoff's and Shelly's, Home Assistant on Intel NUC i3, Aeotec Z-Stick (Gen 5), deCONZ Zigbee Stick, 3 x Echo Dot's and 5 x Google Home
Re: ESP Easy Releases
just move folder TinyI2CWatchdog out of ESPEasy project. That solved this error for me...xbmcnut wote1.6.8 Portable with 2.10 and board NodeMCU 1.0 (ESP-12E Module)Code: Select all
sketch\TinyI2CWatchdog\TinyWireS_Custom\usiTwiSlave.c:41:20: fatal error: avr/io.h: No such file or directory #include <avr/io.h>
Am I missing something obvious?
BTW: what is the need/use for TinyI2CWatchdog ?
Re: ESP Easy Releases
@Martinus,
Ik heb dezelfde fout met 094 en 095. Niet met 093 en ervoor
Arduino: 1.6.8 (Windows Vista), Board:"NodeMCU 1.0 (ESP-12E Module), 80 MHz, Serial, 115200, 4M (3M SPIFFS)"
sketch\TinyI2CWatchdog\TinyWireS_Custom\usiTwiSlave.c:41:20: fatal error: avr/io.h: No such file or directory
#include <avr/io.h>
^
compilation terminated.
exit status 1
Error compiling for board NodeMCU 1.0 (ESP-12E Module).
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Ik heb dezelfde fout met 094 en 095. Niet met 093 en ervoor
Arduino: 1.6.8 (Windows Vista), Board:"NodeMCU 1.0 (ESP-12E Module), 80 MHz, Serial, 115200, 4M (3M SPIFFS)"
sketch\TinyI2CWatchdog\TinyWireS_Custom\usiTwiSlave.c:41:20: fatal error: avr/io.h: No such file or directory
#include <avr/io.h>
^
compilation terminated.
exit status 1
Error compiling for board NodeMCU 1.0 (ESP-12E Module).
This report would have more information with
"Show verbose output during compilation"
option enabled in File -> Preferences.
Re: ESP Easy Releases
Thanks. I had removed the folder several times but without closing Arduino! Removed and reopened and it compiled just fine.micha wrote:
just move folder TinyI2CWatchdog out of ESPEasy project. That solved this error for me...
BTW: what is the need/use for TinyI2CWatchdog ?
Numerous Sonoff's and Shelly's, Home Assistant on Intel NUC i3, Aeotec Z-Stick (Gen 5), deCONZ Zigbee Stick, 3 x Echo Dot's and 5 x Google Home
-
- Normal user
- Posts: 25
- Joined: 20 Mar 2016, 17:38
Re: ESP Easy Releases
i develop a scketch for sending valude to french domotic system JEEDOM...
this scketch is _C009.ino, can anyone include it to the futur release
thanks .....
here the code :
//#######################################################################################################
//########################### Controller Plugin 009: Jeedom #########################################
//#######################################################################################################
#define CPLUGIN_009
#define CPLUGIN_ID_009 9
#define CPLUGIN_NAME_009 "Jeedom HTTP"
boolean CPlugin_009(byte function, struct EventStruct *event, String& string)
{
boolean success = false;
switch (function)
{
case CPLUGIN_PROTOCOL_ADD:
{
Protocol[++protocolCount].Number = CPLUGIN_ID_009;
Protocol[protocolCount].usesMQTT = false;
Protocol[protocolCount].usesAccount = false;
Protocol[protocolCount].usesPassword = true;
Protocol[protocolCount].defaultPort = 80;
break;
}
case CPLUGIN_GET_DEVICENAME:
{
string = F(CPLUGIN_NAME_009);
break;
}
case CPLUGIN_PROTOCOL_SEND:
{
char log[80];
boolean success = false;
char host[20];
sprintf_P(host, PSTR("%u.%u.%u.%u"), Settings.Controller_IP[0], Settings.Controller_IP[1], Settings.Controller_IP[2], Settings.Controller_IP[3]);
sprintf_P(log, PSTR("%s%s using port %u"), "HTTP : connecting to ", host,Settings.ControllerPort);
addLog(LOG_LEVEL_DEBUG, log);
// Use WiFiClient class to create TCP connections
WiFiClient client;
if (!client.connect(host, Settings.ControllerPort))
{
connectionFailures++;
strcpy_P(log, PSTR("HTTP : connection failed"));
addLog(LOG_LEVEL_ERROR, log);
return false;
}
statusLED(true);
if (connectionFailures)
connectionFailures--;
String postDataStr = SecuritySettings.ControllerPassword; // "0UDNN17RW6XAS2E5" // api key for jeedom
switch (event->sensorType)
{
case SENSOR_TYPE_SINGLE: // single value sensor, used for Dallas, BH1750, etc
case SENSOR_TYPE_SWITCH:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
break;
case SENSOR_TYPE_TEMP_HUM: // dual value
case SENSOR_TYPE_TEMP_BARO:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postDataStr += F("&field");
postDataStr += event->idx + 1;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 1],ExtraTaskSettings.TaskDeviceValueDecimals[1]);
break;
case SENSOR_TYPE_TEMP_HUM_BARO:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postDataStr += F("&field");
postDataStr += event->idx + 1;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 1],ExtraTaskSettings.TaskDeviceValueDecimals[1]);
postDataStr += F("&field");
postDataStr += event->idx + 2;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 2],ExtraTaskSettings.TaskDeviceValueDecimals[2]);
break;
}
postDataStr += F("\r\n\r\n");
String postStr = F("POST ");
postStr += F("/jeedom/core/api/jeeApi.php?apikey=");
postStr += SecuritySettings.ControllerPassword;
postStr += F("&type=virtual&id=");
postStr += event->idx;
postStr += F("& HTTP/1.1\n");
postStr += F("Host: ");
postStr += host;
postStr += ("\n");
postStr += F("Connection: close\n");
postStr += F("Content-Type: application/x-www-form-urlencoded\n");
postStr += F("Content-Length: ");
postDataStr = F("value=");
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postStr += postDataStr.length();
postStr += F("\n\n");
postStr += postDataStr;
// This will send the request to the server
client.print(postStr);
unsigned long timer = millis() + 200;
while (!client.available() && millis() < timer)
delay(1);
// Read all the lines of the reply from server and print them to Serial
while (client.available()) {
String line = client.readStringUntil('\n');
line.toCharArray(log, 80);
addLog(LOG_LEVEL_DEBUG_MORE, log);
if (line.substring(0, 15) == "HTTP/1.1 200 OK")
{
strcpy_P(log, PSTR("HTTP : Succes!"));
addLog(LOG_LEVEL_DEBUG, log);
success = true;
}
delay(1);
}
strcpy_P(log, PSTR("HTTP : closing connection"));
addLog(LOG_LEVEL_DEBUG, log);
client.flush();
client.stop();
break;
}
}
return success;
}
this scketch is _C009.ino, can anyone include it to the futur release
thanks .....
here the code :
//#######################################################################################################
//########################### Controller Plugin 009: Jeedom #########################################
//#######################################################################################################
#define CPLUGIN_009
#define CPLUGIN_ID_009 9
#define CPLUGIN_NAME_009 "Jeedom HTTP"
boolean CPlugin_009(byte function, struct EventStruct *event, String& string)
{
boolean success = false;
switch (function)
{
case CPLUGIN_PROTOCOL_ADD:
{
Protocol[++protocolCount].Number = CPLUGIN_ID_009;
Protocol[protocolCount].usesMQTT = false;
Protocol[protocolCount].usesAccount = false;
Protocol[protocolCount].usesPassword = true;
Protocol[protocolCount].defaultPort = 80;
break;
}
case CPLUGIN_GET_DEVICENAME:
{
string = F(CPLUGIN_NAME_009);
break;
}
case CPLUGIN_PROTOCOL_SEND:
{
char log[80];
boolean success = false;
char host[20];
sprintf_P(host, PSTR("%u.%u.%u.%u"), Settings.Controller_IP[0], Settings.Controller_IP[1], Settings.Controller_IP[2], Settings.Controller_IP[3]);
sprintf_P(log, PSTR("%s%s using port %u"), "HTTP : connecting to ", host,Settings.ControllerPort);
addLog(LOG_LEVEL_DEBUG, log);
// Use WiFiClient class to create TCP connections
WiFiClient client;
if (!client.connect(host, Settings.ControllerPort))
{
connectionFailures++;
strcpy_P(log, PSTR("HTTP : connection failed"));
addLog(LOG_LEVEL_ERROR, log);
return false;
}
statusLED(true);
if (connectionFailures)
connectionFailures--;
String postDataStr = SecuritySettings.ControllerPassword; // "0UDNN17RW6XAS2E5" // api key for jeedom
switch (event->sensorType)
{
case SENSOR_TYPE_SINGLE: // single value sensor, used for Dallas, BH1750, etc
case SENSOR_TYPE_SWITCH:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
break;
case SENSOR_TYPE_TEMP_HUM: // dual value
case SENSOR_TYPE_TEMP_BARO:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postDataStr += F("&field");
postDataStr += event->idx + 1;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 1],ExtraTaskSettings.TaskDeviceValueDecimals[1]);
break;
case SENSOR_TYPE_TEMP_HUM_BARO:
postDataStr += F("&field");
postDataStr += event->idx;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postDataStr += F("&field");
postDataStr += event->idx + 1;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 1],ExtraTaskSettings.TaskDeviceValueDecimals[1]);
postDataStr += F("&field");
postDataStr += event->idx + 2;
postDataStr += "=";
postDataStr += toString(UserVar[event->BaseVarIndex + 2],ExtraTaskSettings.TaskDeviceValueDecimals[2]);
break;
}
postDataStr += F("\r\n\r\n");
String postStr = F("POST ");
postStr += F("/jeedom/core/api/jeeApi.php?apikey=");
postStr += SecuritySettings.ControllerPassword;
postStr += F("&type=virtual&id=");
postStr += event->idx;
postStr += F("& HTTP/1.1\n");
postStr += F("Host: ");
postStr += host;
postStr += ("\n");
postStr += F("Connection: close\n");
postStr += F("Content-Type: application/x-www-form-urlencoded\n");
postStr += F("Content-Length: ");
postDataStr = F("value=");
postDataStr += toString(UserVar[event->BaseVarIndex],ExtraTaskSettings.TaskDeviceValueDecimals[0]);
postStr += postDataStr.length();
postStr += F("\n\n");
postStr += postDataStr;
// This will send the request to the server
client.print(postStr);
unsigned long timer = millis() + 200;
while (!client.available() && millis() < timer)
delay(1);
// Read all the lines of the reply from server and print them to Serial
while (client.available()) {
String line = client.readStringUntil('\n');
line.toCharArray(log, 80);
addLog(LOG_LEVEL_DEBUG_MORE, log);
if (line.substring(0, 15) == "HTTP/1.1 200 OK")
{
strcpy_P(log, PSTR("HTTP : Succes!"));
addLog(LOG_LEVEL_DEBUG, log);
success = true;
}
delay(1);
}
strcpy_P(log, PSTR("HTTP : closing connection"));
addLog(LOG_LEVEL_DEBUG, log);
client.flush();
client.stop();
break;
}
}
return success;
}
Re: ESP Easy Releases
Hello,
When can we expect a new stable release as successor of the ESP Build 78 firmware?
When can we expect a new stable release as successor of the ESP Build 78 firmware?
Re: ESP Easy Releases
May I please ask what the IDE version and ESP boards versions are to compile the latest source?
I can compile R78 with 1.6.5 and ESP 2.0.0 but it fails using the latest (108) code.
Thank you
I can compile R78 with 1.6.5 and ESP 2.0.0 but it fails using the latest (108) code.
Thank you
Re: ESP Easy Releases
Just use ESP Core 2.1.0 and it will compile.jram wrote:May I please ask what the IDE version and ESP boards versions are to compile the latest source?
I can compile R78 with 1.6.5 and ESP 2.0.0 but it fails using the latest (108) code.
Thank you
Look at the first line in the source code, it says:
#define ESP_CORE 210
Re: ESP Easy Releases
I understand that I need the Arduino IDE version 1.6.5 (preferably installed as portable), the libraries that come with the latest stable release, and ESP core 2.1.0 to compile the current github code. My problem: Arduino IDE 1.6.5 doesn't play nice with the proxy I am behind. Recent versions of the IDE allow me to enter the proxy pac URL, 1.6.5 doesn't. Has somebody already overcome this obstacle?
Re: ESP Easy Releases
As some users seem to struggle with compiling and such, i've decided to launch a new downloadable stable build (R108) to close the gap between existing R78.
The rules feature seems stable and is no longer labeled "experimental". Most recent versions have been running smooth in my own home situation, so i think this is a good candidate to replace R78 out in the field...
I used OTA on all my unit's to get to this release, no issues encountered.
http://www.esp8266.nu/index.php/Main_Page#Downloads
The rules feature seems stable and is no longer labeled "experimental". Most recent versions have been running smooth in my own home situation, so i think this is a good candidate to replace R78 out in the field...
I used OTA on all my unit's to get to this release, no issues encountered.
http://www.esp8266.nu/index.php/Main_Page#Downloads
Re: ESP Easy Releases
Thanks MartinusAs some users seem to struggle with compiling and such, i've decided to launch a new downloadable stable build (R108) to close the gap between existing R78.
Re: ESP Easy Releases
Thank you! Flashing from the command line to an Wemos D1 mini went without a hitch.Martinus wrote:As some users seem to struggle with compiling and such, i've decided to launch a new downloadable stable build (R108) to close the gap between existing R78.
-
- Normal user
- Posts: 31
- Joined: 09 Feb 2016, 22:16
Re: ESP Easy Releases
Great work! Looking forward to test it, been on 78 since it was released.Martinus wrote:As some users seem to struggle with compiling and such, i've decided to launch a new downloadable stable build (R108) to close the gap between existing R78.
The rules feature seems stable and is no longer labeled "experimental". Most recent versions have been running smooth in my own home situation, so i think this is a good candidate to replace R78 out in the field...
I used OTA on all my unit's to get to this release, no issues encountered.
http://www.esp8266.nu/index.php/Main_Page#Downloads
Re: ESP Easy Releases
Hello,
I've got a serious problem with updating of my ESP's. I have 3x ESP-01 and 1x Sonof with R78. Working without any problem. Today i started with updating the devices with R105. I used EasyOTA, but all the devices didn't work any more, the Blue Led of Wifi was burning very bright and that's it's. What i have done is go back to R78 and then update it using the esptool as flash program. Now 3x ESP working again. The fourth i use for testing on this moment, but OTA isn't working. My question, i used only tools on board of the ESP, why did that not work? What do i wrong and has anyone a solution.
I've got a serious problem with updating of my ESP's. I have 3x ESP-01 and 1x Sonof with R78. Working without any problem. Today i started with updating the devices with R105. I used EasyOTA, but all the devices didn't work any more, the Blue Led of Wifi was burning very bright and that's it's. What i have done is go back to R78 and then update it using the esptool as flash program. Now 3x ESP working again. The fourth i use for testing on this moment, but OTA isn't working. My question, i used only tools on board of the ESP, why did that not work? What do i wrong and has anyone a solution.
Re: ESP Easy Releases
You're using the 'black' editions of ESP-01?ManS-H wrote:Hello,
I've got a serious problem with updating of my ESP's. I have 3x ESP-01 and 1x Sonof with R78. Working without any problem. Today i started with updating the devices with R105. I used EasyOTA, but all the devices didn't work any more, the Blue Led of Wifi was burning very bright and that's it's. What i have done is go back to R78 and then update it using the esptool as flash program. Now 3x ESP working again. The fourth i use for testing on this moment, but OTA isn't working. My question, i used only tools on board of the ESP, why did that not work? What do i wrong and has anyone a solution.
Can you try with ESPEasy_R108_1024.bin from our website? (assuming it was originally flashed with ESPEasy_R78_1024.bin)?
Does the upload using the webgui result in "OK" ?
Is there any output on serial after uploading.
Re: ESP Easy Releases
Hallo Martinus, yep i used the Black Editions of the ESP-01, i tried your suggestions with two new ESP-01. But no result, those two are not usual for this moment. Is the a way to clear all info of the ESP's? the RX-TX trick isn't working. I send the log file as a PM.Martinus wrote:You're using the 'black' editions of ESP-01?ManS-H wrote:Hello,
I've got a serious problem with updating of my ESP's. I have 3x ESP-01 and 1x Sonof with R78. Working without any problem. Today i started with updating the devices with R105. I used EasyOTA, but all the devices didn't work any more, the Blue Led of Wifi was burning very bright and that's it's. What i have done is go back to R78 and then update it using the esptool as flash program. Now 3x ESP working again. The fourth i use for testing on this moment, but OTA isn't working. My question, i used only tools on board of the ESP, why did that not work? What do i wrong and has anyone a solution.
Can you try with ESPEasy_R108_1024.bin from our website? (assuming it was originally flashed with ESPEasy_R78_1024.bin)?
Does the upload using the webgui result in "OK" ?
Is there any output on serial after uploading.
Re: ESP Easy Releases
Try this to erase Flash ?
http://www.esp8266.nu/forum/viewtopic.p ... 1732#p8014
http://www.esp8266.nu/forum/viewtopic.p ... 1732#p8014
Re: ESP Easy Releases
I will, but what program must i use with this command?tozett wrote:Try this to erase Flash ?
http://www.esp8266.nu/forum/viewtopic.p ... 1732#p8014
C:\Espressif\utils>esptool.py -p COM3 -b 115200 erase_flash
Update:
C:\Python27>esptool.py -p COM4 -b 115200 erase_flash
Connecting...
A fatal error occurred: Failed to connect to ESP8266
C:\Python27>esptool.py -p COM4 -b 115200 erase_flash
Connecting...
To night i made first a descend print instead of a breadboard for programming the ESP-01
Last edited by ManS-H on 19 Jul 2016, 13:27, edited 1 time in total.
Re: ESP Easy Releases
Based on the logfiles, it looks like the ESP crashes from within some early stage in the SDK and it never gets to the ESP Easy application. This can happen if a certain flash area gets corrupted. So the only way is to erase the flash with some other tool.
When i have time, i will try to run tests on ESP-01 black version and see if i can reproduce this behavior. I normally upgrade using OTA more frequently so my 'steps' in build versions are much smaller.
When i have time, i will try to run tests on ESP-01 black version and see if i can reproduce this behavior. I normally upgrade using OTA more frequently so my 'steps' in build versions are much smaller.
Re: ESP Easy Releases
R113 is available on github. It fixes an inconvenient bug within rules processing where devices with multiple values are involved.
Only the first value would create a valid event.
Only the first value would create a valid event.
Re: ESP Easy Releases
After a week of trying different configurations i decided to stop for the moment with ESPEasy.Martinus wrote:Based on the logfiles, it looks like the ESP crashes from within some early stage in the SDK and it never gets to the ESP Easy application. This can happen if a certain flash area gets corrupted. So the only way is to erase the flash with some other tool.
When i have time, i will try to run tests on ESP-01 black version and see if i can reproduce this behavior. I normally upgrade using OTA more frequently so my 'steps' in build versions are much smaller.
Programming a ESP-01 with a serial connection works, R77, R78 and R108.
I tried to update the ESP's loaded with R77 or R78 with OTA to R108 it didn't work.
When i go in the past from R77 to R78 i updated the ESP-01 with OTA tot R78, no problem.
Now with brand new ESP's it doesn't work. Even other programs to erase the ESP give not a solution.
I started programming ESP's with USB To RS232 TTL PL2303HX Auto Converter Module Converter Adapter for Arduino, but that one doesn't work anymore.
So i bought a new one: Arduino-programmer, CH340-programmer voor "Arduino Pro" boards
Can this be a reason of my problems?
Re: ESP Easy Releases
Because the current R108, marked stable, still contains some bugs, it would be better to replace it with a newer version. R114 is available for evaluation. We moved to a newer MQTT client, it may improve connection issues. We also moved to Arduino core 2.3.0 because the 2.1.0 has issues with the servo library.
With this build, only core 2.3.0 is supported, so you need to upgrade the core package. I had some issues with the core upgrade, so i decided to download and configure a brand new portable setup using Arduino 1.6.9 with a fresh core 2.3.0 install.
R114 has been running for a week now in my environment. I successfully upgraded all my unit's using OTA. (NodeMCU 1.0 and ESP-01 black editions)
Changes since R108:
// Cleanup code, conditional core 2.0.0/2.1.0 support removed, changed to core 2.3.0
// Bugfix in rules processing with multiple value devices, only the first value would work as expected
// Bugfix for timezones other than whole hours offset. It is now set in +/- minutes
// Bugfix parsing rfid (SENSOR_TYPE_LONG) values in parseTemplate function
// Improved Serial Server plugin, reconnect handling
// Improved thingspeak and emoncms plugins (contributed by pm-cz)
// Fix HTU21d timing
// Moved to pubsubclient 2.6 library (source no longer compatible with 1.9 library, so use the 2.6 version!)
With this build, only core 2.3.0 is supported, so you need to upgrade the core package. I had some issues with the core upgrade, so i decided to download and configure a brand new portable setup using Arduino 1.6.9 with a fresh core 2.3.0 install.
R114 has been running for a week now in my environment. I successfully upgraded all my unit's using OTA. (NodeMCU 1.0 and ESP-01 black editions)
Changes since R108:
// Cleanup code, conditional core 2.0.0/2.1.0 support removed, changed to core 2.3.0
// Bugfix in rules processing with multiple value devices, only the first value would work as expected
// Bugfix for timezones other than whole hours offset. It is now set in +/- minutes
// Bugfix parsing rfid (SENSOR_TYPE_LONG) values in parseTemplate function
// Improved Serial Server plugin, reconnect handling
// Improved thingspeak and emoncms plugins (contributed by pm-cz)
// Fix HTU21d timing
// Moved to pubsubclient 2.6 library (source no longer compatible with 1.9 library, so use the 2.6 version!)
Re: ESP Easy Releases
******** Solved by deleting everything in C:\Users\xxx\AppData\Local\Arduino15 after installing 1.6.9 ********
I'm sure I'm doing something dumb, but anyone know what the issue it is?
I downloaded 1.6.9, also updated the 2.3.0 also Pubsubclient updated to 2.6.0
but when ever I try to 'export compiled binary' I get an error with R114 22-07-2016 ...
... 'Arduino: 1.6.9 (Windows 10), Board: "NodeMCU 1.0 (ESP-12E Module), 80 MHz, 115200, 4M (1M SPIFFS)"
Board nodemcuv2 (platform esp8266, package esp8266) is unknown
Error compiling for board NodeMCU 1.0 (ESP-12E Module).
I then try other boards and get the same error..
Arduino: 1.6.9 (Windows 10), Board: "Generic ESP8266 Module, 80 MHz, 40MHz, DIO, 115200, 4M (1M SPIFFS), ck, Disabled, None"
Board generic (platform esp8266, package esp8266) is unknown
Error compiling for board Generic ESP8266 Module.
******** Solved by deleting everything in C:\Users\xxx\AppData\Local\Arduino15 after installing 1.6.9 ********
I'm sure I'm doing something dumb, but anyone know what the issue it is?
I downloaded 1.6.9, also updated the 2.3.0 also Pubsubclient updated to 2.6.0
but when ever I try to 'export compiled binary' I get an error with R114 22-07-2016 ...
... 'Arduino: 1.6.9 (Windows 10), Board: "NodeMCU 1.0 (ESP-12E Module), 80 MHz, 115200, 4M (1M SPIFFS)"
Board nodemcuv2 (platform esp8266, package esp8266) is unknown
Error compiling for board NodeMCU 1.0 (ESP-12E Module).
I then try other boards and get the same error..
Arduino: 1.6.9 (Windows 10), Board: "Generic ESP8266 Module, 80 MHz, 40MHz, DIO, 115200, 4M (1M SPIFFS), ck, Disabled, None"
Board generic (platform esp8266, package esp8266) is unknown
Error compiling for board Generic ESP8266 Module.
******** Solved by deleting everything in C:\Users\xxx\AppData\Local\Arduino15 after installing 1.6.9 ********
Last edited by hamster on 31 Jul 2016, 17:52, edited 1 time in total.
Re: ESP Easy Releases
hamster,
This hapened to me the last time there was an upgrade to the core. I think it had to do with there being 2 different locations the Arduino IDE stored the ESP core. Once I deleted the old one phyiscally, there were no more problems.
I notice Martinus installed the portable version of Arduino 1.6.9. Perhaps this reduces the number of locations where things are stored in Windows. I will try the portable version today, on a new computer and also on a usb stick. Maybe I can get away with running it on my work computer and not have to lug my laptop in every time I want to do something.
This hapened to me the last time there was an upgrade to the core. I think it had to do with there being 2 different locations the Arduino IDE stored the ESP core. Once I deleted the old one phyiscally, there were no more problems.
I notice Martinus installed the portable version of Arduino 1.6.9. Perhaps this reduces the number of locations where things are stored in Windows. I will try the portable version today, on a new computer and also on a usb stick. Maybe I can get away with running it on my work computer and not have to lug my laptop in every time I want to do something.
Re: ESP Easy Releases
Hi,
I am very new to this, and I am hooked already. ( i have three esp-07 running and 4 more to install)
I use R108 and I do have issues.
You state that R114 is available for evaluation, I would really like to try that.
I dont know how to compile and I cann't find a manual online.
please advise, how to do that or where to download a compiled version
thanks in advance
I am very new to this, and I am hooked already. ( i have three esp-07 running and 4 more to install)
I use R108 and I do have issues.
You state that R114 is available for evaluation, I would really like to try that.
I dont know how to compile and I cann't find a manual online.
please advise, how to do that or where to download a compiled version
thanks in advance
Martinus wrote:Because the current R108, marked stable, still contains some bugs, it would be better to replace it with a newer version. R114 is available for evaluation. We moved to a newer MQTT client, it may improve connection issues. We also moved to Arduino core 2.3.0 because the 2.1.0 has issues with the servo library.
With this build, only core 2.3.0 is supported, so you need to upgrade the core package. I had some issues with the core upgrade, so i decided to download and configure a brand new portable setup using Arduino 1.6.9 with a fresh core 2.3.0 install.
R114 has been running for a week now in my environment. I successfully upgraded all my unit's using OTA. (NodeMCU 1.0 and ESP-01 black editions)
Changes since R108:
// Cleanup code, conditional core 2.0.0/2.1.0 support removed, changed to core 2.3.0
// Bugfix in rules processing with multiple value devices, only the first value would work as expected
// Bugfix for timezones other than whole hours offset. It is now set in +/- minutes
// Bugfix parsing rfid (SENSOR_TYPE_LONG) values in parseTemplate function
// Improved Serial Server plugin, reconnect handling
// Improved thingspeak and emoncms plugins (contributed by pm-cz)
// Fix HTU21d timing
// Moved to pubsubclient 2.6 library (source no longer compatible with 1.9 library, so use the 2.6 version!)
Who is online
Users browsing this forum: Google [Bot] and 0 guests