Great work as always JK - I have just updated with no issues at all!

Great news that version 2.0 is soon in progress!!

I would like to see a more user focused product with many more guages 'out of the box' and colour options to fully customise the web interface, individual graph colour options, and more drag and click to setup the windows in the dashboard.
I strongly suggest you go to the my sensors site and visit all the 'other' controller sites to seek inspiration to take your next version to the top!

I think the automation rules/actions is far to annoying in its current state and a better way of getting something to happen based on conditions would be a bonus.
I'd prefer to keep the operations in one place on one page, that would help to start with!

It would be nice if we could also have the ability to add a video window to the dashboard pages. I use motioneye as cctv controller and would love to easily be able to add cameras from this to the mycontroller pages. All cameras are pi+camera and motion pi runs on a pi3 next to the mycontroller pi. An option to have a 'pop-up' video window on motion detect would also be nice to have.

Ability for dark mode display on timer or light sensor. Good for night time usage and also powersaving.

Ability to add floorplans for bulidings and surrounding area (gardens, outbuildings) etc with sensor locations and sensor status shown on there. Would then see at a glance which security sensor has triggered the alarm on the plan.

Ability to add photos similar to the above. Then taping or clicking on (for example) the lamp in the photo of the room would control that item.

Built in voice control - but probably a step too far for a controller, but maybe the ability to interface with another pi running voice recognition. This is very low on the list though.

Full support for 'ack' messages and better debugging of the system. Maybe some form of test page where each sensor can be interrogated and report back the result?

An automated installer! - I think that setting this all up puts a lot of people off even trying it,which is a shame. Add to that an updater script. These two things alone would improve usability to those who are put off by the current process!

Battery level graph on the dashboard. A must really.

Ability to zoom and pan the graphs within the dashboard environment. Would be probably more use on tablets, but with mouse would also work.

Easy implementation of min/max values and reporting.

Easy support for 'multi use' sensors. E.g. A motion sensor in my kitchen has various modes. Armed = send alarm on detection. Perimeter= Turn on kitchen lights on motion detection and leave on until no motion detceted for x minutes, but only if it is dark enough (that info is from another sensor). Off = Do nothing on sensor detection. Currently it is a pain to get this type of thing working.... which gives me the idae to be able to create a rule and then use that rule as a template for the next sensor/actuator by copying and changing the node/sensor/automation to suit, that would speed up setting things up!

I hope this will give you some thoughts to making an even better mycontroller in 2018!.......

Thank you for making and sharing mycontroller and making this all possible in the first place - Your support and talent is amazing!

Thank you!

As expected the raspberry pi foundation have announced that they are ceasing production of 1Gb raspberry pi models. The falling price of ram on the open market and demand from users for more ram both contriubted to this action.

Now the entry level pi comes with 2Gb ram and has also seen a £10.00 price reduction to under £35.00 in the UK.

Just to wish all of you a happy holiday and good health in the new year!

2021 the year of MyController 2.0? - I can't wait

@jkandasa I think that instead of 'sensor' you could use 'source' as all data has to come from somewhere!

Variable vould become 'value' or 'info' or 'data'.

Just my thoughts on an early Sunday morning!

Here's todays problems with MYC on a pi2......

