you can search for 'BBMD' in this forum. There should be enough articles to get you started.

@nathanrona
do a search on upgrade or re-install or have a look at the documentation website. I saw an article not that long ago that helped me on a similar situation.

Victor.

@ralf
I want to give you a comparison from the point of view of Building Automation Systems (BAS) that will have to deal with such massive amount of points.
Generally, the BAS will have network controller which is similar to a MangoES that polls various devices then either do something with them or perform data-sharing between network controllers.
To accommodate 32000 points and maintain acceptable performance, 2000 physical/software points from all these devices is generally the limit i will put on each network controller.
So, i will need at least 16 network controllers. So that will be 16 CPUs (or cores) (one per network controllers, they could be ARM or similar, keep in mind, these network controllers CPU are much slower than a mid-range desktop CUP). Each network controller may have 2GB RAM, so there will be 32 GB RAM required.
In addition, in system this big, there will be a separate Server-Class PC to serve up all the webpages to the end-users. This server-class PC will at least have 8-core and 16GB RAM. All up, there are at least 24 cores CPUs and 48GB RAM required to run this system.
Looking at your server spec, it is under-powered.

I hope the above makes sense.

Hi,
I have built a watchlist with multiple tags selection options.
As shown below, when I selected multiple items with long names, the two tags display areas overlap which makes it illegible.

I know in dashboard designer, i can set the item list display to go 'table' view which will avoid such issue.

Can i ask if this can be addressed in the standard watchlist object? Or Have I miss-configured any settings?

thanks in advance!

@ralf
Right. I understand.
the only way is one Data Source for each BACnet/IP-PLC then. Just have a go and put in all 150. What is the worse can happen? :)

@joelhaggar @Jared-Wiltshire
Hi, Joel and Jared
Thank you for replying.
I want to chime in with my 2-cents here:
Since Mango OS is going to be used in many IOT devices which can become part of cloud-based SAAS offering.
I notice a lot of SAAS offering touting their integration to tons of 3rd party integration. For example, Airtable/Smartsheets (they are not IOT devices but they are cloud-based SAAS products) have many integration to different data sources. It is a great selling point for any SAAS products because it enhance its flexibility and possibility of being deployed for different purposes.
I understand your team can not do everything all at the same time. However, in the case of Twilio integration in Mango, I think it is a mistake to deprecate rather than make it work. Not many people can write their own code in Mango or want to set up email server to forward an email to another SMS service. This creates too much friction between the user and Mango. Twilio is a house-hold name in its space. This is a case where 'built-it, it will come' apply when people see Mango can work with Twilio.
We can indeed provide feedback to Mango to say we want this feature, however, when someone says he wants it, it normally means he wants now, not when Mango gets around to do it and no one knows how long that is going to be.
I think from the outside, this just looks like Mango has put Twilio for V4.0 into the too-hard basket. I know Mango has many reasons not to pursue the Twilio integration for V4.0 but my concern is the same reasons can be used for other integrations already in MangoOS to be deprecated in the future.
I hope Mango can stick to its promise of providing 'low-code' or 'no-code' programming environment for small integrator or less skilful people like us rather than an environment where coding in JavaScript/AngularJS becomes unavoidable.

Thank you.

Victor

Hi,
I noticed there no 'Save As' function for the above two UIs. I know I can copy/paste the underlining codes between
pages. But I think it will improve productivity and reduce errors by having such function.

thanks.

Hi,
In the legacy UI, the BACnet publisher can automatically assign BACnet Object Instance ID, see below:

However, in the modern UI, the Instance ID has to be manually assigned, see below:

Can i suggest following features to be added:
1-automatic assignment of Instance ID
2-automatic assignment of Instance ID from last ID when additional same type of points are added. for example, if AV1 was added previously, then the next AV to be added needs to have AV2 assigned to it.
3-CSV download/upload feature to facilitate mass edit.
4-COV settings for each analog point.

thanks.

Hi, Guys
I figured it out the issue (at least for me).
It is to do with the broadcast address. For me, I needed to change it from 255.255.255.255 to 192.168.69.255 (which is my subnet host ip range).
after doing that, all is well.

@techalton - give it try.

thanks.

@robmalone
I think there is a sample dashboard called 'Daily comparison chart' inside Mango
that will help you out.
I have created a dashboard similar to what you want for daily/monthly/yearly comparison on the same kWh point.
Below is where you can find the aforementioned sample dashboard.
Hope this helps.

@cmusselm
that is a good outcome! Thanks for the update.

@till
give me suggestion a try. just add one.

@joelhaggar
the video link is not working.

@till
you can export the event handlers in below window

here is what the json file looks like, you can just add/modify, then re-import it, I think that should work.

@joelhaggar @Jared-Wiltshire
Hi, Joel and Jared
Thank you for replying.
I want to chime in with my 2-cents here:
Since Mango OS is going to be used in many IOT devices which can become part of cloud-based SAAS offering.
I notice a lot of SAAS offering touting their integration to tons of 3rd party integration. For example, Airtable/Smartsheets (they are not IOT devices but they are cloud-based SAAS products) have many integration to different data sources. It is a great selling point for any SAAS products because it enhance its flexibility and possibility of being deployed for different purposes.
I understand your team can not do everything all at the same time. However, in the case of Twilio integration in Mango, I think it is a mistake to deprecate rather than make it work. Not many people can write their own code in Mango or want to set up email server to forward an email to another SMS service. This creates too much friction between the user and Mango. Twilio is a house-hold name in its space. This is a case where 'built-it, it will come' apply when people see Mango can work with Twilio.
We can indeed provide feedback to Mango to say we want this feature, however, when someone says he wants it, it normally means he wants now, not when Mango gets around to do it and no one knows how long that is going to be.
I think from the outside, this just looks like Mango has put Twilio for V4.0 into the too-hard basket. I know Mango has many reasons not to pursue the Twilio integration for V4.0 but my concern is the same reasons can be used for other integrations already in MangoOS to be deprecated in the future.
I hope Mango can stick to its promise of providing 'low-code' or 'no-code' programming environment for small integrator or less skilful people like us rather than an environment where coding in JavaScript/AngularJS becomes unavoidable.

Thank you.

Victor

@tungthanh500
yes, there are buttons on the top right hand corner of the page that you can use to create folders and files.

@tungthanh500
you need to go under the 'Admin'/File stores'
see below,

@tungthanh500
did you get stuck on the module file path? If you did, that could be due to that is not the right path for V4.
try replacing 'v2' with 'latest' in the path name.

@joelhaggar
I am using v3.7.7 so I am out of luck there with the setttings.

@joelhaggar @CraigWeb @MattFox
Thank you guys for the replies.
After spending more time on Mango V3.7.7 and adding/removing things , I think the tags display need to be further fined-tune in V4.
For example, in the below screenshot for the Meta Data Source, when it comes to display the external context points, it shows the tags which in this case it takes up a lot of real estate for 1 point. For my use case, I will need to include over a dozen points which means the screen will be taken over by the tags and the script screen will be way down and it will need scrolling up and down for reference.
I think there needs to be a way to turn off the 'Tags' column display all together where its content is not necessarily required. The solution available in V4 by only displaying some tags will not help in situation like this since some tags content can be really long.