the solution is to buffer the 15 minutes humidity values for 7 hours and read the oldest value out of this fifo buffer.
With ‘only’ rules and variables available this is difficult. In coffee or javascript this is easy.
I could write a small swiss-knife pimatic plugin to support this as a first tool.
-
Your help is needed - question regarding rules and variables
-
This Sounds like a plan. Let’s give it a try
And thanks again for your time and help! -
@Andre3000 I released a first version of the pimatic-tools plugin.
It has 1 device type called VariableDelayDevice. You can imagine what its for.
It can be installed via the plugin page (browse tab).
The readme should explain how to use it.
Let me know what the results are and if anything should change.
I’m also testing it, but because of the delay it takes some time -
@bertreb Thanks again for your time and help!
The installation of the plugin was easily possible without any issues.I´m still testing the plugin and I will come back to you as soon as possible.
BR,
André -
@bertreb I´m not sure if the plugin is working as intended. The variable is sampled every 15 minutes but the value is not changing. It stays at the same value as 7h before.
Could you double check with your environment?
Br,
André -
Hi andre,
What is the delay time you use? because after the startup during the delay time the value stays the same. And that is because after startup there’s no info on the past, so i have to build up the delay buffer.
I have a test running with 60 minutes delay and sampleRate of 15
As you can see in the graph the value is changing with a delay of 60 minutes
-
Thanks for your fast reply.
The delay time is 420 minutes. I knew that there can´t be values for the first 7h but the device is now running for longer than 7h.
BR, André
The timestamp is not changing?
-
The screenshot is only covering 3 hours.
I mean the timestamp of the value. You see when you click on the value T 15% or RH 58%A few questions to isolate the problem:
- Is the timestamp of the value also the same or does it increases after 7 hours?
- Are you sure that the actual value is changing
- What is the result if you take a shorter periode like i did (60 minutes delay with 15 minutes timeSample)
- Did you use the latest version 0.0.5. Because earlier version had a wrong delay periode (like times 10)
-
I´m not sure if this is the information you are asking for…
Please forget the values before 2 p.m. <- wrong setup of the device.
The timestamp after 2 p.m is changing every 15 minutes as expected.A few questions to isolate the problem:
Is the timestamp of the value also the same or does it increases after 7 hours?
- Could you please specify “timestamp”
Are you sure that the actual value is changing
- Yes, I can see the changes in the event log
What is the result if you take a shorter periode like i did (60 minutes delay with 15 minutes timeSample)
Did you use the latest version 0.0.5. Because earlier version had a wrong delay periode (like times 10)- I just saw that i´m still on version 0.0.2
I will test now the newest version and report again.
BR,
André -
@andre3000 thanks for the info
If you were on 0.0.2 the error in the delay time was probably causing the problem.
In your setting the time before any change would have happened was 420 * 15 = 6300 minutes = 105 hours = 4,375 days