Ad=s far I understand, we're speaking about radio ACK, which just confirm the right reception on the message, what could be sent. Then, that's gateway that can understand message contents. If senders returns NACK, it just means that no radio ACK has been received from the other end within timeout (set to 1500 ms with MySensors' setup, running @ 250 kb/s, with 15 retries). That's exactly what happens when sending message and receiver off. In the current issue, as you're on a repeater, you're in a good position to be in a position of receiving a message, and sending immediately another one (we can also have the same thing if implementing signature), were timing issues may happen.

SOLVED please see first post

@helvetian Thanks. I am using Domoticz as Controller. After you first start-up of node you will get a Light device, change this device to Dimmer, then in Setup-Hardware-MySensorsSetup, select Node then select Child for SleepTime and disable Ack.

@flopp electrokit is in Malmö and should be open today. Order pickup and you will have the parts later today.

@Yveaux Thanks, i will have a look at it

Hello, I have followed your build and are about to to a similar reverse engineering of a weather station but my winddirection look different and Ineed some input on how I can fix it. On my there are 8 IR leds on the perimiter and 4 IR sensitiv transistors in the middle. The outer leds are wired 2 and 2 with all the odds having common GND and all the even have common GND. So i have problem on how to turn the led on 1 by 1. Any inputs?

@bjacobse :dancer:

SOLVED I added delay(1000); here resend((lastCounterMsg.set(hwRainVolume,2)),10); delay(1000); }

@Yveaux Thanks. I used alcohol to put the silicone back. I have add that information in the post

@Yveaux I don't know because the battery was old when I started to use it. Home made pcb. Report every 30 minutes. No cap on battery. Take a look at this graph. This may be a new battery, don't remember. Has been running since 1/4 2016 [image: 1483800257774-img_3616.png]

@Reza: I tried to reproduce the errors shown by your log. Part of the errors could be reproduced. So if you are leaving range of stable connections, node will try to get an new parent (within range). So broadcasting for new parent is "normal". As long as there is no valid connection node will reject sending messages because "Transport Not Ready". So this is "normal", too. Leaving range resulted in one or two NACK, then connection died quietly. I never got this amount of NACK you got. I could not reproduce !TSF:MSG:LEN:0!=8 or something similar. This means the message has been crippled (possibly). Reviewing logs and testing on my configuration revealed no clue to defective Chips (in regard to NRF24L01). Chips could be fake though, but at least software functions seem to be ok. Fake NRF modules are reported to have very varying (worse) connection distances, sometimes down to a few (possibly only one) meter(s). Maybe -- may be not. There are two major differences between our setups. I am currently not working with ACKs, I will test this tomorrow. Second - I got no actual relays connected (only LEDs). You reported transmission break down simultaneously to pressing switches at higher rate. Are you supplying DC for relays from Arduino or from separate DC-supply? Have you made any arrangement preventing inductive spikes (ferrite rings, self-induction recuperation diode etc) ? If you simply unhook your relays and try again - you get better results? (since your non-inductive sensors work well). If this will turnout true - you may give Solid-State-Relais a try.

Yes Glædeligt jul :-)

@nikgru extensive teardown of the lamp (German, but you know how to translate) : https://m.heise.de/make/artikel/Ikea-Tradfri-Das-steckt-im-Smart-Home-aus-dem-Moebelhaus-3597295.html?wt_ref=http%3A%2F%2Fhackaday.com%2Fblog%2F&wt_t=1486396685063

I think I found it. if (interval<10000L) { // Sometimes we get interrupt on RISING return; } It seems to be that my interrupt is to quick. above code is default if I change to if (interval<35000L) { // Sometimes we get interrupt on RISING return; } it will calculate Watt as I think it should be. I will let it run for a week and see if kWh is OK now.

@mfalkvidd :dancer: