MySensors controller with Rasberry Pi 3 & Windows IoT

[mfalkvidd]

@MrVince big welcome to the MySensors community!
The serial api is used for communication with a gateway. The api is described here: https://www.mysensors.org/download/serial_api_20

You can also look at HomeGenie, which is an open source controller written in C#.

[MrVince]

@mfalkvidd Thanks for the welcome !

I already look and studies the API. I understand a format and how build a Message but not how send it to my gateway.

I've look this https://developer.microsoft.com/en-us/windows/iot/docs/wra on MSDN to connect an Arduino to a Raspberry, but there is something I can't understand. Do I need to create a string with a good format and send it to gateway? If yes, how, and if not, what I need to do.

Maybe it's obvious and there is something I can't understand, I'm sorry if it's that

EDIT : One more thing about the API, it's to the Arduino right?

[scalz]

Hi,

I think you should start by taking a look at a Serial UART example for VS, for learning how com port session, communication are handled.
A very good exercise, could be to start by trying to code a Serial monitor. Then it should be easier to understand.
See above link from @mfalkvidd for the serial api and use it from your homemade Serial monitor, sending command, reading etc..
Or as sugested too, you could take a look how Homegenie works (serial communication, threads, database etc.)

[MrVince]

@scalz I will look thanks :)

[gohan]

Keep in mind that mysensors gw also works over ethernet and mqtt

[MrVince]

Hy everyone ! So, THIS IS WORKING ! Thanks a lot :)

Now, new problemes ! (It's not funny without)

I build a serial gateway and a motionsensor

This is my log

image url)

0;0;3;0;9 -> ok it's a gateway init
0;0;3;0;14 -> gateway is ready

but, what is the next one? Normally I will receive just x;x;x;x;x; right? what's about read: 255-255....

Thank you :)

[gohan]

take a look at https://www.mysensors.org/build/parser

[MrVince]

Ok, if I right, there is a trouble with a motionsensor who want an ID ?

Do I need to give it one, or it's done by a gateway?

[sundberg84]

@MrVince - It is done by the controller. The GW never assign ID.
You could set a static ID in the node as well.

[MrVince]

@sundberg84 It's work ! Thank you :)

[MrVince]

Hi everyone !

Let's do a check up :

• Read from a GW in serial connection : ok
• Read information when I give a static ID : ok
• Find a node who want an ID : ok
• Give an ID to a node with my controller : nope

So, the question is, if I receive '255;255;3;0;3;' my controller understand it's an ID_REQUEST and I need to use an ID_RESPONSE, but if I want to give an ID I need to build something like this :

node-id ; child-sensor-id ; command ; ack ; type ; payload

node-id : ??
child-id : ??
command : 3 for internal
ack : 0 ?
type : 4 for response
payload : new ID (ex: 101)

What are the node-id & child-id if the sensor doesn't have one?

One more time, I want to thank's all of you, with your help it's more easier to understand and I start to see the end !

EDIT : One more thing, I have an idea. I want to open a pop-up when a new sensor is on to choose for wich room is it.
Can I give an temporary ID (like 254), wait for a first message with ID 254, with a first message I can see what type of sensor is, open a pop up, and give a new ID after I choose the room?

[gohan]

the controller should keep track of the assigned IDs and respond with the following free one, I don't think you can change the ID via software, unless there is a way to change it in eeprom and reboot node so it will read it from eeprom and boot with that

[MrVince]

@gohan ok

I understand for the controller, but I think I miss something about the ID_RESPONSE

Imagine this situation:

I have just one sensor with no ID
The GW send me (the controller) : '255;255;3;0;3;' // Sensor want a node_ID
If I want to give it the ID 1, what I need to send to the gw? I think something like '255;255;3;0;4;1', that's right?

EDIT : I try and it's work now, but I need to clear EEPROM first

[carolynlawson]

Thank you for sharing the details.