Let's Control It

GravityRZ

i will try it out. i used to use arduino (which i got working some time ago) but lately it is only giving errors it amazes me that all these platforms are not idiot proof(yes i am the idiot) how hard is it to make 1 package which compiles out of the box all these dependencies are killing functionali...

GravityRZ

I followed the tutorial on https://www.letscontrolit.com/wiki/index.php/Tutorial_building_and_uploading_with_platformio but still atom gives me errors i selected espeasy.ino pressed F7 and selected normal_esp8266_4m1m i see this at the beginning, do i need to remove the ifdef and last endif #ifdef P...

GravityRZ

no problem.
next time i will mention what i changed

GravityRZ

tparvais wrote: ↑02 Apr 2020, 22:36 I found it myself:
there is no need to use [] in on .... do statement...

or you could have read my advice in which i told you to remove the []

GravityRZ

thanks.

i found a lot of threads but none stated that it was implemented

classic RTFM HaHa.

GravityRZ

seb82 wrote: ↑01 Apr 2020, 15:05 Easier: use the Timezone Offset option in advanced configuration

thanks tried it at the beginning but is was not working (offset to big)
tried it again and this is a workable solution when it is 15:00 and want to test 00:00 functionality

GravityRZ

is the problem not that you do a check on an ON statement i am not an experienced ESPEasy rules guru bu can you try on MQ7_Calibration_Start-Stop#etat do //switch pressed TaskValueSet 8,1,[MQ7_Calibration_Start-Stop#etat] set switch pressed setting to Calibration_MQ7#etat if [Calibration_MQ7#etat]=1

GravityRZ

i need to test something on the esp and like to set the time manually to a certain time (23:59)

is this possible?

GravityRZ

maybe you are explaining something i am already doing because i still do not get it. i get the explanation, i get your explanation i do not get how this relates to my situation i currently wait for Watermeter#count to change (this is an event right) i then act on it by checking the value of watermet...

GravityRZ

i have read it but still not clear. Event,Multi=1,2,3,99 what is Multi? is it the name of the Task? i have a pulsecounter called watermeter with Count, Total,Time i also have a temp sensor with only trmperature. i understand that you can trigger an event on a base that something is received but do n...

GravityRZ

thanks. i will try to narrow my search. eventually i will solve this thing :-) i recognize the Clunk sound HaHa how can i use the event variables and the interval recorded from the rules page. i know i have read somewhere that there is a change between values recorded and values ehich are vissible o...

GravityRZ

