Got this to work. Very nice.

Hi all,
I'm following this thread and have upgraded to MySensors v1.5 and get the following error. Version mismatch.

It looks like the Protocol version is 1.4.

Does the Raspberry MySensors Gateway support v1.5 or only v1.4? Any ideas on how to fix?

Got this to work. Very nice.

Does wifi work? It is likely that it is also pretty bad. 2.4GHz can be horrible for multiple reasons which you cite. Its already over saturated in most places so 5GHz for WiFi is the way to go. But for you wireless may not work. You could try using something with 433 MHz or sub 1GHz radios if you really need to go wireless. rfm69 support is baked into mysensors so if wireless is a must, I'd look at that. nodii may work if something small and integrated is needed. But it may be better in your case to go with a wired connection (ie; powerline with ethernet shield) as I've seen lots of issues with concrete building not supporting wireless at all.

I'm looking for some advice. I created a board for my own use to work with mysensors a long time ago and have continued to improve it. Others liked it so I began selling it on my site. We now want to introduce it to more people - so should I upload it to the openhardware.io community? I'm not exactly sure about this.

The design itself is based on ATMega32u4 with RFM69 radio options. I like RFM69 better vs nRF24 for distance. 2.4GHz is also pretty crowded. By the way - Mysensors just continues to get better. I love having all these controller options. Here is a picture of the board. We like yellow boards because they are sunny!

A 32u4 based Arduino board will be more expensive vs a 328p board. That is for sure. But I find some advantages with going the 32u4 route.

1. a big one on my list is support for an attached rechargeable Lipo battery and the recharging of that battery through the onboard microUSB port. If rechargable bty support is not required, this may not matter. Of course you can always detach the LiPo and charge separately, but I like the convenience, especially when nodes are installed and a pain to move.

2. back to cheaper. to me its a toss up. By itself the 32u4 chip is more expensive vs the 328p but if the number of nodes is low you need to factor, you paid for a separate FTDI programmer. In large networks, the extra costs savings per node will be significant but with smaller networks negligible.

Also, I just like the simplicity of one connector for charging/programming. Plus, no ugly FTDI pin headers on my nodes.

Not sure if this compelling for everyone, but I like it.

So back to the original question. Does a 32u4 Arduino board work WELL with MySensors? I know the RFM69 library that I plan to use supports 32u4 MCUs.\

thanks.

I designed a ATMega32u4 + RFM69 radio PCB for my own use and I wonder if the 32u4 chip has been used or tested with MySensors.

I started a thread many, many months ago where I was testing a Pro Micro board with MySensors, and never got it to work. Pro Minis worked just fine.

I see everyone using Nanos and Micro with the ATMega328p chip, but almost nothing at all with the ATMega32u4. and I wonder why?

Before I start down that road, I figured I'd ask.

weird. Permission Denied problem again.

What is the USER : GROUP that is needed for this to work?

Solved my own problem. Using the following command did the trick.

sudo chown -h pi:pi ttyUSB20

Noob question. Any one have an idea on solving the "Permission denied" error.

@hek I'm running a custom 1Mhz build bootloader on a Pro Mini for the Sensor side. This was paired with the standard Serial Gateway running on another Pro Mini with v1.5 on both gateway and sensor. That setup was working. But I moved over to using the Pi gatway+nRF24+ radio and have this issue. I don't believe the hookup is the problem. I've seen the 0 readings before, and that usually meant node side issue or uninitiated Gateway. I have not changed the Node, so it must be the Pi gateway that is the problem. Any thoughts on what to test?

@alexsh1 I know the sensors are on v1.5. As for the Raspberry Gateway, it looks like based on the info here, that is running v1.4.