Topics created by linus72982

@linus72982 For a door sensor there is little use in 'polling' the door state from the base station; it's much more efficient to only send the state changes from the sensor to the base station. That's probably what the SimpliSafe does, so the sensors can powerdown their radios until a door's state changes. You can achieve the same thing using an nRF24 radio and wire the door contact to an interrupt pin of the AVR. The AVR and radio will be asleep at very low power until woken by the interrupt. Once an interrupt occurs the sensor will send the new state to the gateway+controller ('base station'). This scenario is very energy efficient and can easily run for a long time without replacing batteries. See e.g. this example sketch on how to achieve this with MySensors.

Nevermind, I figured it out (sort of). I deleted the serial port from device manager and then checked for hardware updates which reinstalled it. It then worked just fine for one iteration, but the serial monitor showed BinarySwitchSleepSensor output instead of gateway output. And then stopped working. I deleted it again, reinstalled the port, and immediately uploaded the gateway sketch back to it. Now it works great. My guess is that the binary sketch somehow messed up the serial comm when on the Nano? Not sure, but that fixed it. I must have forgotten to switch the port # when I was reuploading the binary sketch to my node and accidentely uploaded it to the gateway port.

Yes, that is confusing. In 2.0 the examples have been updated to use digitalPinToInterrupt instead, see https://github.com/mysensors/MySensors/commit/3433d2da7885066777bc177f073df87313b9947c

@linus72982 The GW doesn't keep track of which nodes that is connected. It only acts as a GW between your sensor network and your controller.. The presentation messages that you see in your controller, is coming directly from the node itself. Your controller should cache the node presentations. As it's the controllers job to assign node-id's they won't change if the GW is rebooted.

The regulator is directly to the left of the led. It has 3 legs on one side and 2 on the other. I use a small side cutter to cut the 2 legs and then i wiggle the regulator up and down until the 3 legs break.

@hek Thanks -- one other quick question: am I right in assuming a child sensors will only ever send "set" message types and will only be routed "req" types? For example, I'll never see a message like this: 3; 3; 3; 0; 9; etc right? Nodes would send that sort of message, but never a child: 3; 255; 3; 0; 9; etc yes? I'm assuming this because most nodes just report a setting or get set to something, they don't have any intelligence beyond that, that all exists on the child's node.

Changed the arduino.. not the radio .. from UNO to Nano (not the sensor but the gateway).. now it works...

@linus72982 You will probably get slightly better range with one of the antennas. The original antennas that come with the modules are probably 1/2 wave antennas whereas the ones on the router could possibly be 5/8 or maybe even full wave which might give you a little gain. The receiving end of the module might not see much with the added length, but where you would get the boost is when it is transmitting. I am not sure that you would want to hook up both antennas as that may hurt your SWR on the transmitting end which would hinder performance rather than help.

@linus72982 thanks. Now let the fun begin and share your idea's