[solved]mySensor V2 problem with device in pimatic

---

Hello,

I had tested MySensor 1.5 vor about 8 month, with one gateway at the USB-Port of the Raspi with one Testsensor with the script from @sweebee whats send “0” and “1”.
That has worked.
Now I had update the Gateway to Mysensor V2 and use at the Testsensor this script:

#define OPEN 1
#define CLOSE 0
#define NODE_ID 1
#define CHILD_ID 3
#define MY_RADIO_NRF24
#define MY_DEBUG    // Enables debug messages in the serial log

#include <MySensors.h>
#include <SPI.h>

MyMessage msg(NODE_ID, V_TRIPPED);

uint8_t value = OPEN;

void presentation()
{
    present(CHILD_ID, S_DOOR);
}

void loop()
{
    value = value == OPEN ? CLOSE : OPEN;
    send(msg.set(value));
    sleep(10000);
}

This will send a “0” and after 10s a “1” and so on.

The Console of the Arduino Software shows this:

TSM:ID
TSM:CHKID:OK (ID=3)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-3 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
TSP:MSG:SEND 3-3-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:READ 0-0-3 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:MSG:SEND 3-3-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,ft=0,st=ok:
Request registration...
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-3 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registration=1
Init complete, id=3, parent=0, distance=1, registration=1
TSP:MSG:SEND 3-3-0-0 s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:SEND 3-3-0-0 s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:SEND 3-3-0-0 s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0

And on the ssh terminal on the Raspi I see this:

sudo screen /dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0 115200

0;255;3;0;9;
TSP:MSG:READ 3-3-0 s=1,c=1,t=16,pt=1,l=1,sg=0:1
3;1;1;0;16;1
0;255;3;0;9;
TSP:SANCHK:OK
0;255;3;0;9;
TSP:MSG:READ 3-3-0 s=1,c=1,t=16,pt=1,l=1,sg=0:0
3;1;1;0;16;0
0;255;3;0;9;
TSP:MSG:READ 3-3-0 s=1,c=1,t=16,pt=1,l=1,sg=0:1
3;1;1;0;16;1

So I think the Testsensor and the Gateway is working.

But the device in Pimatic don’t change from open to close.

In the Pimatic config is the following:

{
      "plugin": "mysensors",
      "driver": "serialport",
      "protocols": "1.5.1",
      "driverOptions": {
        "serialDevice": "/dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0",
        "baudrate": 115200
      },
      "startingNodeId": 3
    },

{
      "nodeid": 1,
      "sensorid": 3,
      "id": "mysensor-test",
      "name": "MySensor_Test",
      "class": "MySensorsButton"
    },

Maybe the “protocols”: “1.5.1”, is wrong.bolded text

I use MySensors since 1/2 year and did same update of Gateway about 2 Month ago.

There hasn’t been any issue with existing devices useing old 1.5.x protocols, but in tghe meantime I updated all execept one to MySensors 2.0. In my config for the Plugin there is still “protocols: 1.5.4” setting, so this was no problem for me.
Maybe you can change to 2.0.0 to see if its working then?

@V1per
Is it right that the last config part of your post shows the device you configered ?

Than it should be NodeID = 3 and Sensor ID =1 isn’t it?

   {
      "nodeid": 3,
      "sensorid": 1,
      "id": "mysensor-test",
      "name": "MySensor_Test",
      "class": "MySensorsButton"
    },

Yes you’re right it is the config of the device.
I think you mean this because

 "startingNodeId": 3

I don’t have changed this part, it was allways “3” and with sweetbee’s testscript it works with:

"nodeid": 1,
 "sensorid": 1,

But for testing I have changed the nodeid in the Arduino script and in the pimatic config to “3”.
But this was not the problem, pimatic shows allways “open”.

 "startingNodeId": 3

As far as I understand, this startingID is only the NodeID for the next NEW device when using auto-discorvery of device with setting

#define NODE_ID AUTO  //=255 *

in the Arduino sketch.
BUT: After first startup the NodeID claimed an ID from Gateway and is already stored inside the Arduino eeprom and shouldn’t change itself even after reprogramming of the arduino sketch later! Your startingNodeID is a setting inside the Plugin section, isn’t it?

On the other side, your logs showing you the right ID of your client device:

TSP:MSG:SEND 3-3-0-0 s=1,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0

For me this signs on an NodeID = 3 (3-3-0-0) and a SensorID = 1 (s=1)
I’m not shure, but think 3-3-0-0 Meaning is >> ther is a Message from NodeID 3- coming via NodeID 3 (it self) going to 0 (=Gateway)

Please try with

"nodeid": 3,
 "sensorid": 1,

AND this setting is in the device section. Every single device has it’s own NodeID setting.

@DDNRN said in MySensor V2 problem with device in pimatic:

Every single device has it’s own NodeID setting.

That means if I have a second sensor it will have an other NoteID? I have understand that I can use up to 255 Sensors on one Node, so only the SensorID is different.

Yesterday I have tested it with SensorID=3 and NoteID=3 and have changed this also in the device section from Pimatic.
The Sensor gives:

TSP:MSG:SEND 3-3-0-0 s=3,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:SEND 3-3-0-0 s=3,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:1

But pimatic shows always “opened”…

@sweebee you don’t have a solution for me?

@DDNRN
Have I understand you right that your Gateway is on MySensor V2.0 and you have Update all scripts from your sensor also to the Version 2.0?

Is anybody else here who used Gateway and Sensors in Version 2.0?

I use both v2.0 of the gateway and v2.0 sketches and it works fine.

in this line

