I started working on MyController version 2.x.
Existing repository renamed to mycontroller-v1-legacy.

Version 1.x: https://github.com/mycontroller-org/mycontroller-v1-legacy

Version 2.x: https://github.com/mycontroller-org/backend and https://github.com/mycontroller-org/console-web

Hello everyone,

MyController was born around August 2015. Currently, version 1.0.0 available for public and before 25, December 2017, version 1.1.0 will be available for the public.

• I see some performance issues with MyController when we have a number of sensors grow.
• We need end user-friendly GUI. I believe for now we have only admin friendly GUI.
• There is no mobile application.
• Supports more databases. H2DB, MySQL, MariaDB, PostgresSQL. To reduce complexity support only for one DB or maximum two databases.
• and more

To rectify all these issues, I am planning to build MyController 2.x from scratch. With the following technologies.

• Spring boot with Undertow GoLang
• Angular 4 front end ReactJS
• Ionic mobile application Reactive native
• Two type databases
  • RDBMS for sensor metadata In-Memory and MongoDB for data
  • InfluxDB for metrics
• backup/restore as CSV YAML or JSON file(except metrics data)

Still, I want to keep MyController's primary platform as Rasberry PI.

Kindly share your experience with influxDB and raspberry PI in the long run. Also, share your thoughts on this big move.

@Avamander Thanks for the pointer. Discourse needs more resources than NodeBB. We do not have that much budget.
So, for now, we do not have any plans to upgrade.

@DaTTcz For now direct battery support not available on Rules. However you can do it from script. I will update how to handle with script.

Kindly create a request on github page to support battery level on rules.

ALL these features are available on SNAPSHOT build

Enter your condition via script,

Steps:

• Create UID Tag for your node,
• Create script to check node battery level (script type: Condition)
• Create rule with this condition script
• Enjoy

Create UID Tag:

Add script:

Java Script to check battery level,

var myImports = new JavaImporter(java.io, java.lang, java.util, java.text);

with(myImports) {
  var mcResult = false; //By default this is false. When your condition meets change this to true
  var batteryLevel = mcApi.uidTag().getByUid("node1").resource.batteryLevel;
  if(batteryLevel >= 50){ // Your condition
     mcResult = true;
  }
}

Add rule:

@skywatch The error shown here is not related to the issue you are facing. This is error is not harmful.

Hello,
MyController 2.0 is in the development stage. I hope we can do a pre-release soon.
I do not want to limit MyController usage not only to the sensors world. can be used for another use case too.

Example:

• monitor stock market and act based on that
• monitor GitHub issues, JIRA issues act based on that
• Monitor an application on a computer
• We have many use cases...

The names should be generic and can be adaptable for all use cases.
So we need a better common name for the sensor and variable.

Current approach (In Version 1.x): Gateway >> Node >> Sensor >> Variable

Sensor:

• The sensor will be renamed as element
• I need better naming here if this is not looking good

Variable:

• We cannot use the name variable, it is more confusing.
• The Variable will be renamed as field (inputs are welcome)

Please respond back with your suggestions

between, Current work of MyController 2.0 deployed at https://demo-v2.mycontroller.org (Username:admin Password: admin)

@seant

var pingDistance = tankDistanceSensor.value; //Water tank level percent

You have to use parseInt(tankDistanceSensor.value), Sensor variable always have String value.
var pingDistance = parseInt(tankDistanceSensor.value); //Water tank level percent

//THESE 2 LINES DO NOT SEEM TO SET THE VALUES
tankLitresSensor.setValue(litres);
tankPercentageSensor.setValue(percentage);

After these two lines add the following lines,

  mcApi.sensor().sendPayload(tankLitresSensor); 
  mcApi.sensor().sendPayload(tankPercentageSensor); 

For now, there is no option to delete a sensor variable alone from the GUI. So I'm providing an option to delete a sensor variable from a script.

Note: This API available from 1.4.0.Final version.

• Now get SensorVariable id from Sensors page. Resources >> Sensors >> Click on view details,
  
  Now click on edit of sensor variable
  

On the URL you can see sensor variable id, This is id is important note it for your target sensor variable

Add the following script on your controller,
Extension: JavaScript
Type: Operation

var myImports = new JavaImporter(java.io, java.lang, java.util);

with(myImports) {
  // pass sensor variable as bindings, example: { id: 99 }
  mcApi.sensor().deleteSensorVariable(id);
}

Execute the script as Run now (select the script and in Actions you can see Run now),
Pass the sensor variable id as bindings, here it is { id: 99 },

Click on Run. All done. Now your Sensor variable removed from MyController.

@skywatch Thanks for the logs. Can you edit and save again gateway2 and see the behavior?

@tag Thank you so much for your continued support!

when you mention influx are you planning to use the complete "TICK" stack which influxDB is part off?

Yes, I am planning to move the metrics completely to influxDB. RDBMS not good for time series data.

@JeeLet said in Grafana install:

a new hardware base, maybe an Odroid-N2 !?

I have not owned Odroid-N2. But it should work

@JeeLet I missed this thread somehow

I don't understand the difference between StorageDB and MetricDB

https://v2.mycontroller.org/docs/overview/architecture/#storage-database

you say "You can also use influx 2.x. MyC supports influx 2.x"?

Yes, influx 2.x supported, more configuration details on https://v2.mycontroller.org/docs/installation/advanced-installation/backend-configuration/#influxdb

on a next new installation I switch to the influxDB-2 version I don't have anything to modify in mycontroller ?? .... I may try ??

You have to update the configuration file as mentioned on the above link

For the last test with grafana, the "mc_gauge_float_data" values work but not the "mc_binary_data" numbers
(maybe I'm wrong in the config)

binary data is in the form of true or false.

@JeeLet You can go with influx 2.x as well. MyC supports for influx 2.x

@JeeLet for now MyC do not delete influx data, when you remove your sensors from MyC. But it is required. I will add this feature soon if possible.

@JeeLet some special cases you need 2mqtt. For example you want to share your USB GW for MyC and other software (via mqtt). If you are using your USB GW only with MyC. 2mqtt is not required.

2mqtt creates a mqtt communication to your USB GW

@JeeLet can you please explain the requirement? It will be easier to guide.

@JeeLet Happy New Year!!
Great! Finally you got it.

@JeeLet

Gw and stick to the controller, it does not do much, it relays, it is an intermediary.
Couldn't we use the Gateway-Usb to monitor the nodes ?
of their values ? of their states ?

It is possible to fetch node/sensor values. But it is ok when you have few nodes. If your node network grows, this eats lots of your RF bandwidth. IMO, it is unnecessary to poll the values. We have a push mechanism (node sends data to MyC) and in this situation, It is not a good idea to implement pull mechanism as well (MyC asks data from from each node).

@JeeLet MyController v2 operates like event based. It means it receives the data from the node or whatever and updates into the database with the timestamp of the data. On a restart of MyC server the data will be loaded again from database. So no change on the data/value, until it receives new value from that node.

The node down status maintained by MyC. If there is no data/heartbeat received from a node for a specified time. MyC assumes that the node is down and marked as down.

@JeeLet It is not a ghost value. You can note the timestamp (Last Seen) the value received 20 hours ago after that data not received. So it is a 20 hours ago data.
Please let me know if it is not clear