Hello.

I having big trouble to programming KNX over Jigsaw with ETS 6 when I test for bus it return error but I can see data on bus with diagnostic but wehn I try to program something I got error Connection closed by remote device. Have anybody similar behaviour?

I think that to have the possibility of comment a line or section and add comments into a program might be really good. For development of task for example or other reasons.

Is it possible to customize the formatting of text in a Confirmation Dialog Box? Is it possible to customize the size of the Confirmation Dialog Box? 

It is good feature - especially the ability to add a pin code.

But its presentation could be better. See my screen shot.

Thank you.

Confirmation Dialog Box.png

Hello,

I would like to change the temp set point for at least 4 rooms with one button in CC. That means I have to communicate with at least 4 group addresses.

I'm sure there is an easy solution.

Can anyone support me?

Thank you 

André

Hello,

Would it be a big problem to provide precise information about what has changed in a given version?
For example, the latest version has changed the way of presenting modbus type objects in relation to the last upgrade - there is no information about it. Every time an update is a surprise of what's new. We cannot do that for commercial customers.

Andy

Hi,

It seems, after searchign in manuals and forums, there is no ability to allow inputing holidays or vacation days through the BoS app, the only way to input holidays and vacations is through the BOS Configurator. 

Is this right_ If so this is weird, not allowing to input a BOS client update its vacations or bank holidays through the front end - or even through an API accessing the typical government site that gives you details of bank holidays.

Has anyone done the above? It feels quite basic

Hello ervryone,

I have probably a basic question but I don't understand what this function does ?

Any ideas or exemple ?

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

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

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.