#define NODE_ID 1

you want to define the node id but that is different in v2. It should be

#define MY_NODE_ID 1

This node id refers to the nodeid of pimatic-mysensors. The sensorid is the child id.

You should also check if the sensor type is correct. If these don’t match it will not work.

Did you try to add a new sensor using the GUI?

@rikki78 said in MySensor V2 problem with device in pimatic:

You should also check if the sensor type is correct. If these don’t match it will not work.

Did you try to add a new sensor using the GUI?

Ok maybe I used the wrong sensor type. In the scetch I used Door Contact but in the Pimatic GUI I don’t found this so I used a MySensorsButton.

@V1per

That means if I have a second sensor it will have an other NoteID? I have understand that I can use up to 255 Sensors on one Node, so only the SensorID is different.

Yes you are right, but for me a device is the physical device = arduino-node and sensor is a singel sensor at this single device.
So each arduino/esp/nrf-radio needs a separate NodeID and inside you can (but not must!) use separate SensorID for every connected sensor at this station.

@DDNRN
Have I understand you right that your Gateway is on MySensor V2.0 and you have Update all scripts from your sensor also to the Version 2.0?

No! I still use some 1.5.x Sensors while all other stuff is already 2.0, thats why I still left the Protocol 1.5.4 in my Pimatic config.
All the time, I converted part by part over several days, everything was working.
But indeed I really don’t know if its neccessary to keep 1.5.x or already can change protocol to 2.0.
Will try that next days, hopefully get some more time in the upcoming holidays.

I don’t know what else I can do…
I have changed:

  "protocols": "1.5.1",
to
  "protocols": "2.0.0",
and
  "protocols": "1.5.4",

It dosn’t help. In pimatic is the sensor now not “opend” now it is “closed”???
But allways “closed”.
The debug from pimatic and the autodiscover shows nothing from MySensor. In the log is only:

info [pimatic-mysensors]: Connected to MySensors Gateway.

Could you post the debug output once more?

@rikki78
I don’t know what debug you mean, can you please explain? Pimatic debug Shows a lot from homedino, ping ect. but nothing from mysensor.

I meant from the node (so the arduino).

And also your configuration

Here are the actual configs and logs:

#define OPEN 1
#define CLOSE 0
#define MY_NODE_ID 3
#define MY_CHILD_ID 3
#define MY_RADIO_NRF24
#define MY_DEBUG    // Enables debug messages in the serial log

#include <MySensors.h>
#include <SPI.h>

MyMessage msg(MY_NODE_ID, V_TRIPPED);

uint8_t value = OPEN;

void presentation()
{
    present(MY_CHILD_ID, S_DOOR);
}

void loop()
{
    value = value == OPEN ? CLOSE : OPEN;
    send(msg.set(value));
    sleep(10000);
}

The Console of the Arduino Software shows this:

TSP:MSG:SEND 3-3-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSP:MSG:READ 0-0-3 s=255,c=3,t=8,pt=1,l=1,sg=0:0
TSP:MSG:FPAR RES (ID=0, dist=0)
TSP:MSG:PAR OK (ID=0, dist=1)
TSM:FPAR:OK
TSM:ID
TSM:CHKID:OK (ID=3)
TSM:UPL
TSP:PING:SEND (dest=0)
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:READ 0-0-3 s=255,c=3,t=25,pt=1,l=1,sg=0:1
TSP:MSG:PONG RECV (hops=1)
TSP:CHKUPL:OK
TSM:UPL:OK
TSM:READY
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100
TSP:MSG:SEND 3-3-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=ok:2.0.0
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:READ 0-0-3 s=255,c=3,t=15,pt=6,l=2,sg=0:0100
TSP:MSG:SEND 3-3-0-0 s=3,c=0,t=0,pt=0,l=0,sg=0,ft=0,st=ok:
Request registration...
TSP:MSG:SEND 3-3-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2
TSP:MSG:READ 0-0-3 s=255,c=3,t=27,pt=1,l=1,sg=0:1
Node registration=1
Init complete, id=3, parent=0, distance=1, registration=1
TSP:MSG:SEND 3-3-0-0 s=3,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0
TSP:MSG:SEND 3-3-0-0 s=3,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:1
TSP:MSG:SEND 3-3-0-0 s=3,c=1,t=16,pt=1,l=1,sg=0,ft=0,st=ok:0

And on the ssh terminal on the Raspi I see this:

sudo screen /dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0 115200

0;255;3;0;9;
TSP:MSG:READ 3-3-0 s=3,c=1,t=16,pt=1,l=1,sg=0:1
3;3;1;0;16;1
0;255;3;0;9;
TSP:MSG:READ 3-3-0 s=3,c=1,t=16,pt=1,l=1,sg=0:0
3;3;1;0;16;0

In the Pimatic config is the following:

{
      "plugin": "mysensors",
      "driver": "serialport",
      "protocols": "1.5.4",
      "driverOptions": {
        "serialDevice": "/dev/serial/by-path/platform-3f980000.usb-usb-0:1.4:1.0-port0",
        "baudrate": 115200
      },
      "startingNodeId": 3
    },

{
      "nodeid": 3,
      "sensorid": 3,
      "id": "mysensort1",
      "name": "MySensorT1",
      "class": "MySensorsButton"
    }

But now I’m really confused… today the sensor stands “opend” so I looked at the Graph and I see that the state changed sometimes. But the state have to change every 10 seconds what the hell goes here wrong???

So after deleting the MySensor Plugin folder and a few reboots now the sensor works how expected

The thread can marked as solved.

Tanks to all who helped me!!!