Posts made by den2k

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.

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?

I just upgrade pyserial to 2.7.

Looks like my problem disappeared. No longer getting Error decoding...bad byte issue.

THANKS!

Setup:

• Pi 2
• Serial Gateway: Pro Mini
• Sensor Node: Pro Mini
• MySensors v1.5
• homeassistant 0.8.0

Everything seemed to be working fine. Node talking to Serial Gateway, posting message to HA. But when I upgraded homeassistant to 0.8.0, I started having issues. NODE and Gateway no longer talked.

I get this error now --> Error decoding message from gateway, probably received bad byte. when I bootup HA.

Does anyone know if HA works with Mysensor v1.5?

This is probably a HA issue.

The Pro mini is now running at 0.7mA without the power LED. I've been able to program using AVRDUDE using a new AVR programmer from Sparkfun (Pocket AVR). The one on Ebay I found out needed to be programmed via AVR first.

9600 Baud works. So all ok now. Thanks everyone.

@LastSamurai When I try programming to upload an Arduino script using the Arduino IDE to the 1Mhz board @ 9600 baud, I am using my FTDI module connected to the Mini. Are you saying I need to hook up a ISP programmer... thought that was only when I needed to program a bootloader.

@LastSamurai interesting you say that 1Mhz doesn't matter that much. I don't know if it does or doesn't yet, because I cannot get it to work.

When measuring power consumption I get 4-5mA of consistent power draw. It spikes up to 25mA when the radio and Mini turn on to transmit and goes back to 5mA.

I have not removed the 3.3V voltage regulator on the Mini, so that may add to the 5mA figure, but I am no where near the <1mA that others are getting.

@Oitzu Not sure that is the issue. This is what I have in my board.txt

nomii.upload.protocol=arduino
nomii.upload.maximum_size=30720
nomii.upload.speed=9600
nomii.upload.tool=avrdude

nomii.bootloader.low_fuses=0x62
nomii.bootloader.high_fuses=0xda
nomii.bootloader.extended_fuses=0x06
nomii.bootloader.path=nomii
nomii.bootloader.file=atmega328p_1mhz_9600.hex
nomii.bootloader.unlock_bits=0x3F
nomii.bootloader.lock_bits=0x0F
nomii.bootloader.tool=avrdude

nomii.build.mcu=atmega328p
nomii.build.f_cpu=1000000L
nomii.build.core=arduino
nomii.build.variant=standard
nomii.build.board=AVR_NOMII

I've had some decent success so far getting a Pro Mini 3.3V + nRF24 + temperature sensor + 2 AAA bty working. The node is pushing temperature sensor data to my serial gateway which is connected via USB to a Pi.

The challenge is driving the node to use even lower power consumption. I am at 4-5mA on average now. This was with me removing 2 LEDs (one from Pro Mini and one from a Step up module).

I've been trying to use this method:
http://iot-playground.com/2-uncategorised/9-arduino-low-power-sensor

To create a low powered Mini running at 1MHz without much luck. When I run avrdude this is what I get after programming the board.

