Living in Southern UK - have pi3 running my controller with 12 pro mini nodes conntected to various rooms/equipment around the house.
@jkandasa Thanks for thinking about it.
It is really not a problem, more a case of ''I wonder if that would be possible". I can load a python script at startup and use that to monitor the gpio pins to run the shudown script.
Do you think it will be an issue with mcagent also running? Could there be a conflict with both python and mcagent trying to access the gpio ports?
Hi,
I am looking to shutdown the mycontroller pi properly remotely using a signal from a sensor.
There are 2 pins on the pi which will shut it down, but I don't know how this will work with mycontroller and mcagent running. I think it would be better to stop these services first and then power off the pi.
So my thinking is that I can send a high or low to the pi gpio, have mcagent monitor and detect the change and then trigger a python script to shutdown the pi?
Is it possible?
@jkandasa Thank you so much for this! 
It had slipped my mind with other more important issues taking the focus away. Today I found some 'ghost' variables and remembered that I had the problem before, but not the solution. Now I know why!
Anyway it worked perfectly and I will keep a lookout for any future ghost variables. This would be a good thing to have built into ver 2.0 
@SamuelMills A gateway should NEVER sleep.
Try again without the sleep function. Actually, try again without anything but a 'clean' gateway sketch and then add bits one at a time until you find the issue or it all works as you expect.
@guille That is a great resource, thanks.
My only comment would be that channels 111-125 are missing in the current version.
@jkandasa Would it be at all possible to move (or alias) this file to the /conf directory so that changes are not reset upon upgrade?
Great work as always JK - I have just updated with no issues at all!
@Daniele From what I have seen this is normal operation. The spikes you see I assume are from mcagent reporting CPU usage. Whilst it can usually keep around 5-6% for me, sometimes it will suddenly start doing peaks every hour/90mins/2hours. I can't see any reason for this and just assumed it was some internal housekeeping of the memory/db etc.
As for the need to restart, I had that yesterday after it stopped responding. Look into the logs and see if you see anything obvious in there. Otherwise it might be power supply related. I had a few pi builds that would sometimes give errant behaviour and even though I got 2.5A power supplies, they were not good quality ones.
On all those 'problem' pi builds, I bought better power supplies and all the issues went away. I have a new power supply to add to the MyController pi as soon as I get some regulators as I will build a UPS at the same time so that power brown-out and black-outs will not be such a problem.
As to the MQTT being a solution, I do not know about that, sorry.
Yesterday when I tried to check my sensors I couldn't get a connection to the pi. Here is the log leading up to the event.
2019-01-17 12:38:03,784 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=15, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728655369, properties=null)
2019-01-17 12:38:42,083 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=61, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728693840, properties=null)
2019-01-17 12:39:15,582 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=43, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728726135, properties=null)
2019-01-17 12:28:24,738 INFO [main] [org.mycontroller.standalone.StartApp:101]
****************************************** Data Processing Agreement *******************************************
By using this software you agree that the following non-PII (non personally identifiable information data
will be collected, processed and used by MyController.org for the purpose of improving quality of this software.
----------------------------------------------------------------------------------------------------------------
If you do not like to share anonymous data(non-PII), disable it in 'mycontroller/conf/mycontroller.properties'
by setting 'mcc.collect.anonymous.data=false' and **restart** this server and **logout and login** in the UI.
------ Thank you! ------
****************************************************************************************************************
2019-01-17 12:28:25,089 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2019-01-17 12:28:31,992 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.4.0-SNAPSHOT, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.04.06 - 2018 Dec 04), Built on:2018-12-07T12:12:54+0530, Git commit:2e154aef28a8849e5721a88e76123268cf0093d0:development]
2019-01-17 12:28:32,477 INFO [main] [org.mycontroller.standalone.offheap.OffHeapFactory:95] Cleared McPersistent location[../conf/persistent_stores/mc/]
2019-01-17 12:28:32,478 INFO [main] [org.mycontroller.standalone.AppProperties:527] Created directory location: [/home/mycontroller/conf/persistent_stores/mc]
2019-01-17 12:28:33,512 WARN [main] [io.moquette.persistence.mapdb.MapDBPersistentStore:78] Using fresh MapDB store file. Path=../conf/persistent_stores/moquette/moquette_store.mapdb
2019-01-17 12:28:34,026 WARN [main] [io.moquette.server.Server:186] Using default SSL context creator
2019-01-17 12:28:34,645 WARN [main] [io.netty.bootstrap.ServerBootstrap:146] Unknown channel option 'TCP_NODELAY' for channel '[id: 0x7c35ba88]'
2019-01-17 12:28:34,736 WARN [main] [io.netty.bootstrap.ServerBootstrap:146] Unknown channel option 'TCP_NODELAY' for channel '[id: 0x94ef539e]'
2019-01-17 12:28:34,743 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:54] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, sslEnabled=false, bindAddress=0.0.0.0, mqttPort=1883, mqttsPort=8883, websocketPort=7080, allowAnonymous=true, enabledOnBackend=true, sslKeystoreFile=null)
2019-01-17 12:28:35,569 INFO [mc-th-pool-1] [org.mycontroller.standalone.gateway.mqtt.MQTTDriver:94] MQTT Gateway[name:Raspberry Pi, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2019-01-17 12:28:35,666 INFO [main] [org.mycontroller.standalone.scheduler.SchedulerUtils:90] System jobs reloaded.
2019-01-17 12:28:38,973 INFO [main] [org.mycontroller.standalone.StartApp:238] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2019-01-17 12:28:39,429 INFO [main] [org.mycontroller.standalone.api.GoogleAnalyticsApi:94] Google analytics details[enabled:true, ga_anonymous_id:0904c9fb-6a3c-4c67-9ca8-908c0c2cb2f0]
2019-01-17 12:28:39,433 INFO [main] [org.mycontroller.standalone.StartApp:136] MyController.org server started in [14217] ms
2019-01-17 12:28:39,594 ERROR [mc-th-pool-2] [org.mycontroller.restclient.core.RestHttpClient:252] Exception when calling url:[https://www.google-analytics.com/collect], headers:[{User-Agent=Mozilla/5.0}], queryParameters:[null]
java.lang.RuntimeException: Failed to execute, Request:POST https://www.google-analytics.com/collect HTTP/1.1, error:www.google-analytics.com: Name or service not known
at org.mycontroller.restclient.core.RestHttpClient.execute(RestHttpClient.java:165)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:247)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:271)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:283)
at org.mycontroller.standalone.api.GoogleAnalyticsApi.access$100(GoogleAnalyticsApi.java:59)
at org.mycontroller.standalone.api.GoogleAnalyticsApi$1.run(GoogleAnalyticsApi.java:373)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-01-17 12:28:39,597 ERROR [mc-th-pool-2] [org.mycontroller.standalone.api.GoogleAnalyticsApi:375] Exception,
java.lang.RuntimeException: Failed to execute, url:https://www.google-analytics.com/collect, error:Failed to execute, Request:POST https://www.google-analytics.com/collect HTTP/1.1, error:www.google-analytics.com: Name or service not known
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:255)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:271)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:283)
at org.mycontroller.standalone.api.GoogleAnalyticsApi.access$100(GoogleAnalyticsApi.java:59)
at org.mycontroller.standalone.api.GoogleAnalyticsApi$1.run(GoogleAnalyticsApi.java:373)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-01-17 12:38:03,784 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=15, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728655369, properties=null)
2019-01-17 12:38:42,083 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=61, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728693840, properties=null)
2019-01-17 12:39:15,582 INFO [mc-th-pool-0] [org.mycontroller.standalone.provider.EngineAbstract:246] Seems like failed to send this message. There is no ACK received! Retried 7 time(s). MessageImpl(gatewayId=1, nodeEui=43, sensorId=SENSOR_BC, type=Internal, subType=Heartbeat, ack=1, payload=, isTxMessage=true, timestamp=1547728726135, properties=null)
2019-01-17 12:28:24,738 INFO [main] [org.mycontroller.standalone.StartApp:101]
****************************************** Data Processing Agreement *******************************************
By using this software you agree that the following non-PII (non personally identifiable information data
will be collected, processed and used by MyController.org for the purpose of improving quality of this software.
----------------------------------------------------------------------------------------------------------------
If you do not like to share anonymous data(non-PII), disable it in 'mycontroller/conf/mycontroller.properties'
by setting 'mcc.collect.anonymous.data=false' and **restart** this server and **logout and login** in the UI.
------ Thank you! ------
****************************************************************************************************************
2019-01-17 12:28:25,089 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:116] Checking migration...
2019-01-17 12:28:31,992 INFO [main] [org.mycontroller.standalone.db.DataBaseUtils:167] Application information: [Version:1.4.0-SNAPSHOT, Database(type:H2 database embedded, version:1.4.194 (2017-03-10), schema version:1.04.06 - 2018 Dec 04), Built on:2018-12-07T12:12:54+0530, Git commit:2e154aef28a8849e5721a88e76123268cf0093d0:development]
2019-01-17 12:28:32,477 INFO [main] [org.mycontroller.standalone.offheap.OffHeapFactory:95] Cleared McPersistent location[../conf/persistent_stores/mc/]
2019-01-17 12:28:32,478 INFO [main] [org.mycontroller.standalone.AppProperties:527] Created directory location: [/home/mycontroller/conf/persistent_stores/mc]
2019-01-17 12:28:33,512 WARN [main] [io.moquette.persistence.mapdb.MapDBPersistentStore:78] Using fresh MapDB store file. Path=../conf/persistent_stores/moquette/moquette_store.mapdb
2019-01-17 12:28:34,026 WARN [main] [io.moquette.server.Server:186] Using default SSL context creator
2019-01-17 12:28:34,645 WARN [main] [io.netty.bootstrap.ServerBootstrap:146] Unknown channel option 'TCP_NODELAY' for channel '[id: 0x7c35ba88]'
2019-01-17 12:28:34,736 WARN [main] [io.netty.bootstrap.ServerBootstrap:146] Unknown channel option 'TCP_NODELAY' for channel '[id: 0x94ef539e]'
2019-01-17 12:28:34,743 INFO [main] [org.mycontroller.standalone.mqttbroker.MoquetteMqttBroker:54] MQTT Broker started successfully. MqttBrokerSettings(enabled=true, sslEnabled=false, bindAddress=0.0.0.0, mqttPort=1883, mqttsPort=8883, websocketPort=7080, allowAnonymous=true, enabledOnBackend=true, sslKeystoreFile=null)
2019-01-17 12:28:35,569 INFO [mc-th-pool-1] [org.mycontroller.standalone.gateway.mqtt.MQTTDriver:94] MQTT Gateway[name:Raspberry Pi, URI:tcp://localhost:1883, NetworkType:MyController] connected successfully..
2019-01-17 12:28:35,666 INFO [main] [org.mycontroller.standalone.scheduler.SchedulerUtils:90] System jobs reloaded.
2019-01-17 12:28:38,973 INFO [main] [org.mycontroller.standalone.StartApp:238] TJWS server started successfully, HTTPS Enabled?:true, HTTP(S) Port: [8443]
2019-01-17 12:28:39,429 INFO [main] [org.mycontroller.standalone.api.GoogleAnalyticsApi:94] Google analytics details[enabled:true, ga_anonymous_id:0904c9fb-6a3c-4c67-9ca8-908c0c2cb2f0]
2019-01-17 12:28:39,433 INFO [main] [org.mycontroller.standalone.StartApp:136] MyController.org server started in [14217] ms
2019-01-17 12:28:39,594 ERROR [mc-th-pool-2] [org.mycontroller.restclient.core.RestHttpClient:252] Exception when calling url:[https://www.google-analytics.com/collect], headers:[{User-Agent=Mozilla/5.0}], queryParameters:[null]
java.lang.RuntimeException: Failed to execute, Request:POST https://www.google-analytics.com/collect HTTP/1.1, error:www.google-analytics.com: Name or service not known
at org.mycontroller.restclient.core.RestHttpClient.execute(RestHttpClient.java:165)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:247)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:271)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:283)
at org.mycontroller.standalone.api.GoogleAnalyticsApi.access$100(GoogleAnalyticsApi.java:59)
at org.mycontroller.standalone.api.GoogleAnalyticsApi$1.run(GoogleAnalyticsApi.java:373)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
2019-01-17 12:28:39,597 ERROR [mc-th-pool-2] [org.mycontroller.standalone.api.GoogleAnalyticsApi:375] Exception,
java.lang.RuntimeException: Failed to execute, url:https://www.google-analytics.com/collect, error:Failed to execute, Request:POST https://www.google-analytics.com/collect HTTP/1.1, error:www.google-analytics.com: Name or service not known
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:255)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:271)
at org.mycontroller.restclient.core.RestHttpClient.doPost(RestHttpClient.java:283)
at org.mycontroller.standalone.api.GoogleAnalyticsApi.access$100(GoogleAnalyticsApi.java:59)
at org.mycontroller.standalone.api.GoogleAnalyticsApi$1.run(GoogleAnalyticsApi.java:373)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Just FYI - it's restarted now and working overnight.
@jkandasa Following a period of relative calm in my setup, yesterday I got 2 ghost nodes appear again. One was a single temperature reading (which if correct was from the heating boiler) and the second was a single on/off.
I wonder if there is some way that a malformed message could do this? The temp one showed +58.4C and the only thing to get that hot is the heating system.
I have some nice new power supplies now (not from ali or ebay!) and will be building a UPS with these to improve stability and performance during power black/brown outs.
So nothing to do on myc front unless this still happens after all the above is done. The new supplies have cured issues on other pi builds, so hopeful on this one too....