ESP Easy Mega

[psy0rz]

Would it work if one installs the dev7-zipfile and copy the newer libs and sources over the existing dev7-directories?

yep i think so.

[starfish]

Altough the point of ESPEasy is to be able to grab one binary firmware file, flash it, and then select the plugin from the build in webgui.

i dont know if you a going this route, .......

the actual way is just perfect, I never had memory problems - flashing a binary file will be ok for most users. If smaller footprint is needed you still can go on compiling and uploading.

[tozett]

- flashing a binary file will be ok for most users. ...

this was also mentioned by martinus a (longer) time agao, to go the way of a binary.
but i never saw any statistical proof (download link-counter) for either way?

anyway. the choice seems up to the devs...

i personally would be glad, if this little additional effort is still made
to keep the arduino-ide/compiler way also working ...

+1 (for the firmware at all)

[starfish]

i personally would be glad, if this little additional effort is still made
to keep the arduino-ide/compiler way also working ...

me too - but is this way endangered?

[costo]

Today I have been playing with the Mega software for the first time.
I followed the wiki for installing ESPEasy-2.0.0-dev7 with the Arduino IDE 1.6.12.
I had to copy a few libraries to make it compile.
Everything worked fine until I added a NEOpixel and IR device without the actual hardware and then the Wemos got in a reboot loop.
Usually no problem, just connecting RX-TX and reset, but this time that did not work, the IDE gave this message:

PID:0
Version:0
INIT : Incorrect PID or version!
Resetting factory defaults...
RESET: Reboot count: 97
RESET: To many reset attempts
Exception (0):

I could not get the Wemos out of the reboot loop. Flashed the normal R148 and cleared it with RX-TX shorted, but when flashing the mega version again the rebootloop was still there. Connecting RX-TX did not help.

At last I edited the void ResetFactory(void) in the Misc file, changed ´if (RTC.factoryResetCounter > 3)´ from 3 to 97

That finally did the job, while RX-TX shorted I saw this in the monitor:

INIT : Booting version: (custom)
FS : Mount successful
Resetting factory defaults...
RESET: Reboot count: 65
FS : formatting...
FS : formatting done...
FILE : File saved
FILE : File saved
Factory reset succesful, rebooting...

[tozett]

i find it extremly helpful for bugfixing to see such user-reports,
and solutions.

but now it seems again, that we have two places to keep up to for this.
this wiki and the issues in bug-tracker on github ...
in the past i checked a lot around this wiki to find helpful reports and hints
on a lot of different threads... hard work ...

[Shardan]

From my point of view the wiki should provide the documentation.
Things like "Supported sensors/actors", Setups and examples, some HowTo's and so an.

Then i'd like to see a separate "Problem solved" area in the forum, kinda FAQ or similiar.
I read the forum often and try to answer questions if i can but many questions come up
repeatedly. "Why does sonoff dual not work?" or "Flashing new ESP-01 V3 fails" are
comming in my mind from the last days. More Points: Power supply, why this capacitor there,
maybe checklists what to do if something Fails and so on.
Would be nice to get solutions and hints bundled in one place, from my opinion this should not be in the Wiki.

Bugreports should be bundled, forum or github. I'd prefer the forum as far more users are accustomed to a forum
then to github but anyways ... one of them, not both in parallel.

But:

All of these will work only if they are kept up to date.
If i take a look into the Wiki.... several plugin descriptions are not even on the R147/148 level,
fields missing / not descripted and so on. For a Newcomer to ESPEasy it's difficult.

As tozett said: many reports and such are very helpfull. If you find them at all!

[costo]

I wanted to report my findings of this reboot-loop bug. I had the choice of opening a new topic in forum ¨experimental¨ , somewhere else or add it in this existing topic.
Maybe there should be a separate subforum for bugs, problems and solutions.

But .... then there should also be a moderator who will move such topics to the right sub-forum. There will always be innocent users who open a topic in the wrong (sub)forum.
Without doubt, having a active moderator would result in a more logical forum and also make it easier for users to find solutions for known problems.

---------------------------
About the reboot-loop problem I experienced:

