elmicha

You don't even need to edit RFM69.cpp, you can set the two values with RFM69::writeReg() after RFM69::initialize(): ``` radio.writeReg(REG_BITRATEMSB, RF_BITRATEMSB_38323); radio.writeReg(REG_BITRATELSB, RF_BITRATELSB_38323); ``` These constants are defined in RFM69registers.h, so...

I don't think I did send something, but I didn't have debug nodes at all of the four pushbullet out nodes (now I have them). I have only one pushbullet...

Yes, that's the part where I'm still struggling with. I now put the name1 inside the comment for case 7b2, which seems to make more sense. I have a few...

I would love to remove these markers and the stderr messages, but I think the code is not yet ready for prime time, so I think it would be better...

I had the same problem with the latest version: ``` 2016-09-30 22:49:22,938 - INFO - New run started... 2016-09-30 22:49:22,938 - INFO - Log message: INFO level set. 2016-09-30 22:49:22,938...

Maybe you can add a feature that opens the Signal desktop instance every 29 days, if it has not been opened in the meantime? Or save some token somewhere to...