Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.

Turns out that the SEND TEST EMAIL doesn't send a test email using the values that you just entered but using the values that are saved. So you cannot test before saving.

@mattfox Thanks Matt :). Nice to see some familiar faces here!

@terrypacker Cool that works. Removing both .h2 and .db was the key. I'll Thanks

@terrypacker said in Too much data for a datapoint: I shall give that a go, thanks.

Hi NinoK, if you create a new BACnet-Data-Source your local device IP (old system settings / BACnet local devices: 192.168.100.105:47808) should be the same as the Mango-Server has: [image: OGyIO0X.png] [image: 2U5o6hF.png] [image: e7qLbz4.png] If you create a new BACnet data point it should look like: [image: TCVMQMi.png] where the "Device instance number" is the given Device ID, here 5. If all BACnet-Devices are in the same IP-Range you don't need a BBMD. Be carful if you scan a large BACnet-Network with many devices and objects. It can take a long time and need server-resources. Better is to scan one ID.

@bhansen Modbus does not support discovery, so you need to know the slave address, register address, type and format to be able to map data points. This reference on the Mango site may help : http://docs-v4.mango-os.com/modbus-point-list-requirements

This one: https://forum.mango-os.com/topic/3551/data-sources-does-not-appear/13?_=1629414527624

@till That is correct. The value will be held in the cache. You can even set the data point to hold x number of values in the cache so there is some history there.

@hazel I am pretty confident one of your registers is being read as: NaN by Mango. I have opened a ticket to make this more robust but the current version of Mango does not have a simple way to determine what data point is causing this. You will need to start looking into what registers you are reading for numeric values that have out of range data.

@terrypacker thanks a lot, an example code is more than enough. I will look into the library in detail and see how to use it in the upcoming days. Thanks once again!