Up to now I have not been able to reproduce this behaviour from which I was unable to escape in a simple way.
I must say that one important check I did not make. I should have shorted RX-TX and then remove power, reconnect power and see what happens. I did not check this so called cold reboot, I only checked warm reboots. If I´m ever able to reproduce the bug I will also check a cold reboot.

I assume the RTC.factoryResetCounter is there to prevent writing to the filesystem too often, which is counted in: Flash Writes (daily/boot) and is limited to 100.
Possibly while I was playing with all kinds of plugins I had reached the limit of 100 daily flash writes.
I noticed that a cold reboot resets the flash-writes counter to zero. So probably that was the proper way to escape from the endless reboot loop.

I suggest to prohibit endless reboot loops, the ¨resetting to factory defaults¨ must be unconditional, skipping the RTC.factoryResetCounter check which caused the endless loop.

I believe, being able to always do a ¨Resetting to Factory Defaults¨ when needed is more important than the risk of exceeding the MAX_FLASHWRITES_PER_DAY or exceeding the RTC.factoryResetCounter.

[psy0rz]

- flashing a binary file will be ok for most users. ...

this was also mentioned by martinus a (longer) time agao, to go the way of a binary.
but i never saw any statistical proof (download link-counter) for either way?

anyway. the choice seems up to the devs...

i personally would be glad, if this little additional effort is still made
to keep the arduino-ide/compiler way also working ...

+1 (for the firmware at all)

offcouse we make sure that compiling also keeps working:)

[psy0rz]

I wanted to report my findings of this reboot-loop bug. I had the choice of opening a new topic in forum ¨experimental¨ , somewhere else or add it in this existing topic.
Maybe there should be a separate subforum for bugs, problems and solutions.

But .... then there should also be a moderator who will move such topics to the right sub-forum. There will always be innocent users who open a topic in the wrong (sub)forum.
Without doubt, having a active moderator would result in a more logical forum and also make it easier for users to find solutions for known problems.

---------------------------
About the reboot-loop problem I experienced:

Up to now I have not been able to reproduce this behaviour from which I was unable to escape in a simple way.
I must say that one important check I did not make. I should have shorted RX-TX and then remove power, reconnect power and see what happens. I did not check this so called cold reboot, I only checked warm reboots. If I´m ever able to reproduce the bug I will also check a cold reboot.

I assume the RTC.factoryResetCounter is there to prevent writing to the filesystem too often, which is counted in: Flash Writes (daily/boot) and is limited to 100.
Possibly while I was playing with all kinds of plugins I had reached the limit of 100 daily flash writes.
I noticed that a cold reboot resets the flash-writes counter to zero. So probably that was the proper way to escape from the endless reboot loop.

I suggest to prohibit endless reboot loops, the ¨resetting to factory defaults¨ must be unconditional, skipping the RTC.factoryResetCounter check which caused the endless loop.

I believe, being able to always do a ¨Resetting to Factory Defaults¨ when needed is more important than the risk of exceeding the MAX_FLASHWRITES_PER_DAY or exceeding the RTC.factoryResetCounter.

i think you can escape that loop by actually powering off and on again while connecting rx and tx. that will reset the reboot counter.

wiki page that describes ways of resetting factory defaults should be updated perhaps.

[psy0rz]

i find it extremly helpful for bugfixing to see such user-reports,
and solutions.

but now it seems again, that we have two places to keep up to for this.
this wiki and the issues in bug-tracker on github ...
in the past i checked a lot around this wiki to find helpful reports and hints
on a lot of different threads... hard work ...

Only if youre 100% sure something is a bug it should go on the issue tracker. Sometimes things are not a bug but a lack of documentation for example. Usually its best to start discussions about possible bugs on the forum i think. Once people can reproduce or confirm it, it should go to the issue tracker, and perhaps post the link to the issue tracker on the forum.

The goal is to keep the issue tracker as short as possible so devs can focus on fixing bugs.

Hope this clears things up a bit?

[costo]

i think you can escape that loop by actually powering off and on again while connecting rx and tx. that will reset the reboot counter.

wiki page that describes ways of resetting factory defaults should be updated perhaps.

Thank you for the confirmation.

[Humanoidx]

