another sensors connection via usb ?

[Koniu]

can a nano be a node for this gate?

[mfalkvidd]

Welcome to the MySensors community @koniu

Use an usb cable. You'll want a Type A (on the rpi side) to Mini B (on the Nano side). See https://www.mycablemart.com/store/cart.php?m=product_list&c=26 for a picture of the different usb connectors.

[Koniu]

You've made my day :)))
I was referring to the code for nano

[Koniu]

Welcome @mfalkvidd

[rejoe2]

@koniu In general this is possible. Both mcu's have to be configured as a gateway, so you may base your code on the serial gw sketch.
BUT: Handling multiple GW's is not supported by all controllers and using 2 mcus with a CH340 USB-serial converter (in case your nano is also equipped with that type) may be tricky to handle in Linux as they seem to be identical for udev etc.
Wrt. controller: E.g. FHEM soports multiple GW's but will mesh all incoming data in one Node and can only use one of them as an adress for active commands like switching relays or set initial values for counters. So at least use different Child ID's for your "S"-es on both mcus

[Koniu]

@rejoe2 Thanks, it works only with different USB-serial converters - for the same mix children
@mfalkvidd cable - xD

[rejoe2]

@koniu said in another sensors connection via usb ?:

@rejoe2 Thanks, it works only with different USB-serial converters - for the same mix children

Sorry, but I don't get your point.
It also works using two CHG340-Nanos, but eg. in FHEM you best would distinguish them using the output of ls -l /dev/serial/by-path

And also when using two different converters it would in any case make much sense to use different ChildID's to avoid mixing up the data from both Nodes.

[Koniu]

@rejoe2 Two different usb-serial converters work well without additional settings.
And You're right - in any case it makes sense to use different ChildIDs