@rafael156 I had a similar problem, my node would stop responding when I tried to reboot it. The problem was in the fuse settings, have you checked if they are all set? What version are you using? (16,8 or 1)

@mfalkvidd thank you, that will do the job! I leave the ideia to a isReq()!

Thank you all

@rozpruwacz You are rigth, I Want GW => Node Request or Node => Node Requests, and I've seen the command type in the notes, but who can I access that command value in the code?

1;1;2;0;2;0 - Requesting Node 1 Child 1 variable V_STATUS, Who do I know that the Command is 2 (request) ?

@gohan you don't use a dummy variable (VAR_1)? So who do you know when the message arrives if it's a request?

@gohan I see, it's the same solution that i'm using at the moment, it would be nice to have a flag in the requests replay, that would allow to make a cleaner code, without having to use dummy variables.

Thank You @gohan

@gohan Ii can see the request:

    } else if (sendTime && !pcReceived) {
        // No pulse count value received. Try requesting it again
        request(CHILD_ID, V_VAR1);
        lastSend=now;
    }

But I can't seem to understand where is being processed, in the receive function no validation is preformed to check if it's a request or a actuation. In this case I presume that It's irrelevant (because is a informative node only), but in the case of a nodes with actuators, I need to know if the message that is arriving is a actuator (set) or a request.

Hello all, is there a way in the response method to check if is a request? Similar to for example the isACK method, how can I know if the message arriving is a request os if is a message that should actuate the node?

Thank you

Thank you @Nca78 @sundberg84 I think that I will redo my board to use a Temperature Sensor SI7021 and for light a foto resistance like the GM5539 (any opinion or alternatives?).

Better do it right, and I can use the sensors that I have around in tests or something.

One question, I'll use this inside a case, ok I can do holes, but will not this change the temperature and humidity readings?

@sundberg84 the idea is to sleep the node whenever possible, and when it wakes up (for example from triggering the PIR) it uses the wakeup to notify all the other nodes and go back to sleep again.

What you are telling is to use 2 Digital pins to one module? One to power it and other for the data? Is that it? I also thought about doing something like that, I would need to feed the atmega with 3AA (4.5v).

@sundberg84 thank you

So basically to keep this modules, the only thing that I would have powered by the 3V is the radio and the atmega. I planned building the PCB without using the modules, but I have a lot of them laying around and I think that it would make the PCB more useful/easy to others that plan to use it.