Does anyone know what the Rule Syntax is for the Email Notification? And what SMTP servers it works with? Been trying to get it to work with google restricted smtp server.

[krikk]

have not tried, but i am sure it will only work with servers, who do not enforce encryption, and google enforces encryption... so you need an smtp server which allows simple clear text smtp

[mvn77]

Whether it is possible by means of rules to save indications of gauges in files on SD card in individual files?

[tozett]

The goal is to keep the issue tracker as short as possible so devs can focus on fixing bugs.

Hope this clears things up a bit?

Yeah, Points are Made in this thread, how to improve.
But must still be Set Up...

But another new example dir the old Problem s, that this thread and bis single topic has now lots of helpful Informationen für lot of Differenz things.
Thread is getting Longer... No one will quickly find this help ...
Aber Moderator could help. Or the other improve ments could help...
A Forum is not so easy to Focus on quick failure/Solutions Like newbies needs..

I see how his Developes here

[alex77k12]

often using buttons to activate relay I wanted to try it on this version, to make use rules, but with some combinations going to panic. To be possible in future versions to add this function directly in the web setting is printed in order to avoid rules?
Right now it's giving into panic in order to excite relay rules in case a value above. Always in the rules excite the same relay by button pressure. Using these values go into panic (using 3 different Wemos d1)

visible problem below, I have highlighted the problem and when next active rules

Code: Select all

FILE : File saved
SW : State 1
EVENT: vent#Vent=1.00 <---no rules ok
WD : Uptime 4 ConnectFailures 0 FreeMem 20240
SW : State 0
EVENT: vent#Vent=0.00 <---no rules ok
WD : Uptime 4 ConnectFailures 0 FreeMem 20056
WD : Uptime 5 ConnectFailures 0 FreeMem 20424
WD : Uptime 5 ConnectFailures 0 FreeMem 20424
SW : State 1
EVENT: vent#Vent=1.00 <---rules venton
ACT : event ventolaon <---rules venton
EVENT: ventolaon <---rules venton
ACT : gpio 2,1 <---rules venton
SW : GPIO 2 Set to 1 <---rules venton

Panic /home/travis/.platformio/packages/framework- <---rules venton crash
arduinoespressif8266/cores/esp8266/core_esp8266_main.cpp:131 loop_task

ctx: sys
sp: 3ffffdd0 end: 3fffffb0 offset: 01b0

stack>>>
3fffff80: 40248992 3fffdab0 00000000 3fff2b00
3fffff90: 00000000 3fffdad0 3fff2af0 402032ed
3fffffa0: 40000f49 40000f49 3fffdab0 40000f49
<<<stack<<<
ets Jan 8 2013,rst cause:2, boot mode:(3,3)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d

Rules is

Code: Select all

on venton do
gpio 2,1
inputventstate 0,1
endon

on ventoff do
gpio 2,0
inputventstate 0,0
endon

