
Sonos function (remember now playing)
Hello ervryone,
I have probably a basic question but I don't understand what this function does ?
Any ideas or exemple ?

4.8.8 Server update failed, please try again or contact Support! linux
fail to update linux , any ideas?

Push quota exceeded.
Hello
I have new problem with the push function on ios.
Devices : 25.02.2021 22:57:50 : Error : General\Messaging : Error sending iOS push: - Dave 7+ - - Push quota exceeded.
The Push function is limited ?
Thank you
Dave

Android client and 4.8.5
Hi,
After installing 4.8.5 update the client on an Android 7.5 tablet (latest available version) quit working and could not establish a connection to server. Clearing keys and cache did not help - still no luck. A workaround with Chrome browser IP direct connection and desktop shortcut works perfectly but it will be troublesome for bigger installations with many fixed tablet installations.

Jigsaw 4.8.5 weather not working
Hello.
In last update to 4.8.5 after linux update I notice that weather is not showing any values. I try reboot and readd weather but with no result.

event logging
What is the most easy way to have an event-log (visible in the user interface)?
Style:
Door open @ 12:35
Door Close @ 12.37
...
I tried with analog log, counter, scheduled tasks,... but no succes
Should be very straigforward I guess but can't find any example

Calculation task (wrong calculation method coded)
The calculation task does not work when both inputs change at the same time and the output of such input is used for further calculation, this is because the Calculation function, as explained in the manual, and confirmed by the trace log, runs a calculation immediately when one of the parameters in the polynom changes.
Effectively, because in practice the two variables of the polynom do not effectively get updated at the same time, there are a few seconds of difference, probably because bOS serialises tasks rather than parallelise them, then this yields to errors. In summary do not use the calculation task is the variables change at the same time because you will get wrong calculation. This is an interesting bug.....
Example, a water line running a main pipe split in two branches, you do not need three water counters, but just two to know the water consumption of the two branches and the total.
Total water counter A
Partial water counter B
Partial water counter C, the result of subtracting A-B
what bOS incorrectly does
KNX water counter A
KNX water counter B
Calculation task C, which is the result of A-B
When water is used in one of the branches, let's say branch B, then two counters get updated, counter A and counter B, because the counter update do not happen at the same time, but serialised as done by bOS then the sequence is as followed
a) Counter A updated
b) Counter C calculated because one of the variables in polynom changes
c) Counter B updated
d) Counter C calculated again because one of the variables in polynom changes
Because C has changed twice, then if you use the ouput of the calculation as input to a CounterLog, then you will get disastrous results in your Counterlog, the counter log will take the incorrect value calculated in step b as an input, hence contaminating the counterlog.
Because there is no documentation of this, it has taken a significant amount of time to find the root cause that was driving my CounterLog to go nuts, it is just bad this situation happens and it is not documented anywhere. I assume not many integrator are using calculation tasks because to me this is very basic

Todaycount() value in CounterLogs, bug
Hi,
When using a CounterLog tasks, the input value used to populate its values only trigger the function to update the TotalValue() value, he remaining values (e.g. Average, Last 24 hours, Daily) are only updated every hour on or about on the hour.
The above possess a significant bug that needs to be fixed, otherwise those using any of those values updated only on the hour or immediately after receive incorrect calculations. This is because bOS calculates those remaining values after the o'clock, hence allocating such value to the next day hence creating and giving significant incorrect information, if this is not a bug then you should forbid using those values in calculations as the result will always be wrong
bOS version 4.7, the below screenshot shows this perfectly, the three graphs use the same calculation against the value. I thought I was doing somethign incorrect, to the point I had to create specific test cases to find out what the hell was going on, effectively proving somethign is wrong in bOS
Graph1 uses 3 variables (one always 0) in the polynom, using TotalValue(), which is updated on the spot by bOS
Graph2 uses 3 variables (one always 0) in the polynom, using TodayCount(), which is NOT updated on the spot by bOS, but on the hour, after the o'clock
Graph3 uses 2 variables in the polynom, using TotalValue(), using TotalValue(), which is updated on the spot by bOS
The results can be easily seen below, at 20:00 the counter shows the correct usage of 1 L of water between 20:00 and 20:59, two graphs are correct, the third one is wrong because the TodayCount calculation happens after 20:59:59 hence pushing the 1L usage of water to the 21:00 to 21:59 block. weird ehh? The worst part comes at midnight, because at that point the TodayCount does the best weird calculation, the whole day calculation moves to the next day, hence creating an artificial and incorrect 24 L use on the following day, completely wrong way of calculating the values. The 24L was the actual waster of water in the previous day, but because the function does the calculation past midnight then we get a terrible wrong result, showing that actually past midnight there had been a waste of 25 L of water.

IFTTT Newest plans (damn...)
Hi everyone,
By now, probably everyone's already know the new plans from IFTTT. It was a matter of time for them to create a paid subscription. Not that I'm criticizing (the company needs to ear revenue, although they were sponsored by the multiple services companies).
From now on, they offer two plans (Standard and Pro).
Standard plan only allows to create 3 applets of our own. So for those who have multiple applets like me, we're downsized to 3 on the free plan.
It's a shame, but it was a matter of time.
I can either use Tasker, or keep it up with only 3 applets, so I'm not suitable for the Pro plan. The Pro plan is "cheap", but for me it doesn't make sense while I can use Tasker for my RPC integration.
I thought I would let you know...
Best regards
Customer support service by UserEcho