I am using the Analog Log to create trend graphs and keep track of history data. But I noticed that the Analog Log does not store negative values! Any negative value is stored as 0.

Is this a bug or done intentional? I would like to log negative numbers. Or am I doing something wrong here?

I noticed after installing the latest bOS Server, that any port and any protocol is enabled in the Windows firewall, creating a serious safety breach into the system. Especially if the server is connected to the internet or the home network is full of iot devices that are easily compromised. This is a serious security issue. Also looking at the amount of hack or intrusion attempts that happen every day on bOS, as parts of it are connected to the internet. A compromised bOS server gives the attacker full access to the rest of the network with these firewall settings. And it is a real risk if you consider the poor TLS protocols that where still in use before bOS 4.9.0.

I also noticed that multiple Firewall entries are created and probably not cleaned after upgrading to a newer version of bOS.

What are the minimum ports/protocols needed by bOS to function properly?

Small glitch in bOS Configurator in the Value TAB. You can see the values from the Settings TAB. This occures throughout the program. 

Occures in Windows 11 and Server 2022. 

When setting-up MQTT and setting Internal broker to TRUE, then the local IP address is used of the client that is running the bOS Configurator (in my case my laptop). This is the wrong IP address and can not be changed! 

It should be the IP address of the bOS Server. 

When setting-up MQTT from the bOS Server, then the IP address is correct.

Using version 4.9.0. When importing new KNX data through xml file, the import tool shows that these objects already exists. But in reality they don't. Import does go smooth using export data from ETS6. 

If I manually change the light status (on/off or brightness) the button shows correct status on the dashboard, however when using a scene to control the light(s) the button / dimmer doesn't refresh and therefore shows incorrect status. This becomes confusing for the user as it's showing the wrong status of the devise.

Should I be using the 'request values' function in the associated scene to force the update?

When I used 'request values' for 6 devises (lights) in a program and triggered it when the scene was activated it did what I expected which was update the dashboard, however it was extremely slow and therefore is not an acceptable solution.

What's the best practise solution for this scenario?

Hello, 

I have some servers that are using older version of bOS Configurator. 

bOS configurator will download the correct version, but once logged out, it doesn't keep that old version. And each time I connect it will have to download the old version. 

Is there a way I can download an old version so that it connects directly and doesn't have to download the version ? 

Thanks 

François 

My android device is unable to connect to bOS Client. I have bOS Client app v4.8 and my device can't connect to the server.

Hi,

A very simple KNX device sending a value every 20 secs, is put into an analog to pain a curve, however, BOS does not seem to calculate properly the values, e.g. Mx value written to database today  is 7.79 (as per screenshot), however, the calculated value "Day max" is shown as 4.0 (as per screenshot). When the graph is painted on a screen the situation is further funnier, as max values painted doe not correspond when jugglign between the Hour, Hour, Month views (i.e. if the hour max value within the running month is 4, the month max value withint the running month is lower than that)

Any thoughts?

Data on the database of the analog log 

Calculated values by BOS

Hi

I need some help of how to do the following in bOS

We have machines with on-off  running speed status retrieving via http

requirements :

1. We need report of how many hours it ran in every 24hour - monthly  (Daily report - monthly report)
2. Production report (after converting the machine speed into production) Daily report 24h - monthly report