Best posts made by flyswiftly

I can happily report that the boot issue I had has been resolved. It turns out I have 2 nano based sensors to use that are basically the same hardware. However, one of the nano's uses the ch340 serial port and the other uses the ftdi. The ftdi one is the one I had loaded the gateway sketch on. I reloaded the gateway sketch on the ch340 based nano, and it was able to register correctly on the pi during boot.

I found several references to grounding pin 26 ( test ) of the ftdi chip, but that wasn't an option since I didn't have any of the equipment here.
https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=59420

I also found a good reference about creating a udev rule to generate an alias device name in case the usb number changes after a reboot. This may come in handy for some folks.... http://rolfblijleven.blogspot.nl/2015/02/howto-persistent-device-names-on.html

Horst

Thanks for the great explanation. I'll have the chance to see how it works next week. I'll report back how it comes together.

I have a partial success. It was very easy to add the serial gateway and configure it under HA. I can now monitor both buildings with MySensors. They have different frequencies and don't interfere with each other.

The one issue I still need to solve appears to be a Hasspian ( Raspian ) issue where the serial GW ( arduino nano based ) won't register properly as a usb device on reboot. I need to physically unplug and replug the arduino for it to show up and be usable. In searching around so far, I've found it may be related to the arduino showing as a usb 1.1 device. I've tried a few things, but need to study up and continue troubleshooting. It's likely not really relevant to this forum anyway.

FWIW, I did try extending the one MySensor's tree using repeater mode in the nodes, but it proved to be unreliable, likely due to the distances and walls in the way.

Thanks again for the help,
Horst