@sstuhlmann check your Chrome dev tools betwork tab to see what REST API requests for data points are actually issued.

If it is like you say you can stop the query running until you retrieve your device name by using a ng-if e.g.

<ma-point-query ng-if="$ctrl.devName">

Alternatively do something like this, so that if devName is undefined it queries for the deviceName being null instead (which should return 0 results)

<ma-point-query query="{deviceName:$ctrl.devName || null}">

Although what I suspect is actually happening is that the query is not exact, I think that type of query is actually a fuzzy query, it will search for deviceName LIKE %devName% in the SQL database.

Try this -

<ma-point-query query="{deviceName:$ctrl.devName, $exact: true}">

Yes, I am writing completely independent modules with definition java files. I'm currently just running development and testing locally. Once I build my new module (which lists module-parent as its parent), I just drop the zip onto my MangoES. I'm currently working on two modules. One is a better and more standardized deviceConfig/templating module. And the second is a graphical gauges one which wraps ma-gauge and uses the DP tags to dynamically load different layouts. Like so:

0_1540483102020_b5380d8c-f55c-4e61-95ac-4611870ee1ae-image.png

The injector will be great. Should work out for me nicely.

At some point I will look at publishing my modules to the store. But they aren't quite ready for prime time.

Yes, you could use the USB utility to move the whole update bundle zip into your /opt/mango directory if named as I suggested previously.

It looks like your DNS resolved the correct IP, but you didn't (or couldn't) get a response. You could try https://store.infiniteautomation.com instead of http:// as your store.url in your env.properties file.

I would agree that the JSON store is probably your best bet at the moment. Store an object where each property is the XID of the data point for easy retrieval. We have also discussed adding some generic JSON data to each data point so that might be an option in the future.

Thanks!

Yes, it is fully realized (with few special exceptions in the system settings: you cannot import database schema version numbers). It is unlikely that data sources or points would change in such a way as to invalidate previous JSON. If there were a change, it would most likely be the addition of a property that would have a class default, so it could be foregone in old JSON without issue. We try to stay conscious of this so that people's backups do not get invalidated.