2017-10-01 14:44:30,684 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/bin/tmp]
2017-10-01 14:44:30,700 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts]
2017-10-01 14:44:30,701 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/conditions]
2017-10-01 14:44:30,703 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/operations]
2017-10-01 14:44:30,707 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/www/_configurations]
2017-10-01 14:44:30,708 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/persistent_stores]
2017-10-01 14:44:30,818 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-01 14:44:34,229 INFO [main] [org.mycontroller.standalone.db.migration.V1_01__Initial_Configuration:398] Migration completed successfully.
2017-10-01 14:44:34,486 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_01__SNAPSHOT:63] Migration completed successfully.
2017-10-01 14:44:34,621 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_02__SNAPSHOT:127] Migration completed successfully.
2017-10-01 14:44:34,733 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_03__SNAPSHOT:48] Migration completed successfully.
2017-10-01 14:44:34,834 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_04__SNAPSHOT:107] Migration completed successfully.
2017-10-01 14:44:34,934 INFO [main] [org.mycontroller.standalone.db.migration.V1_01_05__0_0_3_alpha1:49] Migration completed successfully.
2017-10-01 14:44:35,193 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_04__2016_Apr_25:58] Migration completed successfully.
2017-10-01 14:44:35,206 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_01__2016_Mar_24:340] Migration completed successfully.
2017-10-01 14:44:35,366 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_02__2016_Apr_11:66] Migration completed successfully.
2017-10-01 14:44:39,448 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_03__2016_Apr_14:85] Migration completed successfully.
2017-10-01 14:44:39,617 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_04__2016_Apr_25:58] Migration completed successfully.
2017-10-01 14:44:39,672 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_05__2016_Apr_27:68] Migration completed successfully.
2017-10-01 14:44:39,723 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_06__2016_May_10:49] Migration completed successfully.
2017-10-01 14:44:39,769 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_07__2016_May_19:57] Migration completed successfully.
2017-10-01 14:44:39,834 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_08__2016_Jul_01:108] Migration completed successfully.
2017-10-01 14:44:39,879 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_09__2016_Jul_16:93] Migration completed successfully.
2017-10-01 14:44:39,926 INFO [main] [org.mycontroller.standalone.db.migration.V1_02_10__2016_Jul_29:53] Migration completed successfully.
2017-10-01 14:44:39,977 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_01__2016_Aug_03:66] Migration completed successfully.
2017-10-01 14:44:40,028 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_02__2016_Aug_06:63] Migration completed successfully.
2017-10-01 14:44:40,070 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_03__2016_Sep_20:95] Migration completed successfully.
2017-10-01 14:44:40,109 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_04__2016_Oct_19:61] Migration completed successfully.
2017-10-01 14:44:40,151 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_05__2016_Nov_18:77] Migration completed successfully.
2017-10-01 14:44:40,278 INFO [main] [org.mycontroller.standalone.db.migration.V1_03_06__2017_Mar_03:66] Migration completed successfully.
2017-10-01 14:44:40,715 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:161] Number of migrations done:22
2017-10-01 14:44:40,718 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-01 14:44:41,017 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/persistent_stores/mc]
2017-10-01 14:44:41,676 INFO [Thread-8] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-01 14:44:42,666 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=false)
2017-10-01 14:44:45,177 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-01 14:44:45,178 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [14529] ms
[Sun Oct 01 14:44:45 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
2017-10-01 14:46:44,600 INFO [Acme.Utils.ThreadPool(4)-PooledThread: Acme.Serve.Serve$ServeConnection@39240b] [org.mycontroller.standalone.api.BackupApi:219] Restore triggered.
2017-10-01 14:46:47,602 INFO [Thread-16] [org.mycontroller.standalone.backup.Restore:69] About to restore a backup, BackupFile(name=on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53.zip, canonicalPath=/home/myvbackup/on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53.zip, timestamp=1506863694000, size=316013)
[Sun Oct 01 14:46:47 BST 2017] Accept: java.net.SocketException: Socket closed
2017-10-01 14:46:47,794 INFO [Thread-16] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:70] MQTT Broker has been stopped successfully
2017-10-01 14:46:52,994 INFO [Thread-16] [org.mycontroller.standalone.db.DataBaseUtils:288] Database restore completed. Database url:jdbc:h2:file:../conf/mycontroller;MVCC=TRUE, Restored file name:/home/mycontroller/bin/tmp/on-demand_mc_backup_h2db_embedded-2017_10_01-14_14_53/database_backup.zip
2017-10-01 14:46:53,010 INFO [Thread-16] [org.mycontroller.standalone.backup.Restore:153] Restore completed successfully. Start 'MyController.org' server manually
2017-10-01 14:46:53,015 WARN [MyController.org Shutdown-Hook] [org.knowm.sundial.SundialJobScheduler:140] Scheduler has not yet been created!!! Call "createScheduler" first.
2017-10-01 14:46:53,016 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.AppShutdownHook:36] Bye, Have a nice day! See you soon
2017-10-01 14:48:57,300 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts]
2017-10-01 14:48:57,334 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/conditions]
2017-10-01 14:48:57,336 INFO [main] [org.mycontroller.standalone.AppProperties:497] Created directory location: [/home/mycontroller/conf/resources/scripts/operations]
2017-10-01 14:48:57,883 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-01 14:49:02,677 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-01 14:49:04,067 INFO [Thread-6] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-01 14:49:04,993 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=true)
2017-10-01 14:49:05,754 INFO [main] [org.mycontroller.standalone.gateway.mqtt.MqttGatewayImpl:67] MQTT Gateway[name:Raspberry PI, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2017-10-01 14:49:09,893 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-01 14:49:09,894 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [12683] ms
[Sun Oct 01 14:51:31 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Mon Oct 02 07:53:03 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Tue Oct 03 07:18:29 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 09:20:10 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 14:50:38 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 21:17:40 BST 2017] IO error: javax.net.ssl.SSLHandshakeException: Received fatal alert: unknown_ca in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
2017-10-04 21:22:37,318 ERROR [Thread-8] [org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm:94] Exception, 
java.lang.NegativeArraySizeException: null
	at org.mycontroller.standalone.gateway.serialport.SerialDataListenerjSerialComm.serialEvent(SerialDataListenerjSerialComm.java:59)
	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener.waitForSerialEvent(SerialPort.java:937)
	at com.fazecast.jSerialComm.SerialPort$SerialPortEventListener$1.run(SerialPort.java:885)
	at java.lang.Thread.run(Thread.java:745)
2017-10-04 21:23:11,304 INFO [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortMonitoringThread:112] Serial GatewayTable[GatewaySerial(super=Gateway(id=2, enabled=true, name=MYSGW, type=SERIAL, networkType=MY_SENSORS, timestamp=1505319425589, state=DOWN, statusMessage=ERROR: null, statusSince=1507148557303, txDelay=0), driver=AUTO, portName=/dev/ttyMySensorsGateway, baudRate=115200, retryFrequency=60, runningDriver=JSERIALCOMM)] not connected, Reconnect initiated...
2017-10-04 21:23:11,832 ERROR [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortjSerialCommImpl:74] Unable to open serial port:[/dev/ttyMySensorsGateway]
2017-10-04 21:23:11,842 INFO [Thread-9] [org.mycontroller.standalone.gateway.serialport.SerialPortMonitoringThread:93] Serial GatewayTable[GatewaySerial(super=Gateway(id=2, enabled=true, name=MYSGW, type=SERIAL, networkType=MY_SENSORS, timestamp=1505319425589, state=DOWN, statusMessage=ERROR: Unable to open!, statusSince=1507148557303, txDelay=0), driver=AUTO, portName=/dev/ttyMySensorsGateway, baudRate=115200, retryFrequency=60, runningDriver=JSERIALCOMM)], Unable to reconnected! Will do next try after 60 second(s)
[Wed Oct 04 21:24:08 BST 2017] Accept: java.net.SocketException: Socket closed
2017-10-04 21:24:09,469 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:70] MQTT Broker has been stopped successfully
2017-10-04 21:24:09,486 INFO [MyController.org Shutdown-Hook] [org.mycontroller.standalone.AppShutdownHook:36] Bye, Have a nice day! See you soon
2017-10-04 21:24:29,288 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2017-10-04 21:24:34,266 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.0.0.Final, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.03.06 - 2017 Mar 03), Built on:2017-09-25T11:00:11+0530, Git commit:07c3a228b9c861280fe2f560ed4d1097349d08bb:master]
2017-10-04 21:24:35,659 INFO [Thread-6] [org.mycontroller.standalone.message.RawMessageQueue:54] Cleared offline messages[0] from the queue.
2017-10-04 21:24:36,731 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:52] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, bindAddress=0.0.0.0, httpPort=1883, websocketPort=7080, allowAnonymous=true)
2017-10-04 21:24:37,491 INFO [main] [org.mycontroller.standalone.gateway.mqtt.MqttGatewayImpl:67] MQTT Gateway[name:Raspberry PI, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2017-10-04 21:24:42,259 INFO [main] [org.mycontroller.standalone.StartApp:214] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2017-10-04 21:24:42,260 INFO [main] [org.mycontroller.standalone.StartApp:112] MyController.org server started in [13531] ms
[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet
org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
	at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
	... 12 more
Caused by: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1906)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1870)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1815)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:128)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.write(Serve.java:4854)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:46)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:71)
	at org.jboss.resteasy.util.DelegatingOutputStream.write(DelegatingOutputStream.java:48)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2003)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.flush(UTF8JsonGenerator.java:1019)
	at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:891)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:207)
	... 20 more
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431)
	at sun.security.ssl.OutputRecord.write(OutputRecord.java:417)
	at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:876)
	at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:847)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
	... 29 more

