MyController.org - The Open Source Controller for MySensors.org
I would like to introduce MyController.org to the Open Source World
Still incomplete documents. I'm working on it. We will have complete documents soon.
Document ready: Document Page

Source: https://github.com/mycontroller-org/mycontroller
Demo Link: http://demo.mycontroller.org (Authentication: admin/admin)

To know about new releases visit/watch: http://forum.mysensors.org/topic/2058/releases

Build download location

New features:

• Supports MySensors 2.0.0
• Added new dashboard widgets
  • Custom buttons
  • Custom widget
  • Heatmap charts
  • Groups
  • Display image file
• Rooms detail (sensors based on rooms)
• Topology graph
  • Displays real time connection about things as topology graph
  • Displays how things connected in MyController database
  • Gives quick view about resource status and details with color indication
• New network support
  • Sparkfun - Will do poll https://data.sparkfun.com and storing as local sensors. Now you can perform actions based on this sensors data.
• Send raw message support
• Alarms renamed as Rules with new feature support.
  • Script based condition test
  • Multiple conditions support
• Timer supports multiple Operations
• Scripts support
  • Comes with Java Script, Groovy support
  • We can add Python and Ruby support by adding a jar file
• Added About page to know about MyController
• Added list available Script Engines page
• Added support to add custom style sheet, js file and angular js custom controller for Custom widget
• Template supports for Email and Custom widget
• Variables repository to use it in Scripts and in templates
• UID Tags can refer Sensor variable with unique name. used in scripts
• Send data to External servers, supports for Emoncms.org, Influxdb, Sparkfun[phant.io]
• Node registration support
• Email supports for STARTTLS
• MQTT broker control moved to GUI. Now with out stopping MyController you can enable/disable MQTT broker
• MQTT broker supports for authentication and topics level control for per user
• Added encryption to store user's password in database
• Sensor variable's unit, metrics type are editable. Also can configure graph settings for each Sensor variable
• Offset support #209
• Sensor widgets in order #220
• Rules, Timer, Operations clone option in GUI #201
• Test Email settings #192
• More dashboard layouts #164
• Optional main menu #163
• Automation geolocation #143
• locale support. new languages added (https://transifex.com/mycontrollerorg/)[see here]
• and many more

Changes:

• Units removed from user control. Still user can select Units for each resource.

List requests resolved

Commit changes from last release

How to upgrade from 0.0.3-alpha1 to 0.0.3.Alpha2

Note: Upgrade supports from 0.0.3-alpha1. Older than this release will not support for upgrade.

Before moving to 0.0.3.Alpha2 version,

• Take a backup (1)
• Stop 0.0.3-alpha1 server
• Extract 0.0.3.Alpha2
• Restore backup from (1)

Steps to take backup:

• Navigate to Settings -> Backup.

• Click on Settings. add location where you want to keep backup files. save
  

• Click on Run backup
  

Steps to restore:

• after backup completed successfully. Stop MyController from command line
• Now extract MyController 0.0.3.Alpha2 version on different location.
• Start new version of MyController
• Configure backed up file location on our new installation
• Now old backup file will be listing in our new installation
• Click on the file and run restore in action
  
• after successful restore change mycontroller/conf/mycontroller.properties manually compare to latest version
• start the server manually from command line.
• After successful migration compare and change your mycontroller/conf/mycontroller.properties file with latest file.

Enjoy

Do not forget to file issues on https://github.com/mycontroller-org/mycontroller/issues

Thank you for your support

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

Hello everyone, MyController 0.0.3-alpha1 is almost ready to release. As it has huge changes we want beta testers before release.

Changes summary:

• brand new Enterprise level GUI
• Supports multiple gateways
• Feature added with timers (supports active time, send payload with delay, etc.,)
• Add simple timer support
• user friendly logs display and filter
• user friendly action board
• brand new dashboard (supports multiple dashboards)
• Supports groups (scene control)
• role based authentication (share particular resource to user)
• and many more

Currently I'm working on documentation. Kindly let me know if you are interested to test.

• Download page
• Release notes
• Kindly report issues on GitHub issues page
• If you have question post it on this forum

0.0.3.Final release almost ready. We need pre-release test volunteers.

you can find SNAPSHOT version here

If you face any issues kindly report it on GitHub Issues page

• Issues fixed on this release
• Notable features added on this release,
  • SmartSleep node support
  • Native ESP8266 node support via https://github.com/mycontroller-org/MyControllerDevice
  • Raspberry PI device support via https://github.com/mycontroller-org/mcagent-rpi
  • Offline Heap message queue,
  • New database support added. MySql, Postgres, MariaDB
  • Etc.,

Happy testing

Just sharing my experience with MY_RFM69_MODEM_CONFIGURATION

IMPORTANT: We should not use brockets() when defining MY_RFM69_MODEM_CONFIGURATION,

Wrong way: #define MY_RFM69_MODEM_CONFIGURATION (RFM69_FSK_BR55_5_FD50)

Right way: #define MY_RFM69_MODEM_CONFIGURATION RFM69_FSK_BR55_5_FD50

Why? Check this, actually configuration values are defined as an array.

@prakhar-birla Yes, I am using in my house. I see a good range between concrete walls.
I was using NRF24L01+ Chinese version and was facing range issue. I used to have Gateway for each floor.
But now only single gateway with RFM69HW.

I have replaced RFM69HW with NRF24L01+ couple of weeks ago. I am just experimenting with coverage with RFM69HW. So far I do not face any issue.

The container image will be super easy to distribute.
It contains all its dependencies in it. "no more not working in my environment philosophy".
it is super lightweight compared to VM.

I would like to point that MyController.org has a docker image.
Version 1.x is managed by a community member: (available for x86_64 Linux arch): https://hub.docker.com/r/cdrocker/mycontroller

Version 2.0 is in the development phase and natively supports the container.
Supports for Linux x86_64, arm6, arm7, and arm64

# version 2.0
# run with default configuration
docker run  -d --name mycontroller \
    -p 8080:8080 \
    quay.io/mycontroller-org/all-in-one:master

Note: V2.0 is in the development stage, which means not ready for production. If you need metrics support install external influxdb(2.x).

@qobouky You are correct, the Binary type sensors should be visible here.
I just revisited your sketch and I found a conflict on the allocated sensors id

#define CHILD_ID_HUM 0
#define CHILD_ID_TEMP 1
#define CHILD_ID_CO2 2

#define NUMBER_OF_RELAYS 3 // Total number of attached relays
void presentation()  {
present(CHILD_ID_HUM, S_HUM);
present(CHILD_ID_TEMP, S_TEMP);
present(CHILD_ID_CO2, S_AIR_QUALITY);

 for (int sensor=1, pin=RELAY_PIN; sensor<=NUMBER_OF_RELAYS; sensor++, pin++) {
    // Register all sensors to gw (they will be created as child devices)
    present(sensor, S_BINARY);
  }
}

your relay sensor id should start from 3 or above.
I do not see the use of pin=RELAY_PIN.
You can present the status of your relay's, that can create V_STATUS on MyController

example:

#define RELAY_SENSOR 3 // Relay sensor starts at 3

void presentation()  {
....
MyMessage relayMsg(RELAY_SENSOR, V_STATUS);
for (int sensor=RELAY_SENSOR; sensor < (RELAY_SENSOR + NUMBER_OF_RELAYS); sensor++) {
    // Register all sensors to gw (they will be created as child devices)
    present(sensor, S_BINARY);
    relayMsg.sensor = sensor;
    send(relayMsg.set(loadState(sensor))); // current status of the relay
  }
}

NOTE: You have to update your relay code on setup and in receive too

@RagoTube looks like we need a gateway in a sensor network and with the help of gateway node-node communication can happen. The beauty of MySensors gateway is, you can use your gateway as a node.
I just updated my example shown here. Now the display node is a gateway node.

@RagoTube
Note: I didn't test this code. I believe it should work.

Sender node

#define MY_DEBUG
#define MY_RADIO_RF24
#define MY_NODE_ID 21

#define DISPLAY_NODE_ID 0

#define TEMPERATURE_SENSOR_ID 0

#include "MySensors.h"

// triggering interval
static const uint32_t trigger_ms = 10000; // 10 seconds

uint32_t lastTrigger = 0;
MyMessage msgGeneral(TEMPERATURE_SENSOR_ID, V_TEMP);

void setup() {
}

void presentation() {
  sendSketchInfo("Temperature node 1", "1.0");
  present(TEMPERATURE_SENSOR_ID, S_TEMP, "Temperature");
}

void loop() {
  if (millis() - lastTrigger > trigger_ms) {
    lastTrigger = millis();
    // set destination address
    msgGeneral.setDestination(DISPLAY_NODE_ID);
    
    // get temperature from your temperature sensor
    float lastTemperature = 0.0; // update from your sensor

    // send message to display node
    send(msgGeneral.set(lastTemperature));
  }
}

Display node (Gateway node)

#define MY_DEBUG
#define MY_RADIO_RF24
#define MY_GATEWAY_SERIAL

#define TEMPERATURE_SENSOR_ID 0
#define TEMPERATURE_NODE_ID 21

#include "MySensors.h"

float lastTemperature = 0.0;

void presentation() {
  sendSketchInfo("Display node / Gateway", "1.0");
}

void setup() {
}

void loop() {
}

void updateDisplay() {
  // update your display with "lastTemperature"
}

void receive(const MyMessage &message) {
  if (message.sender == TEMPERATURE_NODE_ID) { // message from temperature node
    if (message.sensor == TEMPERATURE_SENSOR_ID && message.type == V_TEMP) { // message from temperature sensor
      lastTemperature = message.getFloat();
      updateDisplay(); // update display
    }
  }
}

@RagoTube examples are there in,

• https://github.com/mysensors/MySensors/tree/development/examples
• https://github.com/mysensors/MySensorsArduinoExamples

The following sketch can help you to get your setup,
https://github.com/mysensors/MySensors/blob/development/examples/Node2Node/Node2Node.ino

@qobouky to get V_STATUS, you can do it two ways

1. (added automatically in MyController) Send the current status of the relays on your presentation block in your MySensors sketch
2. (add manually in MyController) - you can see S_BINARY sensors in MyController on this node. You can add a V_STATUS variable on each S_BINARY sensor in MyController

You will get a control option for your relays.

@qobouky seems you have problem with MyController and serial port communication. I do not see the node 0 too (gateway node).
can you check the MyController log file, is there any error? Also check the baud rate and port number of your serial device.

@qobouky your attachments are not available. can you please add it again?
do not you get your node by running discover on MyController?

@Yveaux said in serial, Ethernet to MQTT:

Of course, but MySensors MQTT gateway runs just as fine when connected over cabled ethernet, as when connected over wifi

I do not know that
Now on this tool, I do not see much benefit from ethernet to MQTT
Still, it is good from serial to MQTT.

@Yveaux Some people keep wants to use serial or ethernet for security reason. They do not want to use WiFi.
But still, they can enjoy the benefits of MQTT

• experiment different controllers via MQTT
• can have the serial gateways on the different places and connected to a controller (everything connected via MQTT)

Hi,

I have developed a new MQTT bridge to convert from serial, ethernet to mqtt.
Supports for MySensors.
You can have more than one serial ports and/or ethernet connections.
If you are interested in, https://github.com/mycontroller-org/2mqtt
Thanks!