MyController.org
-
Just finished setting up MyController, so it runs besides domoticz, and NodeRed. Looks fine so far, but haven't had that much time to delve into MyController specifics yet.
Have set it up so that when ever I turn a light on / off in MyController, Domoticz also sees this (and of course the sensor network).
Plan was to try and use MyController for OTA firmware updates, and keep track of firmware versions in my network.
-
For some reason cannot seem to get it running.
Have installed the software and the server appears to start, but there is no web access and this is what I get when I check the log.
Have I setup something incorrect
Running on a PI
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/mycontroller/standalone/StartApp : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:792) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode) -
For some reason cannot seem to get it running.
Have installed the software and the server appears to start, but there is no web access and this is what I get when I check the log.
Have I setup something incorrect
Running on a PI
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/mycontroller/standalone/StartApp : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:792) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:482)java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode)@diggs said:
For some reason cannot seem to get it running.
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode)You should update your java version to 1.8 or later. For raspberry PI oracle java is recommended for MyController.
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
jdk-8u60-linux-arm32-vfp-hflt.tar.gz
@diggs hope this link will help you to update your java: http://www.rpiblog.com/2014/03/installing-oracle-jdk-8-on-raspberry-pi.html
-
Just finished setting up MyController, so it runs besides domoticz, and NodeRed. Looks fine so far, but haven't had that much time to delve into MyController specifics yet.
Have set it up so that when ever I turn a light on / off in MyController, Domoticz also sees this (and of course the sensor network).
Plan was to try and use MyController for OTA firmware updates, and keep track of firmware versions in my network.
@tbowmo said:
Just finished setting up MyController, so it runs besides domoticz, and NodeRed. Looks fine so far, but haven't had that much time to delve into MyController specifics yet.
Have set it up so that when ever I turn a light on / off in MyController, Domoticz also sees this (and of course the sensor network).
Plan was to try and use MyController for OTA firmware updates, and keep track of firmware versions in my network.
@tbowmo Nice! you can give try for other features also which is available in MyController ;)
Alarm, Timer, Forward Payload, UID, etc., -
@diggs said:
For some reason cannot seem to get it running.
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) Client VM (build 24.0-b56, mixed mode)You should update your java version to 1.8 or later. For raspberry PI oracle java is recommended for MyController.
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
jdk-8u60-linux-arm32-vfp-hflt.tar.gz
@diggs hope this link will help you to update your java: http://www.rpiblog.com/2014/03/installing-oracle-jdk-8-on-raspberry-pi.html
@jkandasa Thanks for that.
The latest Java version has go me going as far as server access goes, but I am having issues opening the serial port it seems.
I am trying to run in parallel with Domoticz, but I maybe having an issue trying to access the same port I am guess.
Suggestions on how to get around that?
2015-09-27 15:45:16,568 ERROR [main] [org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl:68] Failed to load serial port, java.io.IOException: Unable to open the serial port/device. (Error #2) at com.pi4j.jni.Serial.open(Native Method) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:151) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:242) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.initialize(SerialPortPi4jImpl.java:61) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.<init>(SerialPortPi4jImpl.java:40) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.StartApp.startServices(StartApp.java:217) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.StartApp.main(StartApp.java:78) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] 2015-09-27 15:45:16,646 INFO [main] [org.mycontroller.standalone.db.TimerUtils:144] Updated Time:[SunRise:Sun Sep 27 10:36:00 AEST 2015, SunSet:Sun Sep 27 22:41:00 AEST 2015], City:[latitude:11.2333, longit$ [Sun Sep 27 15:45:21 AEST 2015] TJWS httpd 0.0.0.0 - [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,localport=8443]] is listening. -
@jkandasa Thanks for that.
The latest Java version has go me going as far as server access goes, but I am having issues opening the serial port it seems.
I am trying to run in parallel with Domoticz, but I maybe having an issue trying to access the same port I am guess.
Suggestions on how to get around that?
2015-09-27 15:45:16,568 ERROR [main] [org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl:68] Failed to load serial port, java.io.IOException: Unable to open the serial port/device. (Error #2) at com.pi4j.jni.Serial.open(Native Method) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:151) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at com.pi4j.io.serial.impl.SerialImpl.open(SerialImpl.java:242) ~[mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.initialize(SerialPortPi4jImpl.java:61) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.gateway.serialport.SerialPortPi4jImpl.<init>(SerialPortPi4jImpl.java:40) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.StartApp.startServices(StartApp.java:217) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] at org.mycontroller.standalone.StartApp.main(StartApp.java:78) [mycontroller-standalone-0.0.2-alpha4-single.jar:na] 2015-09-27 15:45:16,646 INFO [main] [org.mycontroller.standalone.db.TimerUtils:144] Updated Time:[SunRise:Sun Sep 27 10:36:00 AEST 2015, SunSet:Sun Sep 27 22:41:00 AEST 2015], City:[latitude:11.2333, longit$ [Sun Sep 27 15:45:21 AEST 2015] TJWS httpd 0.0.0.0 - [SSL: ServerSocket[addr=0.0.0.0/0.0.0.0,localport=8443]] is listening.@diggs said:
@jkandasa Thanks for that.
The latest Java version has go me going as far as server access goes, but I am having issues opening the serial port it seems.
I am trying to run in parallel with Domoticz, but I maybe having an issue trying to access the same port I am guess.
Suggestions on how to get around that?
I guess you cannot share same port for two different applications. We may go with some third party tools to share serial port across applications. But, I do not have any experience on it.
In this case to run MyController server, stop MyController server and Domoticz controller, then start MyController server, it will work.
-
@diggs said:
@jkandasa Thanks for that.
The latest Java version has go me going as far as server access goes, but I am having issues opening the serial port it seems.
I am trying to run in parallel with Domoticz, but I maybe having an issue trying to access the same port I am guess.
Suggestions on how to get around that?
I guess you cannot share same port for two different applications. We may go with some third party tools to share serial port across applications. But, I do not have any experience on it.
In this case to run MyController server, stop MyController server and Domoticz controller, then start MyController server, it will work.
-
@jkandasa Thanks
Have now done all that. Stopped the Domoticz server, started Mycontroller. I get the webpage up now, but still no nodes showing up and for some reason nothing is being written to my logs the past few hours at all.
What can I look at?
-
- stop the server
- connect to your serial port and see if you get any response from gateway ( minicom/miniterm etc ... )
- If above work , check your config for correct serial ports settings.
- If above doesnt work not check your serial gateway
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
#======================================================================== # MySensors Gateway settings # Select Type of gateway will be used, Only one gateway will be used # Types -> serial, ethernet, mqtt #======================================================================== mcc.ethernet.gateway.type=serial #======================================================================== # MySensors Serial port settings # In this section select: Driver, port name and baud rate # Available drivers -> [pi4j, jssc, jserialcomm, auto] #======================================================================== mcc.serialport.driver.type=auto mcc.serialport.name=/dev/ttyACM0 mcc.serialport.baud.rate=115200 #======================================================================== # MySensors Ethernet Gateway settings # Update host name/ip and port number, Default: 192.168.178.6:5003 # Keep alive check frequency in seconds #======================================================================== mcc.ethernet.gateway.host=192.168.178.6 mcc.ethernet.gateway.port=5003 mcc.ethernet.gateway.keep.alive.frequency=60 #======================================================================== # MySensors MQTT Gateway settings # Update broker host name/ip and port number, Default: 192.168.178.6:1883 # Root topic name of broker # Note: MQTT_TRANSLATE_TYPES will be not supported # Disable MQTT_TRANSLATE_TYPES in your MQTT gateway #======================================================================== mcc.mqtt.gateway.broker.host=192.168.178.6 mcc.mqtt.gateway.broker.port=1883 mcc.mqtt.gateway.broker.root.topic=MyMQTT #======================================================================== # Database # Where do you want to keep your database. # It is highly recommended to take a backup of this db on upgrade. # Database: H2DB, location and name, example:/tmp/mycontroller #======================================================================== mcc.h2db.location=../conf/mycontroller #======================================================================== # Web files, will be located under ../www by default # For web used angularjs #======================================================================== www.file.location=../www/ #======================================================================== # Web Application server configuration # bind.address - interface to bind. 0.0.0.0 - all available interfaces # You can use either http or https, enable.https - https is enabled # if https is enabled specify keystore file details # It is highly recommended to use https also change default keystore file #======================================================================== bind.address=0.0.0.0 enable.https=true http.port=8443 ssl.keystore.file=../conf/keystore.jks ssl.keystore.password=password ssl.keystore.type=JKS #logger configuration - logback.xml -
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
#======================================================================== # MySensors Gateway settings # Select Type of gateway will be used, Only one gateway will be used # Types -> serial, ethernet, mqtt #======================================================================== mcc.ethernet.gateway.type=serial #======================================================================== # MySensors Serial port settings # In this section select: Driver, port name and baud rate # Available drivers -> [pi4j, jssc, jserialcomm, auto] #======================================================================== mcc.serialport.driver.type=auto mcc.serialport.name=/dev/ttyACM0 mcc.serialport.baud.rate=115200 #======================================================================== # MySensors Ethernet Gateway settings # Update host name/ip and port number, Default: 192.168.178.6:5003 # Keep alive check frequency in seconds #======================================================================== mcc.ethernet.gateway.host=192.168.178.6 mcc.ethernet.gateway.port=5003 mcc.ethernet.gateway.keep.alive.frequency=60 #======================================================================== # MySensors MQTT Gateway settings # Update broker host name/ip and port number, Default: 192.168.178.6:1883 # Root topic name of broker # Note: MQTT_TRANSLATE_TYPES will be not supported # Disable MQTT_TRANSLATE_TYPES in your MQTT gateway #======================================================================== mcc.mqtt.gateway.broker.host=192.168.178.6 mcc.mqtt.gateway.broker.port=1883 mcc.mqtt.gateway.broker.root.topic=MyMQTT #======================================================================== # Database # Where do you want to keep your database. # It is highly recommended to take a backup of this db on upgrade. # Database: H2DB, location and name, example:/tmp/mycontroller #======================================================================== mcc.h2db.location=../conf/mycontroller #======================================================================== # Web files, will be located under ../www by default # For web used angularjs #======================================================================== www.file.location=../www/ #======================================================================== # Web Application server configuration # bind.address - interface to bind. 0.0.0.0 - all available interfaces # You can use either http or https, enable.https - https is enabled # if https is enabled specify keystore file details # It is highly recommended to use https also change default keystore file #======================================================================== bind.address=0.0.0.0 enable.https=true http.port=8443 ssl.keystore.file=../conf/keystore.jks ssl.keystore.password=password ssl.keystore.type=JKS #logger configuration - logback.xml -
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
#======================================================================== # MySensors Gateway settings # Select Type of gateway will be used, Only one gateway will be used # Types -> serial, ethernet, mqtt #======================================================================== mcc.ethernet.gateway.type=serial #======================================================================== # MySensors Serial port settings # In this section select: Driver, port name and baud rate # Available drivers -> [pi4j, jssc, jserialcomm, auto] #======================================================================== mcc.serialport.driver.type=auto mcc.serialport.name=/dev/ttyACM0 mcc.serialport.baud.rate=115200 #======================================================================== # MySensors Ethernet Gateway settings # Update host name/ip and port number, Default: 192.168.178.6:5003 # Keep alive check frequency in seconds #======================================================================== mcc.ethernet.gateway.host=192.168.178.6 mcc.ethernet.gateway.port=5003 mcc.ethernet.gateway.keep.alive.frequency=60 #======================================================================== # MySensors MQTT Gateway settings # Update broker host name/ip and port number, Default: 192.168.178.6:1883 # Root topic name of broker # Note: MQTT_TRANSLATE_TYPES will be not supported # Disable MQTT_TRANSLATE_TYPES in your MQTT gateway #======================================================================== mcc.mqtt.gateway.broker.host=192.168.178.6 mcc.mqtt.gateway.broker.port=1883 mcc.mqtt.gateway.broker.root.topic=MyMQTT #======================================================================== # Database # Where do you want to keep your database. # It is highly recommended to take a backup of this db on upgrade. # Database: H2DB, location and name, example:/tmp/mycontroller #======================================================================== mcc.h2db.location=../conf/mycontroller #======================================================================== # Web files, will be located under ../www by default # For web used angularjs #======================================================================== www.file.location=../www/ #======================================================================== # Web Application server configuration # bind.address - interface to bind. 0.0.0.0 - all available interfaces # You can use either http or https, enable.https - https is enabled # if https is enabled specify keystore file details # It is highly recommended to use https also change default keystore file #======================================================================== bind.address=0.0.0.0 enable.https=true http.port=8443 ssl.keystore.file=../conf/keystore.jks ssl.keystore.password=password ssl.keystore.type=JKS #logger configuration - logback.xml@diggs said:
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
@diggs just now I tested with RPI native port(
/dev/ttyACM0/dev/ttyAMA0) and gives some issue, let me find out the root cause, -
@diggs said:
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
@diggs just now I tested with RPI native port(
/dev/ttyACM0/dev/ttyAMA0) and gives some issue, let me find out the root cause, -
@diggs said:
@davidbd Thanks for the reply.
Yep, can connect to the port and see the node / gateway data in the line.
Still nothing though in the Mycontroller
All my settings seem pretty standard, so not sure what the issue would be or what to check next.
@diggs just now I tested with RPI native port(
/dev/ttyACM0/dev/ttyAMA0) and gives some issue, let me find out the root cause,@jkandasa said:
@diggs just now I tested with RPI native port(/dev/ttyACM0) and gives some issue, let me find out the root cause,
@diggs Just now I confirmed that issue is not with MyController server. I didn't disable default kernel console access of serial port. Hence I couldn't not access inbuilt RPI serial port from MyController server.
I followed this page to gain user access for RPI default serial port.Now I can access default RPI serial port without any trouble. Hope you are also facing same issue.
-
@jkandasa said:
@diggs just now I tested with RPI native port(/dev/ttyACM0) and gives some issue, let me find out the root cause,
@diggs Just now I confirmed that issue is not with MyController server. I didn't disable default kernel console access of serial port. Hence I couldn't not access inbuilt RPI serial port from MyController server.
I followed this page to gain user access for RPI default serial port.Now I can access default RPI serial port without any trouble. Hope you are also facing same issue.
-
@jkandasa Checked my settings and they were already set as per that article, so I don't believe that is the trouble I am facing. From the logs I sent you, anything else you think could be causing the issue. Was the port being opened OK in the system?
@diggs said:
@jkandasa Checked my settings and they were already set as per that article, so I don't believe that is the trouble I am facing. From the logs I sent you, anything else you think could be causing the issue. Was the port being opened OK in the system?
@diggs Can you check on your RPI do you have /dev/ttyAMA0?
pi@raspberrypi ~ $ ls -lh /dev/ttyA* crw-rw---T 1 root dialout 204, 64 Jan 1 1970 /dev/ttyAMA0If you have /dev/ttyAMA0 try MyController server with /dev/ttyAMA0. I hope it should work. Kindly post your RPI hardware and software details.
-
@diggs said:
@jkandasa Checked my settings and they were already set as per that article, so I don't believe that is the trouble I am facing. From the logs I sent you, anything else you think could be causing the issue. Was the port being opened OK in the system?
@diggs Can you check on your RPI do you have /dev/ttyAMA0?
pi@raspberrypi ~ $ ls -lh /dev/ttyA* crw-rw---T 1 root dialout 204, 64 Jan 1 1970 /dev/ttyAMA0If you have /dev/ttyAMA0 try MyController server with /dev/ttyAMA0. I hope it should work. Kindly post your RPI hardware and software details.
@jkandasa I do have an AMA0, but it does not work on that one either. The gateway is definitely connected to ACM0. Which is the one it works on when I have Domoticz connected up.
Something odd is happening with the PI USB side of things. Tried switching to another port but no luck there either.
As a side, I installed on windows and it works fine, so I know the gateway is OK, but I really want it running on the PI at some point
-
@jkandasa I do have an AMA0, but it does not work on that one either. The gateway is definitely connected to ACM0. Which is the one it works on when I have Domoticz connected up.
Something odd is happening with the PI USB side of things. Tried switching to another port but no luck there either.
As a side, I installed on windows and it works fine, so I know the gateway is OK, but I really want it running on the PI at some point
@diggs said:
@jkandasa I do have an AMA0, but it does not work on that one either. The gateway is definitely connected to ACM0. Which is the one it works on when I have Domoticz connected up.
Something odd is happening with the PI USB side of things. Tried switching to another port but no luck there either.
Are you using USB to ttl connector or native RPI tx/rx pin? can you post your RPI hardware and software details?
As a side, I installed on windows and it works fine, so I know the gateway is OK, but I really want it running on the PI at some point
-
@diggs said:
@jkandasa I do have an AMA0, but it does not work on that one either. The gateway is definitely connected to ACM0. Which is the one it works on when I have Domoticz connected up.
Something odd is happening with the PI USB side of things. Tried switching to another port but no luck there either.
Are you using USB to ttl connector or native RPI tx/rx pin? can you post your RPI hardware and software details?
As a side, I installed on windows and it works fine, so I know the gateway is OK, but I really want it running on the PI at some point
-
This is fantastic. Thank you!
I am very grateful but I do have a feature request. I am collecting data in a greenhouse (and in the gardens) with mysensors. The more automation, the better. However, there are some instruments we still use manually, record data in a notebook, maybe copy to excel and manually create charts. It is very tedious and isolated form the automated sensor data.
It seems with your controller I can add a custom sensor (or use any of the other sensors) and with the Action board send data to the sensor. The feature I want is to enter data and have it appear as if the sensor sent the data. This data would then be logged along with all the automated data.
For example, we manually measure Nitrites. If I could add a custom sensor (a Manual Entry Sensor) and the action board allowed receiving data from the sensor it would provide a huge benefit. (No send data for this type of sensor is needed, only receive).
I am not sure how much work would be needed but it could also be used to test rules and other configurations.
Thanks for your work.
-
This is fantastic. Thank you!
I am very grateful but I do have a feature request. I am collecting data in a greenhouse (and in the gardens) with mysensors. The more automation, the better. However, there are some instruments we still use manually, record data in a notebook, maybe copy to excel and manually create charts. It is very tedious and isolated form the automated sensor data.
It seems with your controller I can add a custom sensor (or use any of the other sensors) and with the Action board send data to the sensor. The feature I want is to enter data and have it appear as if the sensor sent the data. This data would then be logged along with all the automated data.
For example, we manually measure Nitrites. If I could add a custom sensor (a Manual Entry Sensor) and the action board allowed receiving data from the sensor it would provide a huge benefit. (No send data for this type of sensor is needed, only receive).
I am not sure how much work would be needed but it could also be used to test rules and other configurations.
Thanks for your work.
@bpair said:
This is fantastic. Thank you!
I am very grateful but I do have a feature request. I am collecting data in a greenhouse (and in the gardens) with mysensors. The more automation, the better. However, there are some instruments we still use manually, record data in a notebook, maybe copy to excel and manually create charts. It is very tedious and isolated form the automated sensor data.
It seems with your controller I can add a custom sensor (or use any of the other sensors) and with the Action board send data to the sensor. The feature I want is to enter data and have it appear as if the sensor sent the data. This data would then be logged along with all the automated data.
For example, we manually measure Nitrites. If I could add a custom sensor (a Manual Entry Sensor) and the action board allowed receiving data from the sensor it would provide a huge benefit. (No send data for this type of sensor is needed, only receive).
I am not sure how much work would be needed but it could also be used to test rules and other configurations.
Thanks for your work.
IMO, That's one of the good reasons to use MQTT as the communication system. MySensors gets translated to MQTT messages by the gateway and that's all the controller sees. Then adding more "readings" from manual sources or any other source is just a matter of sending a message into the system from that source. There are any number of GUI and command line tools (mosquitto_pub) you can use to post a message that would make entering manual readings very easy.