[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet
org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
	at java.lang.Thread.run(Thread.java:745)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1541)
	at sun.security.ssl.SSLSocketImpl.checkWrite(SSLSocketImpl.java:1553)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:71)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
	... 12 more
Caused by: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:208)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
	at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1906)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1870)
	at sun.security.ssl.SSLSocketImpl.handleException(SSLSocketImpl.java:1815)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:128)
	at java.io.OutputStream.write(OutputStream.java:75)
	at Acme.Serve.Serve$ServeOutputStream.write(Serve.java:4854)
	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.write(HttpServletResponseWrapper.java:46)
	at org.jboss.resteasy.util.CommitHeaderOutputStream.write(CommitHeaderOutputStream.java:71)
	at org.jboss.resteasy.util.DelegatingOutputStream.write(DelegatingOutputStream.java:48)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator._flushBuffer(UTF8JsonGenerator.java:2003)
	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.flush(UTF8JsonGenerator.java:1019)
	at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:891)
	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:207)
	... 20 more
Caused by: java.net.SocketException: Broken pipe
	at java.net.SocketOutputStream.socketWrite0(Native Method)
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
	at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:431)
	at sun.security.ssl.OutputRecord.write(OutputRecord.java:417)
	at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:876)
	at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:847)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:123)
	... 29 more

