Hello.

I noticed that I have issue with updating to 4.10.9 from 4.9.40. When I try to connect to Jisgaw I got popup that I need update but update button is blank and without updating I cannot connect and no dowload config doesnt do anything it just close config program. Please help me to get around this I cannot reach most of my configs. 

Hello everyone,

I am currently trying to connect and control a Daikin VRV central air conditioning system via the DTA116A51 board using the Modbus protocol. However, I am unable to read or write 3 or 8 bits... from the 16-bit Holding Register or Input Register to bOS. Do you have any solutions to this problem? Please help me.

D3NET-Modbus+Communication+adaptor_Function....pdf

Hello!

I've recently testing out TiOC cameras from Dahua, where I need to use their TiOC API. I've tested some of the URLs on the browser, and with curl, and even though they work, I have a small problem with bOS.

The url itself is this one (just for now):

http://192.168.1.108/cgi-bin/coaxialControlIO.cgi?action=control&channel=1&info[0].Type=1&info[0].IO=1

On the browser, I just have to past the url, enter the username and password and that's it. Testing done.

With curl, as I have square brackets, either I use the --globoff option or I have to change the [ ] with %5B and %5D respectively. Otherwise the curl command gives error.

So, I'm trying to use this url on bOS and it simply doesn't work.

If I use the [ ] I don't get anything. If I use the %, it will conflict in the string editor, as %5... will expect the pointer. I've tried almost everything I can remember, 

I know some guy that will probably figure this out, as I know that he probably uses TiOC cameras...

Yes Jürgen, this message is for you :P

Help!

Best regards

Hello all,

Did someone do an integration of Huawei inverter with smartlogger Modbus TCP?

Thank you!

I set images for the buttons in the visualization. By default, the silhouette of the images is visible and they become black when turned on, this works everywhere.

I changed this to default to black. But there is a button where, when turned on, the silhouette appears as I wanted, and there is one where it does not change, it remains the same black.

Why is this so?

I am currently experiencing an issue where the Modbus TCP connection does not automatically reconnect after being disconnected. The bOS still shows the status as "true", but I have to manually enable and disable it to get it to work again. This error occurred after I updated the bOS server to version 4.10.8. Is there any way to fix this?

Hi, I wonder if there is a bug or delay or something in calculating the values with Conter Log. Why is ¨This month count'' showing 140,7 when ''Previous Month count'' and ''Total Value'' is 161,7 and 17,7?

161,7 - 17,7 = 144, not 140,7

If I use the last value in the Log which is 160,8 or the value at 23:00 it doesn't make sense either. 

Or am i missing something here?

Hello,

The new alert, doesn't assume any new paragraphs on e-mails. Instead, it just writes the text on the same sentence. It doesn't assume paragraphs on the e-mails, but it assumes of the push notification and on the log :/

I had to use html tag <br> to be able to have paragraphs on the e-mail body. Which in turn, sucks on the push notification as it shows as <br>

Best regards

Good afternoon,

We have a client demand and would need help regarding the possibility of implementation and whether we would necessarily need a license per user. Below is an outline of the implementations to be made for the evolution of the existing project/system. Attached is an idea of ​​the concepts.Informative concepts

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!