It seems I have similar problems as others.

[John]

Do you information from nodes appearing when you leave the gateway connected?

Maybe @hek can enlighten this a bit if the gateway still sends out a gateway ready message. Which version of mysensors are you using and have you turned on/off debug message logging?

Try to make sure that you get information in the serial monitor, when it does plug it info the pi.

[hek]

@John said:

Maybe @hek can enlighten this a bit if the gateway still sends out a gateway ready message. Which version of mysensors are you using and have you turned on/off debug message logging?

Yes, it does:
https://github.com/mysensors/Arduino/blob/master/libraries/MySensors/examples/SerialGateway/SerialGateway.ino#L107

[John]

@hek thanks!

@den2k PiDome really needs the gateway ready message. It then knows when the arduino is ready to handle data (as different arduino's have different serial available times (for example with the pro mini it is advised to wait a second before sending anything)).

So when you see the gateway ready message appearing in your serial monitor you are ready to go on the pi.

[den2k]

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.

[John]

@den2k

As you say that one of the micro's is being displayed as a leonardo is because the server has a vendor and product id mapping (the usb vid/pid).
I have checked my database with vid/pid combinations and the leonardo has id 0x8036. When i check the Arduino application boards.txt file it also says that 0x8036 belongs to an Arduino leonardo. This is in this file:

leonardo.build.mcu=atmega32u4
leonardo.build.f_cpu=16000000L
leonardo.build.vid=0x2341
leonardo.build.pid=0x8036
leonardo.build.usb_product="Arduino Leonardo"
leonardo.build.board=AVR_LEONARDO
leonardo.build.core=arduino
leonardo.build.variant=leonardo
leonardo.build.extra_flags={build.usb_flags}

As you can see, this usb pid belongs to the leonardo. Are you sure you are not using a clone an/or have you selected the correct board in the Arduino IDE while uploading your sketch? If you bought originals, check the last one.

[den2k]

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?

[John]

Try to put a delay of 2 seconds in the setup part of the sketch before anything is initialized. I have encountered a "spakerFun" ebay clone board someone used (which could be identified as a leonardo pro micro from the usb descriptors). It was with a complete different project but there sketch he used just printed out the first serial output too early.

[den2k]

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....

[den2k]

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.

[John]

Have you turned on device discovery? Currently by default everything that can do device discovery should be enabled to do so.
It is one of the security measurements taken in the server so discovery is not enabled without user knowledge.

If it is turned on, detach and attach your pro mini (give it a second of two minimal between this) and post a part of the log where you can see the driver ask the the gateway for the version number.

[den2k]

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?

[John]

The server is able to do debug logging. Could you please turn this logging on by going to: "system" > "server" > "debug logging" and switch the toggle button.

After this re-connect the serial device, turn no discovery and let the log list be filled as your screenshot shows. After a couple of minutes turn on debug logging and send me the following file "logs/system/appLog.txt" to support@pidome.org (as it may contain sensitive information so you do not want to post it online) and include a link to this thread so i know it is yours.

Cheers!