Troubleshooting

@burningstone Check connections with a continuity tester and measure your voltages coming to the arduino and PIR. When checking continuity, check directly from the jack on the PIR and/or temp sensor to the pro mini terminals, and also check pins near the connections for any possible shorts.

In most home automation scenarios you usually have a (locally installed) controller software where you act on incoming data from the sensors deployed in your home. With "act" I mean everything from logging data (for graphing) to automatically send out commands to actors. I.e. If movement is detected (by a motion sensor) in a room after sunset then turn on ceiling light for two minutes. So... the controller holds all the "rules" in your building automation setup. You can have a very small MySensors setup where sensors/actors send messages between each other and the "rules" is hardcoded in the nodes. But this will soon get very messy to maintain. You'd need at least one Relay node to get this working (with hard-coded id's in the nodes). The controllers can often run headless on simple hardware like Raspberry. Check out our list of supported controllers.

@rejoe2 it is a feature currently mainly useful for gateways. Furthermore, only avr is supported, as far as I know. It has been in for over a year iirr.

I finally had some time to do some further testing. Switching to the development branch of MySensors solved my problem. I have the feeling that the link is not really stable, but at least I can see data coming in. Stef

@wallylama I already did that! :o - That's why I now need to make it all work!!! :)

Thanks for the info and confirmation! I will then move my testing setup to different frequency and the problems with coverage will resolve with repeaters. (I do also have some RFM69 units laying around, but I do not want to use them for the time being due to their bigger footprint)

Are you running the default sketch? What arduino ide do you have? What version of esp8266 library are you using?

@sentur great that you found a solution. Thanks for reporting back.

There is a problem with messages sent by gateway or received by node: you either have bad power supply for radio on gateway or bad antenna or antenna alignment or too much distance; could also be interference near the node

@gohan Thank you so much for your clarifying.

Same error here. gcc version 4.9.2 (Raspbian 4.9.2-10) PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)" Replacing printf("bcm2835_delayMicroseconds %" PRIu64 "\n", micros); with printf("bcm2835_delayMicroseconds %lld\n", micros); in file drivers/BCM/bcm2835.c fixed the issue. EDIT: It did compile, but it segfaults when I try to start mysgw Time to get a fresh copy from git EDIT2: Fix from commit in bug report fixed it.

@mljbr4 thanks for the feedback. Reference to github issue: https://github.com/mysensors/MySensors/issues/980

@Inso great work. Thanks for reporting back.

@Newzwaver When you post code, it helps out a lot if you use the code tag button </> before pasting in your code. The other alternative which is basically what the code tag button does is to put 3 tick marks ( ``` ) before and after your code. It keeps the code indented and makes it MUCH easier to read.

@martinhjelmare changed the antennas again for another design, and send the level to max, and today it seems to be stable. Proof is in the pudding, he needs to control my aqarium lights twice a day. that's the one thats missing. al my sensors are power with power regulators, so that should be good. if the issue is persisent, i will try further.

Installed development version and all working 100%. Thanks for the help.