on vent#Vent do
if [vent#Vent]=1
event venton
else
event ventoff
endif
endon

[toffel969]

often using buttons to activate relay I wanted to try it on this version, to make use rules, but with some combinations going to panic. To be possible in future versions to add this function directly in the web setting is printed in order to avoid rules?
Right now it's giving into panic in order to excite relay rules in case a value above. Always in the rules excite the same relay by button pressure. Using these values go into panic (using 3 different Wemos d1)

visible problem below, I have highlighted the problem and when next active rules

Code: Select all

FILE : File saved
SW : State 1
EVENT: vent#Vent=1.00 <---no rules ok
WD : Uptime 4 ConnectFailures 0 FreeMem 20240
SW : State 0
EVENT: vent#Vent=0.00 <---no rules ok
WD : Uptime 4 ConnectFailures 0 FreeMem 20056
WD : Uptime 5 ConnectFailures 0 FreeMem 20424
WD : Uptime 5 ConnectFailures 0 FreeMem 20424
SW : State 1
EVENT: vent#Vent=1.00 <---rules venton
ACT : event ventolaon <---rules venton
EVENT: ventolaon <---rules venton
ACT : gpio 2,1 <---rules venton
SW : GPIO 2 Set to 1 <---rules venton

Panic /home/travis/.platformio/packages/framework- <---rules venton crash
arduinoespressif8266/cores/esp8266/core_esp8266_main.cpp:131 loop_task

ctx: sys
sp: 3ffffdd0 end: 3fffffb0 offset: 01b0

stack>>>
3fffff80: 40248992 3fffdab0 00000000 3fff2b00
3fffff90: 00000000 3fffdad0 3fff2af0 402032ed
3fffffa0: 40000f49 40000f49 3fffdab0 40000f49
<<<stack<<<
ets Jan 8 2013,rst cause:2, boot mode:(3,3)

load 0x4010f000, len 1384, room 16
tail 8
chksum 0x2d
csum 0x2d
v09826c6d

Rules is

Code: Select all

on venton do
gpio 2,1
inputventstate 0,1
endon

on ventoff do
gpio 2,0
inputventstate 0,0
endon

on vent#Vent do
if [vent#Vent]=1
event venton
else
event ventoff
endif
endon

If I may ask, what is the inputvenstate supposed to do ? I cannot see what this is trying to achieve, nor can I find it in the command reference. So to me it looks like a syntax error. If you clarilfy what you are trying to do with

Code: Select all

inputventstate 0,0

then I should be able to help you

[psy0rz]

Maybe people should start new posts more often, instead of starting new subjects in the same thread?

[toffel969]

Maybe people should start new posts more often, instead of starting new subjects in the same thread?

true story

[tozett]

+1

[the cosmic gate]

I have updated 2 Wemos D1 UNITS, FROM GIT version: v2.0.0-dev4 to dev7.
now the NTP time is not working any more.
is this a know problem.
It give this Local Time:1970-01-01 0:17

getting his same issue, how did you solve this ?

[lucaberta]

I have updated 2 Wemos D1 UNITS, FROM GIT version: v2.0.0-dev4 to dev7.
now the NTP time is not working any more.
is this a know problem.
It give this Local Time:1970-01-01 0:17

getting his same issue, how did you solve this ?

hi, I just tamed the dreaded Atom/PlatformIO beast, and I quite like!

I have thus been able to restart working on the new Mega v2.0 builds, and have compiled and flashed a Wemos Mini D1 with the latest code I pulled from GitHub.

I too have run into the same issue with NTP, but then I changed the NTP server from a hostname (I was trying with "pool.ntp.org") to a fixed IP address and it worked right away, after a restart of the Wemos. I used IP address 197.84.150.123

Bye, Luca

[tozett]

(only a sidenote for the before discussion in this thread about useful places for help)

for the ntp-thing, on github one could mark this issue as solved,
it could has ben categorized by the devs...., put in the wiki-help... ...

i would find such as a shortcut on the search for help with espeasy,
but that would be overall more work to manage this, at least for someone ...

[psy0rz]

can you make a issue for it on github, if there isnt one already?

[tozett]

can you make a issue for it on github, if there isnt one already?

i dont think its necessary on this single case,
(for differnt reasons)

i was tampered to comment on the beforegoing general discussion about
the new development-ways of espeasy and the (wish by the devs?) to ease the implementing
for newbies. but i only can speak out this as a personal view, i dont know
if a wider range of firmware-users or forum-users see this in a similar way or if my view is a help for them ...

(or wasnt the entry not ment for me?)

[grovkillen]

When i want to set up the devices and would like to set up no.5
i get an "Error saving to flash!"

I get the "Error saving to flash!" warning if I have put the GPIO 16 boot state to low. The only way to get rid of this is to re-flash the unit (as far as I know,).

GPIO 16, the ESPeasy GUI should warm about this!

[tony-in-oz]

Hi
I am testing Mega2 on various ESp8266 ESP-12 4M boards and have come across a few issues.

First off, its great being able to publish data to multiple systems at once!

Issues I have found so far - others may have reported these??-
- unable to have Domoticz (as IP) as controller 2
- unable to have Thingspeak (as IP) as controller 2 - seems to be a pattern with cont 2
- Domoticz as controller 1 - works ok
- Thingspeak as controller 3 - works ok
- Formating issues with IDX variable for Task 4 and greater - all IDX numbers put on one line


My setup
Controller 1 - Domoticz hTTP
2 - Thingspeak
Devices 1,2 - DS18b20 on GPIO-2
Device 5 - DS18b20 on GPIO-4
Device 3 - System - wifi dBm
Device 4 - System - uptime

On another unit I am testing a water flow sensor on a GPIO port as a counter. This unit has an uptime exceeding 30,000 minutes

Not the greatest range of devices...but I'm working on it

Tony

[psy0rz]

When i want to set up the devices and would like to set up no.5
i get an "Error saving to flash!"

I get the "Error saving to flash!" warning if I have put the GPIO 16 boot state to low. The only way to get rid of this is to re-flash the unit (as far as I know,).

GPIO 16, the ESPeasy GUI should warm about this!

its not clear what you mean with the GPIO 16 problem.

[psy0rz]

Hi
I am testing Mega2 on various ESp8266 ESP-12 4M boards and have come across a few issues.

First off, its great being able to publish data to multiple systems at once!

Issues I have found so far - others may have reported these??-
- unable to have Domoticz (as IP) as controller 2
- unable to have Thingspeak (as IP) as controller 2 - seems to be a pattern with cont 2
- Domoticz as controller 1 - works ok
- Thingspeak as controller 3 - works ok
- Formating issues with IDX variable for Task 4 and greater - all IDX numbers put on one line


My setup
Controller 1 - Domoticz hTTP
2 - Thingspeak
Devices 1,2 - DS18b20 on GPIO-2
Device 5 - DS18b20 on GPIO-4
Device 3 - System - wifi dBm
Device 4 - System - uptime

On another unit I am testing a water flow sensor on a GPIO port as a counter. This unit has an uptime exceeding 30,000 minutes

Not the greatest range of devices...but I'm working on it

Tony

Only the first controller can be a MQTT type. This is explained on the wiki page: https://www.letscontrolit.com/wiki/inde ... yProtocols

Can you describe the formatting issues? The previous poster also indicates problems with task 4 and higher..

[grovkillen]

its not clear what you mean with the GPIO 16 problem.

I put GPIO 16 boot state "low" and after that I could not save to flash. I guess it's possible that happened at the same time the limit of 100 writes/24 hours occurred?

Anyways, the "Error saving to flash!" message isn't stating why the error occurred... that could be made much verbose in that sense.

[psy0rz]

ahh right..i checked it and created https://github.com/letscontrolit/ESPEasy/issues/235

[grovkillen]

Hi, this is my wish list for the future. When I get more time I might work on a fork if these are not accepted as good features for the main branch. Anyhow, I'm all for MQTT thus this will largely focus on that protocol.

• Have the possibility to broadcast IP etc. at boot without the use of rules.

• Have a Generic MQTT server in the dropdown. This one should not have the forward slash in the beginning of the topic!

• Be able to to turn on periodically publishing of status (RSSI, IP, Uptime etc.)

• Add variables for all the information found in the main tab (Local time, Unit Number etc.)

• Besides the %systime% also have %sysdate%.

• Have the unit publish status topics for some commands like reboot (publish: Publish %sysname%/status,Rebooting etc.)

• Alter settings via MQTT commands, might be optional since it opens up a risk of attacks (only the broker security is in between, but I want it )

• Related to the one above, be able to send OTA updates over MQTT (i.e. send the path or the file).

This is general stuff:

• When saving a config file please do not make it proprietary, I want to be able to change it or create it using a notepad type of software. When I make new units I want to copy some parts of the settings + changing unit name, unit number etc. etc. If this would be possible it would be nice to be able to add the wifi settings (ssid+password) and skip the login-to-ap-and-type-this-in. Please also include rules in the config file. And preferably have it saved in JSON format. This would make it ideal to send over MQTT!

• Related to the one above. Have an option to upload a config file when connected to the AP mode 192.168.4.1.

• When I use Fing to scan my LAN I find alot of "generic" names, this would be of great help if the unit broadcasted it's real name instead.

• Rearrange the "device tab" to have all the devices in a long list instead of only 4 per page. The flipping forward and backwards between the device pages is sometimes a pain when searching for a free GPIO or what GPIO is doing what etc.

• Possibly have the hardware tab populated with what devices that are using each GPIO?

• Have a description field where I can write in free text what the unit is for, it's placement or whatever I might think of to help me distinguish all my nodes from one and another. Have this as a variable to publish as well with the rest of the unit status variables.

• If I have, let's say, a switch. It is possible to have that switch tell either a "1" or a "0". It is also possible to invert this, 1=0 and 0=1. This is great but I would like to have the possibility to tell that 1=Open and 0=Closed or 1=False and 0=True or what ever free text I might think of. It is a lot easier to have this in verbose language when creating rules etc.

• "Wifi Status Led", have the possibility to invert the blinking of receiving/sending.

• Have the possibility to turn of protocols that I don't use (i.e. HTTP REST commands, for security reasons )

Ok, a long list and I don't want to come out as an grumpy old fart. It's is only ideas and I will try to implement them myself whenever I get more time. But feel free to discuss my list here

[tozett]

good list,
looks like my start with a list in 01/2016 at ver 072...

https://www.letscontrolit.com/forum/vie ... =731#p3475

lots of things done, somethings still preferable.
looks like work for the devs... go for it...
+1

[AndrewJ]

+1

[stefbo]

Hi,
I finally managed to set up the new environment and successfully compiled and uploaded the "normal" version to my esp12s. Very impressing! I like it. Good work!!!
However I still have som old esp-01 and 201 around running with V140, which I want to upgrade as well. Therefore I looked at the "mini_512" compile option. I uncommented it and adapted the build_flags to agree with the normal version (without the PLUGUN_BUILD_NORMAL flag).
I assume that all plugins, that do not have any #ifdef PLUGIN_BUILD_... command in the first lines are compiled and put into the executable.
However the size is too large, Seems I have to exclude more plugins.
My first plugins are the OLED (P023 and P036). I inserted the #ifdef PLUGIN_BUILD_NORMAL commands there and recompiled. Still too large.
Looking at the output from the compiler, I see that the SSD1306 library is still compiled. Why? Is it also included in the binary?
I also found actions on Adafruit_TCS34725 lib, even if the corresponding plugin (P050) is marked "experimental".
Can anybody comment on this behaviour?
Best regards

Stefan

[krikk]

the plugin selection with the ifdef is only implemented on the newer plugins, not for the older plugins, best way to get a "small" build up to now is to just delete the unwanted plugins and compile...

[Shardan]

Good Morning all,

well, my wish list for now is much shorter:

Please get the webserver back to work.

I've tested Mega with a FHEM connection these days.
Fhem connected as second controller leaving the inactive Domoticz config untouched does nothing.
Configuring FHEM as primary controller works but the webpage is lost after some seconds.
First i get a "device did not send data" error from the browser. FHEM shows the device as absent, no data transferred
After some minutes the browser just shows a blank page. If rebooted the page is up for short, then it is gone again.

Besides that the serial monitoring shows the firmware crashing regularly every 3... 4 minutes if i reboot and leave the webpage untouched.

Clearing the flash completely with a zero binary and reflashing didn't help.

Tested config:
Hardware: WeMos D1 Mini and NodeMCU V3, BMP-180
Configured Tasks: BMP-180 and System info with RSSI

Firmware: 2.0.0dev7 from github and a 2.0.0dev7 "testing" self compiled with Arduino and PlatformIO

At Dev's: If i can test more things for you please let me know.


Regards
Shardan

[psy0rz]

Yeah, you shouldnt use the link called "Source code". Github adds that automaticly and it misses the submodules.

Use the first link instead, called ESPEasy_v2.0.0-dev7.zip.

I'll see what i can do to remove or otherwise correct that source code file.

I'll ask the nodemcu-build guy if he wants to share his code or add ESPEasy to his site. (Its from Uncle Bob, he's an awesome dude)

I didn't use the "Source Code" link but downloaded using the "clone / download" to get the actual version... seems to create the same thing.
Maybe just add the actual libraries to the repository so that "download .zip" gives a complete actual version?

Anyways, i can't offer help with coding. My programming knowledge is completely outdated.
But if needed i could help with Wiki and HowTo's to keep the documentation up with development.

Regards
Shardan

We now no longer use submodules, so these issues should be fixed.

You have to do this one time to get rid of the submodules:

* delete the lib-directory
* then do:
git pull
git checkout lib

[psy0rz]

p.s. I assumed that people that want to help fix wiki/documentation issues already have wiki-access? If not, let me know.

You can probably request an account via https://www.letscontrolit.com/wiki/inde ... estAccount and get access automaticly?

If you see something that needs fixing on the wiki, please do so.

Edwin

[maluko]

hi

its any problem with timerset 8,10?

i can put work the 1,2,3,4,5,6,7 but the 8 dont work.

and the timerset with 0 sec dont work either,

[psy0rz]

I've added checks to prevent crashes when someone uses invalid timer values. However that check was off-by-one.

Latest commit fixes it. Valid timers are 1 through 8 (inclusive).

Also setting a timer to 0 sec disables it. This is usefull to create events that start and stop repeating timers: I use this for things like alarms and blinking indicators.

(Altough instead of using espeasy, i'm only coding on it

I just updated the wiki page with more info about repeating timers:

https://www.letscontrolit.com/wiki/inde ... ith_events

[maluko]

I've added checks to prevent crashes when someone uses invalid timer values. However that check was off-by-one.

Latest commit fixes it. Valid timers are 1 through 8 (inclusive).

Also setting a timer to 0 sec disables it. This is usefull to create events that start and stop repeating timers: I use this for things like alarms and blinking indicators.

(Altough instead of using espeasy, i'm only coding on it

I just updated the wiki page with more info about repeating timers:

https://www.letscontrolit.com/wiki/inde ... ith_events

apreciate a lot

thanks psy.

ps: how can i get the bin with this fix?

[jjansen]

p.s. I assumed that people that want to help fix wiki/documentation issues already have wiki-access? If not, let me know.

You can probably request an account via https://www.letscontrolit.com/wiki/inde ... estAccount and get access automaticly?

If you see something that needs fixing on the wiki, please do so.

Edwin

I have requested an account, but no response yet

[psy0rz]

I will ask remco to fix that

[psy0rz]

I've added checks to prevent crashes when someone uses invalid timer values. However that check was off-by-one.

Latest commit fixes it. Valid timers are 1 through 8 (inclusive).

Also setting a timer to 0 sec disables it. This is usefull to create events that start and stop repeating timers: I use this for things like alarms and blinking indicators.

(Altough instead of using espeasy, i'm only coding on it

I just updated the wiki page with more info about repeating timers:

https://www.letscontrolit.com/wiki/inde ... ith_events

apreciate a lot

thanks psy.

ps: how can i get the bin with this fix?

sorry missed this question: you have to wait until the next release, or compile it yourself. (instructions are on the wiki)

[Shardan]

Hello all,

psy0rz has commited a bugfix that solves a problem loosing controller and website connection.
Be aware it is not in the binaries zip file yet.

I've tested it the last days and it works for me with FHEM server.

It would be nice if some users could test it with other servers too
and report back here.

Regards
Shardan

[axello]

p.s. I assumed that people that want to help fix wiki/documentation issues already have wiki-access? If not, let me know.

You can probably request an account via https://www.letscontrolit.com/wiki/inde ... estAccount and get access automatically?

If you see something that needs fixing on the wiki, please do so.

Edwin

Google found the Arduino setup on the wiki https://www.letscontrolit.com/wiki/inde ... are_Upload , but it is not on the front page under "
Source code development" https://www.letscontrolit.com/wiki/index.php/ESPEasy
Is this because you are moving away from Arduino?
I spent 15 minutes so far installing Atom and PlatformIO, but the beta of the latter keeps failing to install, hence I want to continue to use an environment that is more stable: Arduino IDE. Or use something from the command line. Has anyone done that already?

I am willing to work on the wiki, if you please.

Axel

[krikk]

arduino IDE AND platformio should work... ...but the latter is prefered by our main developer psy0rz... and believe me, it has it's advantages, especially if you code more than a few lines, arduino IDE really lacks tons of features of a modern IDE!

[psy0rz]

indeed Arduino IDE should still work, and i've did make a few changes to the Arduino IDE instruction, because we've changed the directory layout.

maybe someone should update the wiki so that page is easier to find.