ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Moderators: grovkillen, Stuntteam, TD-er
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
I have not seen any issue with my relay on GPIO12, it has always turned on when it has meant to & always shown the correct state in the device page.
It is only my switch on GPIO14 that has been a problem..
The OnClock rules seem to work really well.
I have not been able to open an issue 'to cover everything I see going wrong' on GitHub because I am still not sure how to make it easily replicable for developers..
I guess I could break the issues into 'blocks', see if those issues can be improved upon and the impact it has on other issues rather than try and show everything I see all at once = information overload..
I am growing weary of trying to have a workable module
I am open to any suggestion & can supply any data that anyone might consider helpful to a resolution.
It is only my switch on GPIO14 that has been a problem..
The OnClock rules seem to work really well.
I have not been able to open an issue 'to cover everything I see going wrong' on GitHub because I am still not sure how to make it easily replicable for developers..
I guess I could break the issues into 'blocks', see if those issues can be improved upon and the impact it has on other issues rather than try and show everything I see all at once = information overload..
I am growing weary of trying to have a workable module
I am open to any suggestion & can supply any data that anyone might consider helpful to a resolution.
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Somewhere recently I Cold Booted - I looked down and the reservoir level was low, great another overflow.....
And so... I was just out there, an onClock event started - obviously ignoring my rule to not pump if GPIO14 was '1'
well actually, I had to pull the power cord to stop more water loss, was it a lag in response to change in GPIO14's state ????? or whatever..
Now I have pulled the power I can not easily even tell...
Enough grief, it's costing me too much time and making ME look like a complete idiot in front of my wife..
Time for other alternatives
And so... I was just out there, an onClock event started - obviously ignoring my rule to not pump if GPIO14 was '1'
well actually, I had to pull the power cord to stop more water loss, was it a lag in response to change in GPIO14's state ????? or whatever..
Now I have pulled the power I can not easily even tell...
Enough grief, it's costing me too much time and making ME look like a complete idiot in front of my wife..
Time for other alternatives
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
I've been working all afternoon (well until now, almost 2 am) on these WiFi issues.
See PR: https://github.com/letscontrolit/ESPEasy/pull/1165
The thing is, the reconnect of WiFi may take a lot of resources from the ESP unit, which has all kinds of side-effects.
For this approach the WiFi will be managed completely event based and no longer polling.
Still, the possible issue @Grovkillen mentioned with the recorded state of pins is not being dealt with yet.
And there is also another PR ready to improve the handling speed of commands (you also execute commands from rules)
So we're working on getting the thing as stable as soon as possible, although it is still a few months waiting for us literally on the other side of the planet, before we can expect some strawberries in our garden.
See PR: https://github.com/letscontrolit/ESPEasy/pull/1165
The thing is, the reconnect of WiFi may take a lot of resources from the ESP unit, which has all kinds of side-effects.
For this approach the WiFi will be managed completely event based and no longer polling.
Still, the possible issue @Grovkillen mentioned with the recorded state of pins is not being dealt with yet.
And there is also another PR ready to improve the handling speed of commands (you also execute commands from rules)
So we're working on getting the thing as stable as soon as possible, although it is still a few months waiting for us literally on the other side of the planet, before we can expect some strawberries in our garden.
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Again, please do not misunderstand me, I know you are not paid...
If you want to point me in the direction of something, anything to replace the existing firmware then supply feedback, by all means do so..
Something to test for you ? Ok too...
email me if that helps - oxyandy at google's service
Happy to help where I can, but as my most recent posts reflect, just when I thought I was getting somewhere BAM something happens which devastates me..
It is completely true that I have my wife looking over my shoulder & completely true that she 100% lays blame on me for stupidity, she is not good with technical things & can only see I am getting nowhere...
I sometimes feel excited that I am getting somewhere & share that with her, only to fall flat on my face..
I installed an access point (outdoor hacked up old ADSL router) and log WiFi strength it has been great...
Remember I said that firing a rule - the logs get too busy ?
I still stand by that, what the logs show now looks like a resource pig..
I think they should be
But instead is normally
All sent via WiFi cause I added 'publish' in middle of rules, but it was the same when I was using SYSLOG, the new style just easier to examine at a glance..
But yeah I know, you have other tasks to do...
Not trying to push you TD-er ... That would just be rude..
Is simply like a diary of my 'real experience' & frustrations over my experience & observations.
If you want to point me in the direction of something, anything to replace the existing firmware then supply feedback, by all means do so..
Something to test for you ? Ok too...
email me if that helps - oxyandy at google's service
Happy to help where I can, but as my most recent posts reflect, just when I thought I was getting somewhere BAM something happens which devastates me..
It is completely true that I have my wife looking over my shoulder & completely true that she 100% lays blame on me for stupidity, she is not good with technical things & can only see I am getting nowhere...
I sometimes feel excited that I am getting somewhere & share that with her, only to fall flat on my face..
I installed an access point (outdoor hacked up old ADSL router) and log WiFi strength it has been great...
Remember I said that firing a rule - the logs get too busy ?
I still stand by that, what the logs show now looks like a resource pig..
I think they should be
Code: Select all
12:00:00 OnClock timer start
12:00:00 Pump On
12:02:54 Float Switch '1'
12:02:54 Pump Off
12:02:56 Float Switch '0'
12:05:00 OnClock timer stop
Code: Select all
2x OnClock timer start
8x Pump On
8x (msgs) about Float Switch
8x Pump Off
2x OnClock timer stop
But yeah I know, you have other tasks to do...
Not trying to push you TD-er ... That would just be rude..
Is simply like a diary of my 'real experience' & frustrations over my experience & observations.
- Methuselah
- Normal user
- Posts: 45
- Joined: 04 Feb 2018, 01:39
- Location: Boston, MA
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
It’s been apparent to me (and many other readers) for a long time that ESPEasy is not the product for you. It simply isn’t going to have the level of stability, and support, you need for your application.
N00b to the world of ESPEasy, but I've been programming since the days of punch cards and paper tape
- grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
- Contact:
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
We're trying our best to make sure that the FW is top notch but major rewrite of code is done and with that bugs will be showing up. Maybe you'll have to wait and come back here at a later stage.Methuselah wrote: ↑24 Mar 2018, 09:59It’s been apparent to me (and many other readers) for a long time that ESPEasy is not the product for you. It simply isn’t going to have the level of stability, and support, you need for your application.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Quite the opposite, this is not a dead project.. No other firmware comes close to meeting my needs !Methuselah wrote: ↑24 Mar 2018, 09:59It’s been apparent to me (and many other readers) for a long time that ESPEasy is not the product for you. It simply isn’t going to have the level of stability, and support, you need for your application.
I am keeping an eye on the development and it is making awesome progress !
My goal was to be able to spell out my experiences and make careful enough observations - to pin down the points of failure in an easy repeatable way,
making developers lives as easy as possible to then initiate positive change, but that is were I have been getting stuck.
TD-er has taken note, provided feedback and offered a solution, for this I am grateful, it's just testing in a 'real life' situation was harmful to my plants, so as I said.. yesterday I made an alternative way to keep my plants happy, so that will save me a lot of time looking after them, so I can focus better on modules
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
grovkillen yes, I have been reading, it is clear the development is constant..
You are forever posting on the Git Hub side and replying here on this forum..
You are a huge asset to the team, I have been looking over TD-er's recent WiFi changes
Updated the code direct from TD-er, compiled while everyone on your side of the globe was sleeping..
First thing I noticed was I can click through pages on the web-config and they are 'just there'
even from one page I tried to open links in new tabs, when I went to those tabs everything was open,
previously I would be seeing blank pages..
For me is quite noticeable, well done TD-er
Weather was awful but I managed to setup a back-up system to take care of my strawberry plants,
I set up another system so I can use it test modules in a real life task, but as it has no plants or nutrient solution, so no grief.. is only water
You are forever posting on the Git Hub side and replying here on this forum..
You are a huge asset to the team, I have been looking over TD-er's recent WiFi changes
Updated the code direct from TD-er, compiled while everyone on your side of the globe was sleeping..
First thing I noticed was I can click through pages on the web-config and they are 'just there'
even from one page I tried to open links in new tabs, when I went to those tabs everything was open,
previously I would be seeing blank pages..
For me is quite noticeable, well done TD-er
Weather was awful but I managed to setup a back-up system to take care of my strawberry plants,
I set up another system so I can use it test modules in a real life task, but as it has no plants or nutrient solution, so no grief.. is only water
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
I think with my recent experience, I'd be an ideal candidate to test & log anything as a result of any changes..
Point me in the direction, thanks
I did not get much time yesterday as weather was terrible, but managed to get a firmware compiled & flashed
Tried notify 1 OnBoot & it fails..
I will in fairness flash the BIN image you uploaded to drop box, I guess - dev_ESP8266_1024
and begin a routine of tests, beginning with boot tests - then put it into a working situation & log data
- grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
- Contact:
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
At system boot you may not have connection to the wifi. Please use WiFi#Connected instead.
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
- Methuselah
- Normal user
- Posts: 45
- Joined: 04 Feb 2018, 01:39
- Location: Boston, MA
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
I for one appreciate the effort. The ESPEasy firmware has made several of my automation tasks much easier, both in my home and in my ham shack. I wish I could contribute more, but my applications are extremely limited so I do not think I could contribute much.grovkillen wrote: ↑24 Mar 2018, 11:09 We're trying our best to make sure that the FW is top notch but major rewrite of code is done and with that bugs will be showing up.
I did not say the project is dead. However, it seems you need commercial, instrumentation-level control for your application. That's not something you're going to get with ESPEasy.... yet.
For a bunch of volunteers, the devs on this project have done an amazing job.
N00b to the world of ESPEasy, but I've been programming since the days of punch cards and paper tape
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
@Oxyandy: I also think you put pretty much pressure on the voluntary developers here. From your shouting and posts, one would think your problems are the only ones here.
You should really consider the suggestion of @Methusalem and not use espeasy for your precious plants, until you extensively tested it by yourself and make sure it does what you need.
Also, there are older (proven) versions of espeasy - why you have to use a bleeding edge version in a production environment?
With a commercial and paid product you also can claim its proper function.
You should really consider the suggestion of @Methusalem and not use espeasy for your precious plants, until you extensively tested it by yourself and make sure it does what you need.
Also, there are older (proven) versions of espeasy - why you have to use a bleeding edge version in a production environment?
With a commercial and paid product you also can claim its proper function.
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
So does this mean you are posting to suggest to me a particular firmware that I should try ?
Something which I could provide Developers feedback on, so changes can be back-tracked ?
Such as 'was working in release XXX', but then stopped in every version there-after ?
Sure, I can try - Happy to hear your suggestion, thanks
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
This version works for me with a reed switch on gpio-13: v2.0.0-dev12
I would suspect a hardware problem - to exclude that, the tests should first happen without switching a heavy inductive load (like a big water pump). Maybe even not with a sonoff, but rather a nodemcu or wemos board with a good power supply. Only after you are able to detect the pulses from the switch reliable, you should add more components (hard and software) step by step (relay, rules, etc) and check for failure - with the pump at last.
You tried also the tasmota firmware, but i didnt understand the result...was it working?
I would suspect a hardware problem - to exclude that, the tests should first happen without switching a heavy inductive load (like a big water pump). Maybe even not with a sonoff, but rather a nodemcu or wemos board with a good power supply. Only after you are able to detect the pulses from the switch reliable, you should add more components (hard and software) step by step (relay, rules, etc) and check for failure - with the pump at last.
You tried also the tasmota firmware, but i didnt understand the result...was it working?
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Tasmota firmware works fine 99.9%, but the timer cycles are not internal & are dependant on a back-end such as Domoticz to fire the cycles & then Domoticz rules to then stop the pump.. And of course a constant WiFi signal...
The 'Tasmota way' simply has more points of failure than something with a complete 'internal process' which only relies on WiFi for data logging & error reporting.
If a point of failure occurs and I am say 'camping' I can use another reservoir / pump / ESP module to replace the primary via the dashboard,
or even automate it in such a way that it becomes the primary system.
Timer cycles & rules Internal to ESPeasy are therefore just what I need.
When I first found ESPeasy (see my join date here) as an alternative to Tasmota, I read there were 2 branches Release & development,
thinking my task was simple & wanting reliability I downloaded a release V2 firmware..
I never knew 'release was Beta' & 'old was Alpha', that defies logic.
I am now using an ancient release (R_xxx series) & compared to the current releases I have been using -- is like a turbo charged ESP on steroids,
everything 'just works' as it should.. wow what a contrast.
I could list the differences.. a long list after learning the quirks of what I have been using.
I (when I get time or find a fault) will start stepping up release versions by reading change logs & merging in parts of the source & compiling homebrew as I go..
My pumps use 30W @240V, no drama there, even my sump pump @5 amps has no issue..
Because you have been a member here much longer than n00b me, I think you could have been a bit nicer to me, helped me maybe ?
By simply telling me to try an older release such as v2.0.0-dev12 sooner ?
Anyhow help is still help & I think you are a legend for steering me in the right direction, old is good, just like me
The 'Tasmota way' simply has more points of failure than something with a complete 'internal process' which only relies on WiFi for data logging & error reporting.
If a point of failure occurs and I am say 'camping' I can use another reservoir / pump / ESP module to replace the primary via the dashboard,
or even automate it in such a way that it becomes the primary system.
Timer cycles & rules Internal to ESPeasy are therefore just what I need.
When I first found ESPeasy (see my join date here) as an alternative to Tasmota, I read there were 2 branches Release & development,
thinking my task was simple & wanting reliability I downloaded a release V2 firmware..
I never knew 'release was Beta' & 'old was Alpha', that defies logic.
I am now using an ancient release (R_xxx series) & compared to the current releases I have been using -- is like a turbo charged ESP on steroids,
everything 'just works' as it should.. wow what a contrast.
I could list the differences.. a long list after learning the quirks of what I have been using.
I (when I get time or find a fault) will start stepping up release versions by reading change logs & merging in parts of the source & compiling homebrew as I go..
My pumps use 30W @240V, no drama there, even my sump pump @5 amps has no issue..
Because you have been a member here much longer than n00b me, I think you could have been a bit nicer to me, helped me maybe ?
By simply telling me to try an older release such as v2.0.0-dev12 sooner ?
Anyhow help is still help & I think you are a legend for steering me in the right direction, old is good, just like me
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
I have been building up a 'tool box' of tools,
first - 'working OTA Sonoff firmware updating', tick done.
second - a full set of all firmwares since inspection and each's source-code, tick done.
third - modify all those firmwares so they are also fully compatible with OTA Sonoff firmware updating, tick done.
fourth - Using the oldest firmware I can, OTA install and then test & log data carefully, compare many variables & carefully examine function /performance etc.
Slowly getting done, is a time consuming task, observations need to be done carefully over time, then reset, start over again to confirm those observations..
A few key issues with the most recent releases do NOT appear in some of these older releases..
I then need to look carefully and determine exactly when and what source changes were made which had negative impact, I can say I have done some narrowing down, such as Dev 4 seems (only seems) cause I must verify everything over & over.. but seems like it works, many things I am comparing
This is very consistent 'expected' behaviour
On Clock#timer, turns on pump, level rises until float goes from closed circuit to open circuit, rules fires before timer ends turning off pump, float returns to stop (NC) & then timer ends.
Uptime is excellent, no data missing in logs & logs not showing 8 of each event, only 2..
About 2, I am not sure if this is intentional or not, there maybe reasons for 2 duplicate log entries for everything ??
IE
See appears twice, I would rather see only once, but again not sure if 2 is intentional, and if so the reasons for 2 ??
If you have followed my previous posts, on newer firmware many have 8 duplicate log entries
Yet to find the exact point 2 became 8, but I am on a mission and I will.
Then I will attempt to merge newer source changes over the older more predictable 'working as expected version'..
first - 'working OTA Sonoff firmware updating', tick done.
second - a full set of all firmwares since inspection and each's source-code, tick done.
third - modify all those firmwares so they are also fully compatible with OTA Sonoff firmware updating, tick done.
fourth - Using the oldest firmware I can, OTA install and then test & log data carefully, compare many variables & carefully examine function /performance etc.
Slowly getting done, is a time consuming task, observations need to be done carefully over time, then reset, start over again to confirm those observations..
A few key issues with the most recent releases do NOT appear in some of these older releases..
I then need to look carefully and determine exactly when and what source changes were made which had negative impact, I can say I have done some narrowing down, such as Dev 4 seems (only seems) cause I must verify everything over & over.. but seems like it works, many things I am comparing
Code: Select all
2018-03-30 09:20:03 Timer_OFF_ 9:20
2018-03-30 09:20:03 Timer_OFF_ 9:20
2018-03-30 09:17:55 Float_Switch_0 9:17
2018-03-30 09:17:55 Float_Switch_0 9:17
2018-03-30 09:17:53 Float_Switch_1 9:17
2018-03-30 09:17:53 Float_Switch_1 9:17
2018-03-30 09:15:03 Timer_ON_ 9:15
2018-03-30 09:15:03 Timer_ON_ 9:15
On Clock#timer, turns on pump, level rises until float goes from closed circuit to open circuit, rules fires before timer ends turning off pump, float returns to stop (NC) & then timer ends.
Uptime is excellent, no data missing in logs & logs not showing 8 of each event, only 2..
About 2, I am not sure if this is intentional or not, there maybe reasons for 2 duplicate log entries for everything ??
IE
Code: Select all
2018-03-30 09:20:03 Timer_OFF_ 9:20
2018-03-30 09:20:03 Timer_OFF_ 9:20
If you have followed my previous posts, on newer firmware many have 8 duplicate log entries
Yet to find the exact point 2 became 8, but I am on a mission and I will.
Then I will attempt to merge newer source changes over the older more predictable 'working as expected version'..
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
If you find some version after which the switch doesn't work anymore, please include that in the appropriate (new?) issue on Github.
FYI. I started working on ESPeasy around -dev12.
FYI. I started working on ESPeasy around -dev12.
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Yes, no problem TD-er, I have a plan and everything is coming together very nicely..
Which reminds me I have several things to do if I want faster progress.
I had better stop everything I am doing now and focus on those menial tasks..
Thank for the distraction @3.51AM
I want this done...
Which reminds me I have several things to do if I want faster progress.
I had better stop everything I am doing now and focus on those menial tasks..
Thank for the distraction @3.51AM
I want this done...
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
And so I backed tracked the first bug...
The GPIO14 showing wrongly all started in Dev_11, Dev_10 & older firmwares older work just fine..
Next bug to backtrack, is the excessive reporting
Serial output from removing a jumper cable between GPIO14 & GND - wait - Then replacing it
The GPIO14 showing wrongly all started in Dev_11, Dev_10 & older firmwares older work just fine..
Next bug to backtrack, is the excessive reporting
Serial output from removing a jumper cable between GPIO14 & GND - wait - Then replacing it
Code: Select all
SW : Switch state 0 Output value 0
EVENT: FULL_Tray_2#Switch=0.00
EVENT: FULL_Tray_2#Switch=0.00
EVENT: FULL_Tray_2#Switch=0.00
EVENT: FULL_Tray_2#Switch=0.00
EVENT: FULL_Tray_2#Switch=0.00
SW : Switch state 1 Output value 1
EVENT: FULL_Tray_2#Switch=1.00
EVENT: FULL_Tray_2#Switch=1.00
EVENT: FULL_Tray_2#Switch=1.00
EVENT: FULL_Tray_2#Switch=1.00
EVENT: FULL_Tray_2#Switch=1.00
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Oh nice, first firmware I try is:
ESP_Easy_mega-20180112_normal_ESP8266_1024.bin
Serial output from removing a jumper cable between GPIO14 & GND - wait - Then replacing it
That's what I am looking for, now when was it introduced ?
Fortunately is a bug that is always there, so takes seconds to check
ESP_Easy_mega-20180112_normal_ESP8266_1024.bin
Serial output from removing a jumper cable between GPIO14 & GND - wait - Then replacing it
Code: Select all
SW : Switch state 0 Output value 0
EVENT: FULL_Tray_2#Switch=0.00
SW : Switch state 1 Output value 1
EVENT: FULL_Tray_2#Switch=1.00
Fortunately is a bug that is always there, so takes seconds to check
- grovkillen
- Core team member
- Posts: 3621
- Joined: 19 Jan 2017, 12:56
- Location: Hudiksvall, Sweden
- Contact:
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Much appreciation for your thoroughness!
ESP Easy Flasher [flash tool and wifi setup at flash time]
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
ESP Easy Webdumper [easy screendumping of your units]
ESP Easy Netscan [find units]
Official shop: https://firstbyte.shop/
Sponsor ESP Easy, we need you
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
No problems Grovkillen !
These bugs are resource hogs I am sure, their impact can cause roll on effects,
such as Wifi disconnects, reporting over loads & even reboots..
While active in current releases I am sure it makes debugging 'other issues' harder too..
I have several more bugs I have noticed that need the same treatment, one at a time I will get through them.
These bugs are resource hogs I am sure, their impact can cause roll on effects,
such as Wifi disconnects, reporting over loads & even reboots..
While active in current releases I am sure it makes debugging 'other issues' harder too..
I have several more bugs I have noticed that need the same treatment, one at a time I will get through them.
Last edited by Oxyandy on 19 Apr 2018, 01:20, edited 1 time in total.
Excessive Reporting Bug
A fresh firmware flash, NTP, Wifi connection, DHCP, Domoticz MQTT controller
a switch with send boot state, not inverted, internal pull up ticked
Nothing else needed to replicate.
The point this 'excessive reporting bug' was introduced
Jumper cable between GPIO14 & GND, no need to touch the jumper
Simply tick "Send Boot state" and cold boot, the serial output shows the bug in seconds.
ESP_Easy_mega-20180212_normal_ESP8266_1024_DOUT.bin
OK
ESP_Easy_mega-20180213_normal_ESP8266_1024_DOUT.bin
BAD starts too much reporting -
This 'excessive reporting' is still a bug in:
ESP_Easy_mega-20180403_normal_ESP8266_1024.bin
However, I have not been able to test any firmwares released after this date, because the web server has not been loading.
The CRC : Settings CRC ...FAIL, started in the next firmware after mega-20180403.
a switch with send boot state, not inverted, internal pull up ticked
Nothing else needed to replicate.
The point this 'excessive reporting bug' was introduced
Jumper cable between GPIO14 & GND, no need to touch the jumper
Simply tick "Send Boot state" and cold boot, the serial output shows the bug in seconds.
ESP_Easy_mega-20180212_normal_ESP8266_1024_DOUT.bin
OK
Code: Select all
Subscribed to: domoticz/out
EVENT: System#Boot
SW : Switch state 0 Output value 0
EVENT: FULL_Tray_2#Switch=0.00 <- ONLY ONCE
WD : Uptime 0 ConnectFailures 0 FreeMem 20744
EVENT: Clock#Time=Thu,05:32
BAD starts too much reporting -
Code: Select all
Subscribed to: domoticz/out
EVENT: System#Boot
SW : Switch state 0 Output value 0
EVENT: FULL_Tray_2#Switch=0.00 <- Correct: as above
WD : Uptime 0 ConnectFailures 0 FreeMem 20448
EVENT: Clock#Time=Thu,05:29
EVENT: FULL_Tray_2#Switch=0.00 <-EXTRA
EVENT: FULL_Tray_2#Switch=0.00 <-EXTRA
EVENT: FULL_Tray_2#Switch=0.00 <-EXTRA
EVENT: FULL_Tray_2#Switch=0.00 <-EXTRA
ESP_Easy_mega-20180403_normal_ESP8266_1024.bin
However, I have not been able to test any firmwares released after this date, because the web server has not been loading.
The CRC : Settings CRC ...FAIL, started in the next firmware after mega-20180403.
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Good Day
Could someone send me a ESPEasy settings file for sonoff basic + mqtt (albertusgeyser@gmail.com).
Thank you
Albertus Geyser
Could someone send me a ESPEasy settings file for sonoff basic + mqtt (albertusgeyser@gmail.com).
Thank you
Albertus Geyser
- Methuselah
- Normal user
- Posts: 45
- Joined: 04 Feb 2018, 01:39
- Location: Boston, MA
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
The forum search feature is your friend.Albertus wrote: ↑23 Apr 2018, 18:32 Could someone send me a ESPEasy settings file for sonoff basic + mqtt (albertusgeyser@gmail.com).
N00b to the world of ESPEasy, but I've been programming since the days of punch cards and paper tape
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Albertus, this will be useful if you still need to get up and working.
There is no 'one config' suits all, we all need different things.
https://www.letscontrolit.com/wiki/index.php/ESPEasy
Any questions, please open a fresh topic
thanks
There is no 'one config' suits all, we all need different things.
https://www.letscontrolit.com/wiki/index.php/ESPEasy
Any questions, please open a fresh topic
thanks
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Good Day
Thank You Did get my solution:
Openhab to control relay with EasyESP on Sonoff Basic:
Switch Relay1 "Light" <light> {mqtt=">[mosquitto:/UnitName/GPIO/12:command:ON:1],>[mosquitto:/UnitName/GPIO/12:command:OFF:0],<[mosquitto:/UnitName/Device/state:state:default]"}
Thank You
Albertus Geyser
Thank You Did get my solution:
Openhab to control relay with EasyESP on Sonoff Basic:
Switch Relay1 "Light" <light> {mqtt=">[mosquitto:/UnitName/GPIO/12:command:ON:1],>[mosquitto:/UnitName/GPIO/12:command:OFF:0],<[mosquitto:/UnitName/Device/state:state:default]"}
Thank You
Albertus Geyser
Re: ESPeasy Mega running on Sonoff Basic - Bad Behaviour
Hi Albertus,
As I said "Any questions, please open a fresh topic"
I have no experience with "Openhab"
I use "Domoticz" for simple data logging & some complex rules for alerts for alarm / fault situations
I can help with general questions about Sonoff Basic units, but again "New Topic"
thanks
Had you opened a fresh "New Topic" your question would get greater exposure..
As I said "Any questions, please open a fresh topic"
I have no experience with "Openhab"
I use "Domoticz" for simple data logging & some complex rules for alerts for alarm / fault situations
I can help with general questions about Sonoff Basic units, but again "New Topic"
thanks
Had you opened a fresh "New Topic" your question would get greater exposure..
Who is online
Users browsing this forum: Google [Bot] and 57 guests