I believe using avrdude the bootloader is programmed correctly into the Pro Mini, but not sure because when I try to program the board from the Arduino IDE, (I've already added the special board to the board.txt file) it won't program correctly.

Any clue?

Problem solved. For those interested. The issue was the 3.3V Step up board. When the radio turns on there is a large power draw which causes the voltage on the 3.3V rail to drop. This caused the temperature reading fluctuations I was seeing. I added a large cap between the Vout / GND of the step up. Problem solved.

This is the hookup I have for the MCP9700. Hmm. Any additional thoughts? I'm going to try adding a 1uF and 200 ohm resistor and see if anything happens.

Thanks for the input. Just to clarify, are you talking the stepup data sheet?

But aren't the caps on the stepup module enough to dampen and stabilize the power. I shouldn't assume it does, but figure I'd ask.

Does anyone else have this similar issue?

When using power through a USB FTDI dongle, reading are very stable (beginning part of chart showing roughly 72F), but when I plug in just the battery source at around 11PM, the readings swing dramatically as you can see. This is my hookup minus the DPT sensor, swapped in with a MCP9700 sensor.

Yes. On the Pro Micro it did not show the Gateway ready. But, now that I using Pro Mini's it does show Gateway ready.

I traced back to Arduino, and it looks like I wasn't able to get even the Serial Gateway to work and show through the Serial Monitor, Gateway started on the pro Micro. But on the Mini the gateway at least seems to be working.

@tortoisedoc - I'm not sure why you can be "Waiting for gateway" but yet still have packets between GW and Node show up on the driver. I'm still debugging as well.

Does anyone else see this when going to the Dashboard on PiDome?

TypeError: Cannot read property 'id' of undefined
at eval (eval at (http://192.168.0.100:8080/shared/js/libs/jquery/jquery.min.js:4:4231), :62:123)
at handleJsonResultData (http://192.168.0.100:8080/shared/js/sitelibs/utils.js:320:17)
at Object. (http://192.168.0.100:8080/shared/js/sitelibs/utils.js:308:9)
at l (http://192.168.0.100:8080/shared/js/libs/jquery/jquery.min.js:4:24882)
at Object.c.fireWith [as resolveWith] (http://192.168.0.100:8080/shared/js/libs/jquery/jquery.min.js:4:25702)
at k (http://192.168.0.100:8080/shared/js/libs/jquery/jquery.min.js:6:5348)
at XMLHttpRequest. (http://192.168.0.100:8080/shared/js/libs/jquery/jquery.min.js:6:9152)

@tortoisedoc said:

but in PiDome I get "Waiting for gateway" in Gateway information page Version field.

I had a similar problem...You need to fix the Waiting for gateway as it doesn't look like it is working. What type of gateway are you using. I had a hardware issue where the Pro Micro's I was using did not work, no matter what I tried.

Is Device Discovery working?

This is what I get when I first plug in the Serial gateway (Pro Mini) into the Pi USB port.

I then turn on Enable Device Discovery on Pidome and set this to Single Device (I've also tried 10 minutes). After that I turned on the sensor Node (Pro Mini).

The Node IS NOT discovered. This is what it shows under Drivers. All the radios attached to the Pro Mini's are nRF24+ radios.

Any clues?

Finally getting somewhere.

At least with the new Pro Mini's I am now using with PiDome, it is detecting the Pro Mini Serial Gateway that is plugged into the USB port on the Pi.

Now I just have to figure out what Device Discovery doesn't see the Node I powered up, but the Driver section under messages as you can see above can see the Node.

This is all for today. Now have to figure what's next given it is not completely working yet.

Just to give an update. I was never able to get the Pro Micro's that I bought on Ebay to work. I purchase some Pro Mini. Looks like I am able to get the Serial Gateway not only detected by the Pi, but also looks like I am about to received Node data. Not completely done yet but looks promising.

I spent a bunch of time testing different boards over the last few days. Official Uno. Sparkfun Pro Mini from Sparkfun. They all work.

But not the Pro Micro clones I bought on Ebay. I reinstalled Pro Micro drivers from the Sparkfun Learn site. I've even used the Board Manager function and added URLs to 3rd party URLs under preferences thinking this official way to add boards instead of manually coping the driver into the correct directly would work. Nope!

For now, my conclusion is the MySensors code does not work the Pro Micro clones. it sounds like these boards work for others. If so, please ping me. I've test a number of standard arduino sketches and also RF24 sketches, and they work on these Pro Micro clones, but for some reason the MySensors sketches do not work.

Looks like I'm going to be purchasing some more test boards...

I did a few things.

1. Added 2 sec delay to Setup loop for the Pro Micro. Nope. Still didn't work.
2. Went off and used an official Uno. Was able to finally see the Gateway Statup
   
3. Went back to Pidome. Now cannot see new Nodes. Added. With a non working Gateway, I was at least able to see when I added a new Node, even though Pidome did not see the gateway. Now I cannot see a node....

A little update. I hooked up an official Arduino Uno I had around. This is what I see. It works! I see the gateway startup complete. which is great.

I just wish my Pro Micros...

Thanks NeverDie. I feel like that now as I plug away...

I 've got the serial gateway plugged into the PC for now, so I have a stable 5V supply and a stable 3.3V supply to the nRF24 radio. So my issue shouldn't be the voltage yet.

Unfortunately I'm not ready for battery testing yet, given not even being able to do the very basic uploading of a Serial Gateway sketch.

I purchased the 3.3v version of the pro micros so I have 3.3v coming out of VCC. I measured with a voltage meter to make sure. So I don't use any voltage regulator coming out of the VCC. I've tried with different pro micros from the same batch. Hmmm.

If you have a Pro Micro that is running at 16mHz the output from the VCC line to power the radio is 5 volts. You need to step down to 3.3v to the radio.

But I'm using batteries so don't want an extra regulatory taking up power in between.

Hmm.

http://www.ebay.com/itm/301613131022?_trksid=p2057872.m2749.l2649&ssPageName=STRK%3AMEBIDX%3AIT

I am using cheap Pro Micros bought on Ebay. I'm really not sure what the issue is. I have other sketches that work on the Pro Micro. Even RF24 sketechs passing info between radios. I have several and have swapped out the Micro and the nRF radio. Not thinking it is hardware.

As you can see, in the Device Manager. I have the SparkFun Pro Micro drivers installed on the PC and it detects the board as I plug it in.

I believe it recognizes it as a Pro Micro. I also installed the Pro Micro Arduino plug in, which is shown on the Pull down Menu. Nothing shows up when I upload the standard library/SerialGateway sketch in the Serial Monitor.

I am pulling out my hair with this. I have other threads going on other topics, but it all now boils down it seems to not being able to properly program the Serial Gateway on the Pro Micro.

Others have done it, but I cannot get it to work?

While it seems everyone else can get their Pro Micro's to work. I continue to ....

This is what I see.

1. I have the hookup as mentioned above.
2. I uploaded the library/MySensors/SerialGateway.ino sketch to the Pro Micro
3. I see nothing on the COM16 port.

I have several 8Mhz Pro Micro's and have tried different ones. Don't work. I bought these on Ebay. Very cheap. I also installed the SparkFun Pro Micro drivers, etc. as you can see in my Device Manager.

Other Sketches work. I've even had RF24 sketches working using the same nRF24 radios and pro micros. I believe it is not hardware, although can never be sure.

This is my hookup. Am I doing something completely wrong?

Pro Micro - 8MHz, 3.3V at VCC

SCLK - 15
MISO - 14
MOSI - 16
CSN - 10
CE - 9
VCC - VCC (3.3V)
GND - GND

Hi Martin,
this will sound stupid, but what is the standard pin configuration you are using on the Pro Micro to connect to the nRF24L01+? Or point me to the pin configuration you are using.

I think I've tried them all. I do have a different setup and thought I could modify the code to match... probably getting to far ahead of myself....

I am trying to program a Serial Gateway using the Pro Micro.

I'm back to basics. Thought I had the wiring down. I've followed the sparkfun tutorials to hookup the radio. but I don't think this entirely matches the configuration for MySensors unless I'm mistaken.

Reconnecting everything. Nothing yet still seems to work. Will keep trying...

Thanks.

How and where do I change the default PINS so I can hook up a Pro Micro (not Pro Mini)?

Thanks. This is helpful. Not really sure why I don't have a gateway ready message on the monitor. I'll try the double reset and see if the issue is the Micro not getting programmed correctly. The weird thing is I have one 16Mhz Pro Micro and a bunch of 3.3v Micros. The 16mhz micro say Arduino Leonardo, while the 8mhz micros say Sparkfun Pro Micro. I only use the 8mhz micros and I've been assuming the firmware on the SF ones are with the 8 sec wait time. Given with other RF24 examples and even mesh was working on the same hardware....

I'll update if I get further.

@Sparkman

I tried that. I'm pretty sure the radios and arduinos themselves work. I have several that I play with and have swapped out some - just to eliminate HW being the issue.

I'm guess it's a dumb problem that I caused....hmm

thanks for the help everyone! Just wished it was working!

I tried to check if it has anything to do with my nRF24L01+ radios.

When I go back to basics and use the RF24 Getting Started example. this is what I get.

Looking around I thought I was suppose to get a status register output on the serial monitor.

Does it mean the radios are not genuine?

I'm really pulling my hair out trying to figure this stuff out.

I know my radios works because I've used other examples to have different nRF radios send messages back and forth...

Nope.

I just finished

• reinstalling the Arduino IDE 1.6.5.
• Reinstalled Pro Micro Drivers
• Reinstalled Pro Micro PlugIn for IDE
• Reinstalled MySensors 1.5 libraries into IDE libraries
• Uploaded the Serial gateway script to the Pro Micro.
• Successfully compiled and uploaded to the micro.

Not working....still. I still don't see anything on the Serial Monitor.

What am I suppose to see on the Monitor?

I changed it to AVRISP mkll, Arduino ISP, Arduino as ISP. Didn't seem to make a difference....

Still not seeing anything on the serial monitor. After programming it successfully.

I may try deleting all libraries and try the install of MySensors again. I've seen that suggested else.

I did upgrade from 1.4 previously to 1.5. Was having problems (posted on separate thread) so thought 1.5 might help...

This is what I see.

I'm using Arduino IDE 1.6.5.

I have a Pi Controller. Do you mean I need to see "Gateway started" in the serial monitor on the Arduino IDE when I have the Pro Micro gateway connected to the PC?

Just trying to be extra clear, as it seems to be working for some many, so I'm trying to rule out stupid assumptions on my end.

If yes. I dont see anything.

I downloaded MySensor 1.5 API and believe I correctly followed the instructions....I've done this a few times already... Hmmm.

Yup. As additional info.

I also noticed on Pidome under Drivers / Gateway Info - it says waiting for gateway.

I find this strange because I plug in the gateway and it "sees" it under Peripheral.

Do I need to plug in a NODE? to have data show up on the Arduino Serial Monitor?

I did so, but still see nothing.

I see nothing.

I reprogrammed a new Serial Gateway using a new Arduino Pro Micro and nRF+ radio. Thought it might be hardware related.

I plugged in the Serial.Gateway into the Pi. Pidome "sees" it under Peripherals. I set it up like above, but under Driver Settings/Gateway info it still says "Waiting for gateway" like the above pictures.

I plug the Arduino back into the PC. I pulled up the Serial Monitor. 115200 baud. I see nothing on the monitor.

Yes. I get nothing on the Arduino IDE Serial Monitor for the gateway.

It compiles and uploads.

I understand the Serial Monitor on the Gateway, spits out a responses.

Not sure what I am doing wrong. NOOB.

Is installing the Libraries for MySensors a completely manual process? I am trying to get the Serial Gateway installed on an Arduino Pro Micro.

If I don't want to touch any of the code, it seems I need to copy a whole bunch of files manually to specific folders managed by the Arduino IDE.

I must be doing something wrong.

Example.
Copy /libraries/XXXX files into /arduino/libraries
Copy /libaries/MySensors/Myxxxx.xx files into /arduino/examples?

I also have this issue every time I reload the Dashboard. I don't believe it has any issue with Node Discovery, but I figure I add it here.

I think I saw this fixed somewhere on the forum, so I'll look at up when I get a chance.

The problem i have is while Pidome seems to know when a new Node Sensor is on the network (ie: Discovered drvices Orange notification) I cannot go any further. I try to set the Address. And it just stays unconfigured.

Here is some additional info.
After unplugging the Pro Micro Gateway and plugging it back in. The Peripheral reset, so this is what I used as settings. This was also the same settings I used before.

This is what i see in the Drivers screen. Same as before. Pidome seems unable to configure/communicate any further with the added Sensor Node.

Help! I have similar issues that I see others have. But for the life of me, I cannot seem to fix the issues by reading the forum posts.

Controller: raspberry pi 2
Gateway: Arduino Pro Micro (connected to USB port of Pi)
Gateway Radio: nRF24+ (connected to Micro)

Temperature Node: Arduino Pro Micro
Temperature Node Radio: nRF24+ (connected to Micro)

When I turn on the Temp. Node I see the following.

I then Set the Address. Using 1. I've also tried 10. I'm a noob so I don't quite know exactly if I am mapping Node-ID and Pidome correctly. I only have 1 Node.

This is what I see under Drivers.

I've read, this is a problem, because the gateway is not able to talk to the Node.

This is what I have programmed on the Arudino - Temperature Node.

Here is my Custom Device Setup