[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
[Wed Oct 04 21:24:48 BST 2017] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
[Wed Oct 04 21:24:48 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl
[Wed Oct 04 21:24:48 BST 2017] IO error: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLException: java.net.SocketException: Broken pipe in processing a request from /192.168.1.6:8443 / sun.security.ssl.SSLSocketImpl

Hope this helps to improve stability.....

How do you compare 2 sensor values in a script to send different messages dependant on the values?

Just to let you all know that a new mysensors version is released now.

You asked for suggestions so here's a couple for now....

1. Monitor and report network lan traffic bandwidth used (maybe with options to see different types of traffic eg tcp/http/udp etc....).

2. Get data for the number of packets sent/received by the nrf24l01+ attached to the pi.

Still, it's working well now and very useful to see this info!

@Tag
thanks for the support but the mystery is solved (at least this bit) - I rebooted the pi before giving the mysgw -d and of course mysgw was already started at boot and so was trying to start a second session and that is why the strange messages happened.

I have the system working again now and hope that it will stay that way for many weeks! ......

New version of ssh client/server for x64 x86 and arm is now available.

@jkandasa I'm in for a new version!!!

For those who use the IDE on local device and want to be on the latest version - tested with 1 sketch and no issues found.

For those who use PuTTY for SSH access there is a new release at their downloads page.....

As the title suggests - a new version is now released and so far testing it I have not encountered any issues with it....

@jkandasa I don't know if it might be related, but yesterday when rewiring my gateways I entered a condition where the GW was 'up' and showing last message count OK, but no update on any sensor graphs attached to that GW - I wonder if it is an issue between myc and the db as I assume all graph updates come from db?

The cure was to remove power from GW and then restore power. All seems OK after that....

@jkandasa Great stuff - another amazing new feature for V2.0!

@jkandasa Thanks, I understand but was thinking that to make it simple for users in 2.0 an entry in settings with a checkbox for RTC attached and then a 'timer style' option for frequency of update and then say 2 boxes to enter the NTP wervers to try and update from.

This way user only need to get RTC connected and recognised by pi and all the rest is taken care of in MyController....

I also see that GPS time servers are getting cheaper so another option if 'off grid' accurate time is required.

@jkandasa I was thinking more on this, I suppose that without a RTC then it all depends on the accuracy of the 'fake clock' on the pi? I also assume that the pi needs NTP to update the clock at regular intervals to remain accurate.

Maybe in version 2.0 we could add in an option for RTC module (they are cheap) and a menu for users to add regular NTP updates as per their own schedule?

@jkandasa Thank you!