ok i will try. my pulsecounter is set at an interval of 1 second(so the counter resets every second) the max pulses i get is around 1 pulse every 2.4 seconds(25 liters per second) so to avoid jitter(which is also done with the debounce time) i only send a pulse if the time is greater than 2000ms(eg ...

GravityRZ

thanks for checking. i can use all the help i can get.. here are the devices so you can see what i am using. i have a pulsemeter called Watermeter and a dummy device called Water so it looks like that rule is ok. the reason for dummy device is i can not use the values from the pulsecounter direcly(m...

GravityRZ

@TD-er i discovered what looks like the root cause of the problem. however the problem seems very strange. i changed the rules so i can see what the total count is as well as the daily count on both ESP and in domoticz. what looked like a MQTT or transmission problem actually seems to be a calcultat...

GravityRZ

ok thanks. everything was totally stable for 3 days and and of a sudden 5 missed pulses. i suspect that this problem might be related to wifi stablitity this is easilly checked because the amount in the ESP is different then the one in domoticz. Since the values in the ESP are now right i am going t...

GravityRZ

ok i will mention it on github as a wanted feature.
no hurry

GravityRZ

i understand

for multiple pulses per second it is not a good feature but for measuring the watermeter (max 1 pulse every 2 seconds).
maybe making it an option and when that option is enabled force the minimum debounce time to 1-2 seconds to avoid running out of resources

GravityRZ

still testing with the 250ms interval settings and 300ms timeout setting. i took a shower which is taking approx 12 liters a minute (5 seconds between pulse) i noticed that despite the 250ms interval setting the time between messages when they arrive at domoticz is not 250ms but 200ms or sometimes e...

GravityRZ

i think i am using the functionality you mean. i do not care if the pulsecounter looses its values after a reboot because i copy all the values i need to a dummy device which survives a reboot i also attach my script i am using mqtt to send out stuff to domoticz but also added the http variant comme...

GravityRZ

Same here. in a time where we complain a lot it is very nice to see that other people make time and effort to please other people. ESPeasy is like it's name, very easy to implement and it integrates very nice with Domoticz or Node-Red. Sure it is not perfect but we do not want it to be perfect becau...

GravityRZ

with http i experiencd the same problems(most of the time extra pulses instead of missing pulses) so it looks like it has nothing to do with the protocol now with MQTT i experience more logical things, if i miss a pulse i can see that(because it was counted inside the esp but not in domoticz) maybe ...

GravityRZ

yes, i only send +1 to an incremental counter. That counter also shows the daily usage. so i can check the real meter value against the domoticz meter value and i check the total counts is esp(gets reset at 00:00) against the daily usage on the domoticz meter. both numbers need to be the same, which...

GravityRZ

my MQTT broker is local and running as a mosquitto package on synology. the behaviour i am facing is this i use a pulsecounter to send out 1 pulse per liter for my watermeter this pulse arrives in domoticz on a counter incremental once synced every pulse detected should increment the watermeter in d...

GravityRZ

i do not think that the queue gets flooded because like i said i am sending out 1 message every 30 seconds, 1 message every 60 seconds and when the pulsecounter is counting max 2 messages together per 2 seconds. my thoughts were when those messages once in a while are send out at the same time. i ch...

GravityRZ

good info. it is not that i want to send out messages faster than 100ms but i think that once in a while this is the case thus causing lost or multiple packets i have a temp sensor which sends out temp every 60 seconds the pulsecounter triggers a rule which sends out 2 messages right after each othe...

GravityRZ

check, Thanks. i am doing some tests with the delays to see if the pulsecounter can react more accurately. i suspect that the 100ms delay is sometimes causing dropped messages or repeated messages. when lowering the delay to 10ms i got instantly more pulses(probably messages which were send out more...

GravityRZ

offcourse i first checked the manuals and documentation :-) Minimum send interval is in the docs, message interval is not. it looks like it is the same setting but you can change it on 2 different locations(controller settings and advanced settings) i changed controller setting to 200ms and left the...

GravityRZ

i see MQTT interval settings in 2 different places

under
MQTT controller
Controller Queue
Minimum Send Interval: 100[ms]

under
Controller Settings
MQTT Retain Msg:
Message Interval: 100[ms]

what is the difference?
is this interval also used when using rules?

GravityRZ

tested it and it makes no difference. changd things back to use only the variables from the plugin to get a more consistent flow value

GravityRZ

i am testing this at the moment to see if it is more accurate when used with the generic pulsecounter. The pulsecounter only triggers on an interval base. When you set the interval to 1 second it is workable but then you can get to a situation that when the counter is triggered and the 1 second time...

GravityRZ

good to hear.
i recently had an idea to reset counters at midnight.
Turned out that it did not work(because i did not have an accurate time)
so i turned on NTP so let's wait and see

GravityRZ

when i look at my MQTT data it also is a JSON string but it uses double quotes(") instead of single quotes(')

so maybe you can try to change the MQTT code you are sending and replace ' with "

GravityRZ

i think you can not get a single value. what you can get is a json string with all the values if you have node-red it is easy to get a single value from it http://192.168.1.129/json?view=sensorupdate otherwise the idea is to send the value from espeasy to another application by using http or MQTT wh...

GravityRZ

in my current rules i trigger a task by monitoring a change of that task value. does it make a difference to monitor a gpio pin instead and run a task, based on that change. eg, is there a difference in responsetime, cpu overhead i know when i want to monitor a gpio pin i need to add a monitor comma...

GravityRZ

i do not use ntp since i do not need the time.
this might also help in stability.

probing ntp servers and failing to update might screw up the data flow and affect things(eg when the esp is busy updating it can not do something else)

just my thoughts

GravityRZ

i have the latest mega bild running for a week now and sofar it seems more stable then previous one. i use it as a pulsecounter. with the previous build i had the idea that i was either missing pulses or i had to much pulses(jitter). With this build i hardly miss a pulse and sofar no big jitter prob...

GravityRZ

not an expert but recently figured this out 1/ depending on "interval" value defined for each sensor ? If I set Temprature measurement to 15s, the temp will me measured every 15s and dat sent over MQTT. Correct, if interval is set to 15s it will send a message every 15 seconds 2/ depending...

GravityRZ

got it working.
i noticed a connection which was not 100% ok
under a microscope i was able to do some soldering on the pcb.

also once i got it working i tested by removing the SDO and CSB connection, still working and defaults to I2C and 0x76
thanks for the help

GravityRZ

thanks i am going to inspect the module under a magnifying glass because it is hooked up exactly like you said. i even changed address to 0x77 to make sure there is not a bug in the plugin which defaults to that(both 0x76 and 0x77 do not work) if i bought this one at aliexpress i could live with tha...

GravityRZ

yes i have that one.
good for testing but i need something for final results

eg with the wemos board you can solder everything on the board

i now use header connectors and solder everything on those but since the 2 header connectors are not mounted to each other the components float

GravityRZ

it is this one.
got it from opencircuits (expensive but fast shipping)

so you are saying VCC should be connected to 5V (on the site it states max 3.6v)
as far as i can tell there is no standard for VCC

: bmp280.JPG (38.06 KiB) Viewed 15445 times

GravityRZ

no it did not discover the module.

also i tried putting the module to 0x77 (connect SDO to 3.3v) but this did not help either.

really strange

tried other wemos module but the same result so the problem is either a faulty module or something i missed

GravityRZ

i have a BMP280 connected to a Wemos D1 mini running latest ESPeasy mega software i am using the BMX280 plugin VCC on 3.3V GND op GND SCL op D1 SDA op D2 CSB 3.3V (to select i2C) SD0 GND (to select 0x76 adres) somehow i do net get any data in hardware page is also on default SDA GPIO-4 D2 SCL GPIO-5...

GravityRZ

i noticed that regarding wemos D1 mini lots of options are available with either header connectors(which are included) or daughter pcb's for the nodemcu's (V2 and V3) i can not find anything. just a simple pcb with headers should do the trick but nothing exists, you need to make everything yourself ...

GravityRZ

ok but if you set the interval to 1 second you get at least 1 trigger per second. this means that if the value changes within that second it is send. if it changes more times in 1 second then indeed it does not work. i also wanted the device to send a pulse whenever a change is received instead of r...

GravityRZ

i would do an extra check on the time to skip that bounce first on the pulsecounter device deselect send to controller and put interval to 1 second Then you need to know what your fastest good pulse is going to be eg if your fastest pulse is 2000ms then do a test that the pulse received is a good pu...

GravityRZ

setup-settings-accept new hardware aanzetten. daana zouden apparaten die de rflink herkent automatisch ook in domoticz moeten verschijnen. Je hoeft ze dus niet handmatig aan te maken. zo werkt het bij mij(maar ik heb een RFXcom maar ga er van uit dat rflink hetzelfde werkt) bij RFXcom kan ik echter ...

GravityRZ

change means it counts a pulse when the signal goes from 0-1 and also when going from 1-0 in your case you want to count the pulse so it needs to be either falling or rising falling counts when signal goes from 1-0 rising when signal goes from 0-1 you state your pulse is 50-100ms what you need to kn...

GravityRZ

indeed we should here is the complete script(i left some stuff in so that it is backwards compatible in case i want to start counting pulses again every 60 seconds On System#Boot do // When the ESP boots, do TaskValueSet 3,1,0 // TaskValueSet TASKnr,VARnr,Value, Reset the Liters counter to 0 TaskVal...

GravityRZ

sure, here is the code On Watermeter#Count do // When Pulse is detected if [Watermeter#Count] > 0 SendToHTTP 192.168.1.50,8084,/json.htm?type=command&param=udevice&idx=337&nvalue=0&svalue=1 TaskValueSet 3,3,60000/[Watermeter#Time] SendToHTTP 192.168.1.50,8084,/json.htm?type=command&a...

Search found 206 matches