NOTE: This is not a support forum! For questions and support go here: https://www.letscontrolit.com/forum/viewforum.php?f=1
How can we trigger this problem?
With firmware ESPEasy_v2.0-20180124 or later (testen till ESPEasy_v2.0-20180206) i have an issue with
sending (publish) MQTT message within rule. for example:
on Pushbutton#SW04 do // trigger wanneer switch veranderd toggleswitch
if [RelayStatus#SW05]=1 do
gpio,5,0 // Relais uit
Publish /Bewatering/Power,Off
// TimerSet 1,60
When i load firmware ESPEasy_mega-20180114 or earlier everything works fine.
Does the problem presist after powering off and on? (just resetting isnt enough sometimes)
Yes
Tell us what should happen?
Message published with MQTT within rule
Tell us what happens instead?
nothing
Hardware:
Wemos D1
Software or git version:
mega-20180114 development
ESP_Easy_mega-20180114_dev_ESP8266_4096
rules1.txt
The only notable changes between 20180114 and 20180116 were:
Both are somewhat time related, but I guess I'll have to look into the source code, since I will not try to wake my daughter and ask her about watering the plants :)
So let's hope the problem is in the code, or else you have to wait ;)
Hmm, maybe @Grovkillen can also have a look at your rules first, before I dive into C++ code without knowing what to look for.
Please check if this command work in advenced options tab:
Publish /Bewatering/Power,Off
06.02.2018 8:33 PM "Gijs Noorlander" notifications@github.com napisał(a):
Hmm, maybe @Grovkillen https://github.com/grovkillen can also have a
look at your rules first, before I dive into C++ code without knowing what
to look for.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/letscontrolit/ESPEasy/issues/828#issuecomment-363538750,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHOUzD2BG98Ohq-zUeq9zyZfpVf8Su9ks5tSKkSgaJpZM4R7cIx
.
Publish /Bewatering/Power,Off
Works for me.
Strange, when i upgrade the firmware the publish stops working. When i downgrade to ESP_Easy_mega-20180114 it works again. This is reproducable
So it must probably have something to do with the time functions I moved?
I met the same problem with 2.0 firmware (ESP_Easy_v2.0-20180221_test_ESP8266_4096.bin)
But mega firmware is OK for me. Please try. (ESP_Easy_mega-20180221_test_ESP8266_4096.bin)
Controller: OpenHAB MQTT
MQTT Broker: Mosquitto
Rules command: Publish /%sysname%/LEDswitch/state,1
On the other hand mqtt.loop() will not be executed if deepsleep is enabled.
@uzi18 That's an interesting remark you just made.
Will have to think about it, how the new idea of timers should be implemented.
Maybe somehow related to #827 ?
OpenHAB MQTT + rules + works in Mega, not in v2.0
Is this still an issue?
Hi Gijs,
I shall try it with the latest build
Regards,
Peter van der Veer
Van: Gijs Noorlander [mailto:[email protected]]
Verzonden: vrijdag 23 maart 2018 14:39
Aan: letscontrolit/ESPEasy
CC: arduinopjotr; Author
Onderwerp: Re: [letscontrolit/ESPEasy] Publish to MQTT from rule stopped working (#828)
Is this still an issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/letscontrolit/ESPEasy/issues/828#issuecomment-375667602 , or mute the thread https://github.com/notifications/unsubscribe-auth/AiHsisMHtSrVAZvSJxdL_2xB75UkMBqcks5thPsAgaJpZM4R7cIx . https://github.com/notifications/beacon/AiHsisZk39cSYNDC0u38ftUqQtZna7t9ks5thPsAgaJpZM4R7cIx.gif
A report please? :)
ok, further to this
I have a mosquitto broker running on Raspbian Stretch - all latest versions
My IP address publishing rule worked on the previous versions of ESPEASY - as above, and then stopped working.
I just loaded up mega-20180331 DEV versions on many different ESP's and the rules publishing to MQTT appears to be working again!!!
Thank you.
Out of interest, here is my rule set
On System#Boot do //When the ESP boots, do
Publish Instrument/%sysname%/SY/IP,%ip%
timerSet,1,20 //Set Timer 1 for the next event in 20 seconds
endon
On Rules#Timer=1 do //When Timer1 expires, do
Publish Instrument/%sysname%/SY/IP,%ip%
timerSet,1,60 //Resets the Timer 1 for another 60 seconds
endon
Hey, seems that this issue is still there, on my ESPEasy, I've no Publish command nor timeSet working !
My hardware : Sonoff s20 EU V1.3 - 2017-2-16
Build | 20102 - Mega
Libraries | ESP82xx Core 2_4_1, NONOS SDK 2.2.1(cfd48f3), LWIP: 1.4.0-RC2
GIT version | mega-20180502
Plugins | 47 [Normal]
Build Md5 | d855a355bdd12517f5ec6a7824f7843
Md5 check | passed.
Build time | May 2 2018 02:03:14
Here's the simple rule I've implemented:
on Button#State=1 do
timerSet,2,10
Publish /Prise_Jade/test/State,1
endon
on Rules#Timer=2 do
gpio,12,1
endon
And look at the logs there : https://pastebin.com/mgBPjRZn
(From the boot to the event)
btw, funny thing, I realized that empty rules are stored also when you open it for the first time, maybe storing a space in the rules.txt ? Not an issue, but if you don't open the rule set, then, it's not saved in the ESP...
Could you please also test with the last release I made last night, not the nightly build.
It is in the releases section.
There has been an issue with the compilation of builds lately
@ScanxTaz Download from Here
Thanks, will give a try this week and let you know my findings
testing... Having some difficulties to find which image I should choose from the zip you sent me :)
You should be able to use the nightly builds again. (not todays build, which is deleted because of a bug)
For example 20180513.
And then pick the version based on the processor you have (ESP8266 or 8285) and the amount of flash you have.
You could see this information in the sysinfo page on the current version you run.
Yo, thanks for your support. I'm currently trying to reset my sonoff, but it seems i've issue with the flashing, I suspect the DOUT symptom. (it flashes to 100% but at the end, no new image on the chip, and still running the previous version)
I'm using my wife's laptop on #fuckdows so will give a try tonight with my ubuntu, will be better I think... Oh... It's maybe me to you now :) #nobodyIsPerfect :)
Keep you posted
OK, you can close the issue, working on my side...
It took me a Loooooonnnng time to realize that the config is kept when I'm upgrading :) lol
Thought I would have to reconfigure everything...
Wonderful job guys, thanks.... I'll continue to follow and post logs in case of issue.