@electrik Yes, I called that "different automation solution" - I was wondering if the controller "MyController" can do that, so that I would not need to set up another one...
The other way round I can send MQTT messages that MyController can handle (push them into a sensor variable of type Text for example) and then could try to work on the JSON in that string...which does not sound very smart or elegant.
Before installing a different automation solution, I wonder if it is possible to make MyController operate on non-MySensors MQTT messages? I am using the MiLight ESP8266 Gateway and would like to use a MiLight remote to control other things besides Milights and therefore want to use the messages that the ESP8266 will publish to MQTT to run scripts and things like that...?!
Greetings,
Velo17
@mfalkvidd I make / make install a couple of times and maybe did a git pull inbetween as well - now everything is back to normal again. Thank you for giving me some dbug tips for the next issue 
My strace output looks similiar.
My configure line is
./configure --my-rf24-channel=124 --my-rf24-irq-pin=29 --my-rf24-ce-pin=31 --my-rf24-cs-pin=36 --spi-driver=SPIDEV --spi-spidev-device=/dev/spidev1.0 --my-debug=disable
I just noticed that mysgw is constantly consuming 95-100% CPU here. This even happens when I unplug the NRF24 module so that after starting mysgw basically nothing happens. Running development branch. Hmmmm. Any idea what to check?
I think I might have found the root of the problem. The ./configure detects my Rpi2 as such (rpi2) but in the RPi.cpp in line 26 there is the pin to GPIO translation array and it is lacking translations for the high pin numbers - which is obviously wrong as on the RPi2 you have the extended GPIO connector with 40 pins...
const static int pin_to_gpio_rev1[41] = {-1, -1, -1, 0, -1, 1, -1, 4, 14, -1, 15, 17, 18, 21, -1, 22, 23, -1, 24, 10, -1, 9, 25, 11, 8, -1, 7, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1 };
const static int pin_to_gpio_rev2[41] = {-1, -1, -1, 2, -1, 3, -1, 4, 14, -1, 15, 17, 18, 27, -1, 22, 23, -1, 24, 10, -1, 9, 25, 11, 8, -1, 7, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1, -1 };
const static int pin_to_gpio_rev3[41] = {-1, -1, -1, 2, -1, 3, -1, 4, 14, -1, 15, 17, 18, 27, -1, 22, 23, -1, 24, 10, -1, 9, 25, 11, 8, -1, 7, -1, -1, 5, -1, 6, 12, 13, -1, 19, 16, 26, 20, -1, 21 };
I copied the rev3 array to the rev2 array and compiled this and it seems to work in my case!
Hello everyone!
I am trying to use a NRF24 module on the SPI1 of a Raspberry2 (so that I can also use a touch tft on SPI0).
I enabled it in the config.txt so that is lists under /dev/spidev1.0 - for conveniency I configured the CS0 to be at GPIO16=Pin36 (by using dtoverlay=spi1-1cs,cs0_pin=16).
I use the dev branch of MySensors.git as the master branch does not recognize my Pi. I used this configure line:
./configure --my-rf24-channel=124 --my-rf24-irq-pin=29 --my-rf24-ce-pin=31 --my-rf24-cs-pin=36 --spi-driver=SPIDEV --spi-spidev-device=/dev/spidev1.0
successful make
but when I run the gateway in the shell with sudo ./bin/mysgw -d, I get the following:
mysgw: Starting gateway...
mysgw: Protocol version - 2.2.0-beta
__ __ ____
| \/ |_ _/ ___| ___ _ __ ___ ___ _ __ ___
| |\/| | | | \___ \ / _ \ `_ \/ __|/ _ \| `__/ __|
| | | | |_| |___| | __/ | | \__ \ _ | | \__ \
|_| |_|\__, |____/ \___|_| |_|___/\___/|_| |___/
|___/ 2.2.0-beta
mysgw: MCO:BGN:INIT CP=RNNG--Q-
mysgw: TSF:LRT:OK
mysgw: TSM:INIT
mysgw: TSF:WUR:MS=0
mysgw: pinMode: invalid pin: 29
mysgw: pinMode: invalid pin: 31
mysgw: pinMode: invalid pin: 36
mysgw: digitalWrite: invalid pin: 31
mysgw: digitalWrite: invalid pin: 36
mysgw: digitalPinToInterrupt: invalid pin: 29
mysgw: digitalPinToInterrupt: invalid pin: 29
mysgw: digitalWrite: invalid pin: 36
Any ideas what I can do to make it work?
Hello everyone!
I'm using a Rasp2 (with the 40 pins GPIO header)
Has anyone experience with using the NRF module on different pins than default? I'm asking because I wonder if I can connect a GPIO-connected touch TFT (which would use the 2 CE lines for the touch and display interfaces) together with the NRF - by hooking the MISO/MOSI/SCLK to the default pins (and thus sharing them between the TFT and NRF) and defining free pins for the CE and CS lines in the ./configure script when compiling the gateway code...?!
Or maybe using the SPI1 by first enabling it as laid out in this blog post - but how to proceed from there? (How to tell the gateway code to use SPI1?)
@marceloaqno Thanks for the hint! This actually solves the lock up. But shouldnt the interrupt offer a superior connectivity and thus be desireable? Until yesterday (before I did the RPi upgrading) this worked - or at least it appeared to work (I dont know if the interrupt was actually used)
(sorry, I hit reply on mfalkvidd's post)
I have a strange problem:
I tried to be smart (haha) and updated my Raspberry2 with
sudo apt-get update
sudo apt-get dist-upgrade
This took quite a while and looked successful to me.
Unfortunately the MySensors Gateway and/or controller setup is not working correctly anymore. For troubleshooting I disabled my controller (MyController running on the Pi and for sniffing also MYSController available on my Windows machine). I stopped the gateway service and manually ran the gateway with -d debug information and get this:
mysGateway: Starting gateway...
mysGateway: Protocol version - 2.0.1-beta
mysGateway: MCO:BGN:INIT GW,CP=RNNG--Q,VER=2.0.1-beta
mysGateway: TSF:LRT:OK
mysGateway: TSM:INIT
mysGateway: TSM:INIT:TSP OK
mysGateway: TSM:INIT:GW MODE
mysGateway: TSM:READY
mysGateway: Listening for connections on 0.0.0.0:5003
mysGateway: MCO:REG:NOT NEEDED
mysGateway: MCO:BGN:STP
mysGateway: MCO:BGN:INIT OK,ID=0,PAR=0,DIS=0,REG=1
mysGateway: TSF:MSG:READ,7-7-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:BC
mysGateway: TSF:MSG:FPAR REQ,ID=7
mysGateway: TSF:PNG:SEND,TO=0
mysGateway: TSF:CKU:OK
mysGateway: TSF:MSG:GWL OK
mysGateway: TSF:MSG:SEND,0-0-7-7,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
mysGateway: TSF:MSG:PINGED,ID=7,HP=1
mysGateway: TSF:MSG:SEND,0-0-7-7,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
mysGateway: TSF:MSG:SEND,0-0-7-7,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=OK:0100
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=0,t=17,pt=0,l=5,sg=0:2.0.0
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=11,pt=0,l=17,sg=0:Ernie Giess-O-Mat
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=12,pt=0,l=4,sg=0:0.17
mysGateway: TSF:MSG:READ,7-7-0,s=2,c=0,t=6,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:READ,7-7-0,s=0,c=0,t=7,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:READ,7-7-0,s=3,c=0,t=30,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:READ,7-7-0,s=4,c=0,t=21,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:READ,7-7-0,s=255,c=3,t=26,pt=1,l=1,sg=0:2
mysGateway: TSF:MSG:SEND,0-0-7-7,s=255,c=3,t=27,pt=1,l=1,sg=0,ft=0,st=OK:1
mysGateway: TSF:MSG:READ,7-7-0,s=0,c=1,t=1,pt=7,l=5,sg=0:8219.0
mysGateway: TSF:MSG:READ,7-7-0,s=2,c=1,t=0,pt=7,l=5,sg=0:29.66
mysGateway: TSF:MSG:READ,7-7-0,s=3,c=1,t=38,pt=7,l=5,sg=0:9.0
mysGateway: TSF:MSG:READ,7-7-0,s=4,c=1,t=34,pt=1,l=1,sg=0:0
mysGateway: TSF:MSG:READ,17-17-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
mysGateway: TSF:MSG:BC
mysGateway: TSF:MSG:FPAR REQ,ID=17
mysGateway: TSF:PNG:SEND,TO=0
mysGateway: TSF:CKU:OK
mysGateway: TSF:MSG:GWL OK
mysGateway: TSF:MSG:SEND,0-0-17-17,s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=OK:0
mysGateway: TSF:MSG:READ,17-17-0,s=255,c=3,t=24,pt=1,l=1,sg=0:1
mysGateway: TSF:MSG:PINGED,ID=17,HP=1
mysGateway: TSF:MSG:SEND,0-0-17-17,s=255,c=3,t=25,pt=1,l=1,sg=0,ft=0,st=OK:1
mysGateway: TSF:MSG:READ,7-7-0,s=0,c=1,t=1,pt=7,l=5,sg=0:10834.0
mysGateway: TSF:MSG:READ,7-7-0,s=2,c=1,t=0,pt=7,l=5,sg=0:3.96
mysGateway: TSF:MSG:READ,7-7-0,s=3,c=1,t=38,pt=7,l=5,sg=0:9.0
mysGateway: TSF:MSG:READ,7-7-0,s=4,c=1,t=34,pt=1,l=1,sg=0:0
mysGateway: TSF:MSG:READ,17-17-0,s=255,c=3,t=0,pt=1,l=1,sg=0:67
mysGateway: TSF:MSG:READ,17-17-0,s=1,c=1,t=0,pt=7,l=5,sg=0:18.8
mysGateway: TSM:READY:NWD REQ
mysGateway: TSF:MSG:SEND,0-0-255-255,s=255,c=3,t=20,pt=0,l=0,sg=0,ft=0,st=OK:
mysGateway: TSF:SRT:OK
Which looks okay to me (2 sensor nodes are sending data here). But after this NWD REQ...STR:OK block nothing more happens, only more of these 3 lines blocks repeat over and over with about 15 minutes or so inbetween.
"of course" I also re-compiled the gateway source with re-setting the configuration, which is
sudo ./configure --my-rf24-channel=124 --my-rf24-irq-pin=11 --my-debug=enable
sudo make install
any ideas what I can try to make it work again? 
In any case, happy weekend to everyone,
greetings from Germany!
Hello everyone. Is there a way to reduce the number of Heartbeat messages the gateway produces by itself? Using MYSController to analyze the data traffic, I see every 10 seconds a Heartbeat - would like to reduce this once everything is working as expected to maybe every 5 or 10 minutes...
Hello! Will there be a chance to change the radio channel used for the bootloader OTA process?
@niccodemi It's been already a couple of years ago when I last tried to get this running like you describe - actually in the IPv4 days. But that client I used doesnt work with IPv6 anymore. Can you tell me which client and maybe DDNS service you are using? And yes, I'm running Raspbian. True, last option would be Teamviewer.
Thank you and greetings from Germany!
...trying to download the jar from the link in the first post, but server is not reachable. Is there any other URL to this .jar?
I have sort of the same question, but the easy way to give access to my Raspberry thru my router by using a DDNS service is not working for me, as I have a crippled dual stack lite IPv6 implementation.
So I am more or less left to rely on the other way round: Push data from the home server into the internet. Is there a recommended way of doing this with mycontroller or more general mysensors? I am not using MQTT so far, just an ethernet gateway. For example Domoticz have this my.domoticz service which enables just this very easily.
Hello!
I'm getting into MyController now and it looks really promising so far! So far I used Domoticz but my main needs are better statistics/graphs and MyController out of the box delivers better graphs.
What I would really love to be able to do, is to specify more than 2 Y-axis to be able to combine more different graphs with better scaling. And even better would be to be able to define an individual interpolation type for each datarow.
In my gardening application I currently have a sensor that delivers soil moisture, temperature, VCC voltage and a "level" value, that indicates how many watering cycles a given pump for this plant was triggered at a given time. Most of the time the sensor will deliver 0 for this cycles value as only 4 times in 24 hours the pumps will eventually run at all.
So at the moment:
My soil moisture gives an arbitrary value of 10000-20000 (this could be changed by my code of course to a different range, but as this will be the left axis anyway, that doesnt make a big difference)
Temperature is 0-30
VCC is 8-10
Cycles is mostly 0, and sometimes in the range 1-10 (for this i would love to use the step interpolation, for all others the base or something else)
I fear that the used API for the graphing only allows a max of 2 Y-axis and so this simply is too much to ask for - but maybe I am lucky and this only needs a little extra work?!
Ah, forgot to ask: Is is possible to change the formatting/datatype that is used in the graphs? Im asking because for example my VCC comes as a float value with one decimal digit but in the graph this is always an integer and so I dont see much change there...
Another enhancement would be if any graph widget could be quickly adjusted for the time being shown (for example by a listbox selection) - at the moment the whole widget has to be edited to change the x axis data source. Maybe mouse-selection ranging / zooming would be cool as well (as Domoticz user I miss these features here)
Thank you for this nice piece of software already!
Hello 172pilot.
I am in the same boat. I created a watering system based on 2 Arduinos, one is outside and one inside, the latter acting as monitoring screen that regulary receives values from the outside station. I want to change to MySensors in order to have more possibilities.
I now use a Raspberry Pi that acts as MySensors gateway with a NRFL01 module and also as controller running Domoticz.
To get started I programmed another Arduino with some basic sensor code so that I have some test data to send to my gateway and after this worked I now start to adapt my outside station code to report it's data to my gateway.
Over here I only need to include
#define MY_RADIO_NRF24
#include <MySensors.h>
to my working code and then define the sensor node id etc. as you can see from the various examples.
So I would suggest to first start with a test sensor node so that you can check that the basic data transfer is actually working fine.
In your scenario you would probably try to run the gateway code on an Arduino and connect it to your controller by a WiFi connection and see if this happens correctly, but this is different from my project.