MySensors node doesn’t appear in Jeedom
-
Hi,
After installing MySenor plugin on Jeedom, I switched a serial gateway arduino on my raspberry, and send messages by an arduino (value 1 and 0 every 10 seconds).I see it in MySensorsLog in my plugin jeedom interface :
Thu Jan 05 2017 11:05:54 GMT+0000 (UTC) - Jeedom url : http://192.168.0.49:80/plugins/mySensors/core/api/jeeSensors.php?apikey=(...), gwAddress : /dev/ttyUSB0
DEPRECATION: Please userequire('serialport')
instead ofrequire('serialport').SerialPort
Thu Jan 05 2017 11:05:54 GMT+0000 (UTC) - server bound on 8019
Thu Jan 05 2017 11:05:54 GMT+0000 (UTC) - connected to serial gateway at /dev/ttyUSB0
Thu Jan 05 2017 11:05:55 GMT+0000 (UTC) : 0;0;3;0;9;gateway started, id=0, parent=0, distance=0
Thu Jan 05 2017 11:05:55 GMT+0000 (UTC) : 0;0;3;0;14;Gateway startup complete.
Thu Jan 05 2017 11:05:59 GMT+0000 (UTC) : 0;0;3;0;9;read: 0-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0:1
Thu Jan 05 2017 11:06:00 GMT+0000 (UTC) : 0;3;1;0;16;1
Thu Jan 05 2017 11:06:10 GMT+0000 (UTC) : 0;0;3;0;9;read: 0-0-0 s=3,c=1,t=16,pt=2,l=2,sg=0:0
Thu Jan 05 2017 11:06:10 GMT+0000 (UTC) : 0;3;1;0;16;0But not any mySensor node appears in Jeedom with inclusion mode !
Thanks
-
@philoudumdum
did you restart any node when your are in inclusion mode?
-
I have the same problem, and i did a restart of my node when jeedom was in inclusion mode.
Wed Jan 18 2017 19:22:03 GMT+0100 (CET) - Jeedom url : http://:80/plugins/mySensors/core/api/jeeSensors.php?apikey=KN3AxPW64r0xrnjGckMD5E9bD4TV6DZcZvCj3xgJZrmykMT1&gateway=master, gwAddress : /dev/ttyUSB020 DEPRECATION: Please use `require('serialport')` instead of `require('serialport').SerialPort` Wed Jan 18 2017 19:22:03 GMT+0100 (CET) - server bound on 8019 Wed Jan 18 2017 19:22:03 GMT+0100 (CET) - connected to serial gateway at /dev/ttyUSB020 1/18/2017, 7:22:03 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;255;0;0;17;2.1.0 -> 105;255;3;0;6;M Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;255;3;0;6;0 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;255;3;0;11;TemperatureAndHumidity 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;255;3;0;12;1.1 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;1;0;0;6; 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;1;1;0;0;20.0 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' } Wed Jan 18 2017 19:22:22 GMT+0100 (CET) : 105;0;1;0;1;21.0 1/18/2017, 7:22:22 PM { [Error: socket hang up] code: 'ECONNRESET' }
-
It works now.
I just added gw.sendSketchInfo command in the setup of my sketch script.
-
Hello,
I've just installed a sensor node and a serial gateway with the last version of MySensors Library, 2.1.1 and nRF24L01+ network devices. The serial gateway is connected (/dev/ttyACM0) to my Jeedom box running the last software version (2.4.6.).
The sensor node is running the Air Humidity sketch (with DHT22 device) found here and the serial gateway with the adequate sketch found hereon this web site.Communication between them seems to work correctly, the serial gateway seems also to be recognized by the Jeedom box via the MySensors Plugin (latest stable version), but Jeedom cannot see any sensor node, even with inclusion mode and after reconnecting the sensor node itself (off/on).
Here is an extract of the the Jeedom plugin MySensors_node log.
Thank you in advance.... Fri Feb 10 2017 17:15:04 GMT+0100 (CET) - connected to serial gateway at /dev/ttyACM0 2/10/2017, 5:15:04 PM null Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;MCO:BGN:INIT GW,CP=RNNGA--,VER=2.1.1 Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;TSM:INIT Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;TSF:WUR:MS=0 Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;TSM:INIT:TSP OK Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;TSM:INIT:GW MODE Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;TSM:READY:ID=0,PAR=0,DIS=0 Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;MCO:REG:NOT NEEDED Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;14;Gateway startup complete. Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;0;0;18;2.1.1 Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;MCO:BGN:STP Fri Feb 10 2017 17:15:05 GMT+0100 (CET) : 0;255;3;0;9;MCO:BGN:INIT OK,TSP=1 2/10/2017, 5:15:05 PM null Fri Feb 10 2017 17:15:56 GMT+0100 (CET) : 0;255;3;0;9;TSF:MSG:READ,3-3-0,s=1,c=1,t=0,pt=7,l=5,sg=0:20.0 Fri Feb 10 2017 17:15:56 GMT+0100 (CET) : 3;1;1;0;0;20.0 Fri Feb 10 2017 17:15:56 GMT+0100 (CET) : 0;255;3;0;9;TSF:MSG:READ,3-3-0,s=0,c=1,t=1,pt=7,l=5,sg=0:37.4 Fri Feb 10 2017 17:15:56 GMT+0100 (CET) : 3;0;1;0;1;37.4 2/10/2017, 5:15:56 PM null 2/10/2017, 5:15:56 PM null```
-
Hello,
Hallelujah, I managed to get everything working perfect. Shame on me
The main problem came from a bad definition of the internal address (Network configuration section), in particular the "complementary" part of the address (/jeedom) which was not to be defined for me (check your URL Jeedom access to be sure).
So I have : http://jeedom:80 where "jeedom" is 127.0.1.1 (as to be defined in /etc/hosts).
Hope this help.
Eric.
Suggested Topics
-
Vera Inclusion Not Working
Troubleshooting • 3 Apr 2014, 04:52 • MisterE 16 Apr 2014, 17:03 -
Jeedom application can't see ethernet gateway
Jeedom • 18 Feb 2016, 17:37 • fredmet8 25 Feb 2016, 19:36 -
Jeedom update error
Jeedom • 25 Mar 2018, 08:53 • pgaudel 30 Mar 2018, 11:28 -
Cannot show history and graph
Jeedom • 23 Nov 2015, 10:15 • jeppefugl 23 Nov 2015, 10:15 -
Mysensors et dual Bus
Jeedom • 7 Mar 2022, 15:13 • JeeLet 9 Mar 2022, 20:49 -
Jeedom and RGB control
Jeedom • 24 Mar 2020, 10:35 • Robert77 24 Mar 2020, 10:35