I have a problem with Ostent device. Whenever I reboot or update bos server I have to go into comfort click editor and manually change baud rate to some other number and then back to the number 115200 otherwise it does not connect with the bos server and it stays that way until I do this change manually. Is there any way to avoid that?

The cameras stopped working on application for mobile phone after update.

Is there any solution for that?

Satel status value of partition shows numeric values (index) instead of text statuses. Can you provide list of number statuses corresponding to text statuses and/or better change this function in bOS?

Since the latest updates on bOS and Denon HEOS there seems to be an issue with forming/keeping groups of speakers.

The Denon node did work as expected, but since the update it tries to control the group. But by doing so it disassembles the existing group, or (if the group’s not there yet) will fail to combine the speakers into a group.

Anyone experiencing the same behavior?

By the way:

Denon is having another problem, it’s losing its favorites all the time. I’ve contacted Denon support for that.

Hello.

I am getting this issue ReadMProp failed with Jigsaw version 1 and ETS 6 when trying program KNX over local network but diagnostic is working. Is there some fix for it?

I try to connect to Hikvision doorbell using http and authentication is Digest Auth. I connect successfully from Postman but not using http from confortclick. Any idea if http suport digest auth and how to do it?  

Hello

I have a KNX energy meter in front of a stove, and there is a 0-10V KNX regulation in front of the air extractor, which is already controlled, by percentage from 0-100%.

Energy, DPT type = 14.031

0-100%, DPT type = 5.001

With a consumption on the stove of, for example 300W, the air extraction level should be set to 15%.
At 500W, the level should be set to 25%.
At 1000W, the level should be set to 45%.

The stove's heating element, is switched on and off at a fixed time interval, and the interval becomes smaller, as the stove is regulated to a higher level, and the consumption is getting higher.
After all, the air extraction must remain constant, as long as the consumption is, for example between 300 and 500W.
When the stove is switched off (less than 0.10W), the extraction is desired to continue at 15W for 5 minutes.

If we use the same KNX IP Interface or Router (in this case) on multiple points in bOS will bOS use only one channel of the KNX IP Router/Interface, or as many as the connection points?

For example, in a hotel, rooms A101 through A115 are under the same KNX line (1.1). The KNX IP Router of that Line supports 5 channels and its IP is 192.168.1.2. As shown in the picture, we've separated each room for a more clear structure. Is it possible to set all 15 rooms in bOS to the same KNX IP router or will the limit of the IP router will be reached?

Additionally, is there a difference between "KNX IP" and "KNXnet/IP (Falcon)" apart from the ability to remote program the KNX installation with the option of "KNX IP"?

Thank you in advance.

We are writing to inquire about the following topics for our upcoming hotel building BMS project:

• What type of Comfortclick device is recommended for a hotel building BMS system?
• How many devices does Comfortclick support to connect with the Modbus TCP protocol?
• Can 2 devices be managed remotely on the same bOS interface account at the same time?

We appreciate your assistance.

Hello,

I sucessfully integrated a Shelly Plus Plug S via MQTT.

MQTT messages that contain "switch" updates (when it's turned on/off) are successfully interpreted. I catch them with Token Name : params.switch:0.output (see screenshot below).

Meanwhile, the Shelly device is also sending other MQTT messages with energy consumption information. When doing so, the parameter "output" is not present in the JSON file, resulting in a Exception error : Error parsing received data. Value cannot be null.Parameter name: value

Any advise how to prevent these errors ?

Thank you.

---

JSON message when "output" changes. This gets successfully parsed. Example of a switch off message :

{"src":"shellyplusplugs-e465b85ccccc","dst":"shellyplusplugs-e465b85ccccc/events","method":"NotifyStatus","params":{"ts":1701336805.47,"switch:0":{"id":0,"apower":0,"current":0,"output":false,"source":"WS_in","voltage":0}}}

Periodically JSON message to notify energy updates. These don't get successfully parsed (as it is missing the 'output' parameter. Example :

{"src":"shellyplusplugs-e465b85ccccc","dst":"shellyplusplugs-mytext/events","method":"NotifyStatus","params":{"ts":1701352440.40,"switch:0":{"id":0,"aenergy":{"by_minute":[5.012,8.202,0.000],"minute_ts":1701352439,"total":4.922}}}}