when i try to connect my lg tv i get the following out message in my visu.

he first time I allowed this on my lg tv...

With friendly greetings

Hello in 4.3.3 update I see some incorrect translation in Slovak language in graph set on days.

I have a KNX light sensor on my roof. Problem is that I'm having difficulties separating direct morning light and indirect light in the afternoon.

When I found the sun position parameter I included it into my automation, ruling out any position the sun is blocked by other buildings or is hitting other sides of my house.

After first day of testing this i see that this position stops at 100. I guess this means that this actually is not referring to the suns position, but more a percentage of time the sun is over the horizon.

A calculated parameter with the suns position relative to the compass would be great for this purpose.

Other suggestions are welcome

Is it possible to create a customized driver in c#?

Best regards

I run comfortclick configured scenes with the press of a KNX button. It would be handy if I could run the same scene inverted (to turn off the specific lights for example)

Hi guys!
I've been using the software for Windows for a few years now, and I've never had any "serious" problems, everything always works well, for all our customers (here's the record that I love this product lol).

But now, with the new version 4.10.4, I noticed problems with MQTT communication on all the devices (Tasmota) that I use, they simply cannot connect to the broker, they remain in an eternal "connect / disconnect"!

Here's a photo of the "bench" test settings, in version 4.10.4.

And here is a photo of the "bench" test logs, in version 4.10.4

After MANY tests on the devices (which I thought was the problem), I decided to try to downgrade the server version, to version 4.9.36, which is the installation I had before the upgrade. (here is a record of the difficulty in finding previous versions, I only found the very old ones, 4.4...)

And to our surprise... Everything works normally again (MQTT and Tasmota).

Here's a photo of the "bench" test settings, in version 4.9.36.

And here is a photo of the installation of version 4.9.36, to prove that I'm not lying lol.

I have no problem maintaining version 4.9.36, and as I don't have any other device other than Tasmota to connect via MQTT, I understand that the problem could be with these devices.
As I said, everything has always worked well until then...

Did anything change about the MQTT broker compatibility version between versions 4.9.36 and 4.10.4??

In the end, I could just stay in the old version, but I like Comfortclick and IoT devices, so I leave a topic about it for the thousands of users of both who may be looking for some support about it.

Thank you team, and hugs to everyone!

Hey,

Has anyone played with Ezviz devices? I have H8 Pro for testing. I would like to use it in bOS too. I activated the RTSP stream on it but cant get any stream to play in bOS. It doesn't have ONVIF sadly but it has PTZ support. It's also supported by amazon and google home. I think it would be possible to use it with Hikvision NVR as port 8000 should also work on it.

RTSP link should be on it: rtsp://%u:%p@%ip:554/1 or /2 for lower video quality.

Any plans to integrate a driver for it @CC support? 

Hello,

Just looked at the last webinar video as I couldn't join. Very nice explanation and product discoveries.

I've seen that the https://jsoneditoronline.org/ tool is used to identify the parser. If the tool is nice, I found some time ago a very handy one, avoiding errors since as it identifies the exact expression for you, by just selecting the data you are looking for in the right hand window. The link is : JSON Path Finder.

As it saved me quite some time in the past, I thought it might be useful to others, thus sharing here.

Here an exemple with a blebox API expression. Just do not copy the "x." in the expression to get the correct one to past in CC.

Regards

Hello,

I get the following error:

Devices : 07/04/2023 20:02:50 : Error : Devices\KNX\Zentral\Wetterstation\Dämmerung : PropertyChanged Error References. Object reference not set to an instance of an object. at ComfortClick.Tasks.TaskTriggers.IfTrigger.OnPropertyChanged (System.String deviceName, System.String propertyName, System.Object value) 0x0003a in <018cf2e87d74455f87f7a657f2cf0c78>:0
at BOSCommon.References.ValueReference.ObjectValueChanged (System.String path, System.String propertyName, System.Object value) 0x00020 in <9cf46083622746b19c87ec03af0965e6>:0
at BOSCommon.Node.Attributes.NodeValueData.ObjectValueChanged (System.Object value) 0x00045 in <9cf46083622746b19c87ec03af0965e6>:0

Unfortunately I have no idea where this might come from. The object that seems to cause the problem is coming from the weather station - nightly twilight.

Any idea what might cause the error?

Kind regards

What do you use to control floor heating? I bought a

R4DCB08 8-channel RS485 DS18B20 Sensor Board MODBUS RTU, but the temperature value every now and then drop down to 0°C and I don´t know why. And for the valves DANFOSS ‑ Z‑Wave Hydronic Controller HC5, didn´t get that one to work either. So I am looking för a better solusion.