Hi Ralf

Untill the next beta is released you can use Firefox which does not have the bug.

Hi Ralf

A v3 licence will not be valid for v4. Going from v4-beta to v4 should be seamless.

Ok, I found a solution!

The old thread pool settings:

0_1578997281515_ad7a49b3-2b49-4a5b-bdcf-9577fd404f36-image.png

Settings now:

0_1578997216570_5c7fd5ef-9f5b-478a-8084-3f4391eea992-image.png

The setup with more than 120 BACnet-Devices needs a lot of threads, so the ptp-sync hasn't enough and failed.

Now it needs more CPU (20-45%) but it is working, that is fine.

@ralf said in SQL Data Source Insert and Update rows:

INSERT INTO table_xz (
IDNr, StartSum, StartTemp, ValveNr, LineNr, StartTime)
VALUES (?,?,?,'KS0717','B',NOW())

I know you can extend the insert query by just adding another batch of values after in brackets.

INSERT INTO table_xz ( IDNr, StartSum, StartTemp, ValveNr, LineNr, StartTime) VALUES (?,?,?,'KS0717','B',NOW()),(?,?,?,'KS0717','B',NOW())

You may need to insert the actual values though.

Hi Jared,

no, the system works fine.

All other publisher events are only shown once ...

Thanks!

@ralf
it is so nice to have your feedback. That is a very impressive points count.
I am glad it works out for you. I would say the SSD definitely helped a lot as well.
The spec of your server is not too hard to obtain anyway which is good.
Did you use the Windows Service (auto startup) component mentioned in Mango's help instructions?
I am curious how you tested it with a second PC before you upgraded the system.
I am guessing that you ran both PCs at the same time since all your DSs are IP based.

You should write a user-case for the forum 'Stories' section as well. that will be nice.

The best advice I can give is that the drop-down on the dashboard designer is filterable. Just start typing your pages name.

Hi Ralf,

We have explored adding the ability to set event detectors to not raise the event more than once in some amount of time, but that feature was not merged in at the time so hasn't become part of Mango yet.

I think what you're requesting would be something like that, but for data source events, which is a good idea if it is a good idea to do it for event detectors.

Thanks for the suggestion!

Hi Ralf,

You are right! Thanks for bringing this to our attention!

Edit: Posted a little fast... Here's the git issue: https://github.com/infiniteautomation/ma-dashboards/issues/299

You could work around this by using a JSON or CSV import, or using the old UI.

@Ralf I would suggest that you read the markup that Phillip posted and try and understand what it is doing, then try to adapt it to suit your needs. We are here to help you, not to do it for you.

This is probably only a display issue. I would guess above that on the page it is showing the value for hour 23 as the current value, and that if you chart it for the day you will see the values in the chart. Thanks for bringing this to our attention!

Thanks for sharing the resource that helped you!

This thread has some information on updating Java that could be useful if Mango is being run on a lower privileged user at port 80: https://forum.infiniteautomation.com/topic/2678/java-update-encouraged

@ralf said in iOS 12.2 Problem:

I don't understand why this bug only exist with iOS.

iOS / Safari don't exactly have a great track record when it comes to web standards.

Unfortunately this does seem to be a bug in Safari, see here - https://stackoverflow.com/questions/37898048/websocket-network-error-osstatus-error-9807-invalid-certificate-chain

Since the message there says "Invalid certificate chain" it might be worth checking your certificate using a site like https://www.ssllabs.com/ssltest/

PS I would recommend you to try a different browser but I don't think it will make any difference as Apple in its infinite wisdom prohibits using anything than its own Safari browser engine on iOS, so Chrome on on iOS is a basically a skinned version of Safari.

That works, thank you!

Thanks Jared, that is a great tip. That might solve a few things I have encountered.

Hi Ralf,

It means that for 26 points there was more data already on the receiving end than data on the publisher's side for the period checked. Usually this is caused by a point with interval logging on the publisher transmitting its realtime updates as opposed to logged events, then the receiver's default point logs all data if the receiver is configured to save real time data, and that amounts to an overcount. It can be possible other ways (disk getting full, importing extra data at receiver, etc), but that's what I'd guess caused it here. The solution to prevent it if that is the cause would be to change your publisher's publish event to logged data instead of updates.

@ralf Yeah like I said I'll make it use the user's locale. I wont make it possible to define number formats in the user settings however if this is what you meant.