Topics created by Snyfir

@Snyfir what is the return value of the sleep call? What does the debug output say? Those pieces of information will help a lot when trying to understand what is happening and why. What type of Arduino you are using would also be useful.

In all honesty, I'm not quite convinced you'd need two separate networks. Just provide the security sensors, the repeaters, the gateway and your controller - that form the security system - with some sort of ups and they will keep running until the UPS has no more power left. The none security devices will stop working when the power goes out and, unless I don't really understand your problem well. That does what I think you want to achieve? Unless you have combined a lot of sensors within a repeater it would really be my way to go. It wouldn't mean any modifications to your security hardware, because they need to be battery powered or have some sort of UPS anyway, to keep working when the power goes down. But again it's hard to judge when you don't really understand the problem some one is trying to solve.

@snyfir with this fix, everything work fine

I am use switching DC-DC the same as you to get 5V from 12V and LDO XC6206 to power NRF24 module - all work good.

I've created a lot of devices on Arduino Nano's with soft signing. You have to learn how to manage memory, and then it works great. A gateway on a nano with nothing in the code except it being a gateway, that should work fine. I've never seen that error message when I used the SIMPLE SECURITY option. Low memory warning might also not really be a problem in practise. If your sketch is empty, then there may not be much to worry about: there are no functions in your code that suddenly need a lot of memory. The only question then is how much MySensors needs which isn't globally defined. I don't know the answer to that, but someone else might. In the end I'd say: test it. If all seems to work ok, then there's really not a problem.

@anticimex said in Send secured command to the gateway: Another hack you could make which is less "hard core" is to adjust the behavior of the weak security flag to never allow "nerfing" security settings for a node. That is, even with the weak flag set, a gw will never allow a node to stop requiring signed messages. @Anticimex That sounds like a good idea for a new official feature to me? Especially if it's just one line that needs to be commented out?

@berkseo said in Node not working very well when MY_DEBUG not defined: My problem is temporarily solved(nrf5). Delivery confirmation to the controller come steadily if the file MyTransport.ccp (line 723) add: #if !defined(MY_DEBUG) wait(5); #endif based on: https://github.com/mysensors-rus/MySensors/commit/06f8083b785237b8d1b430a142fe3d9a3cd6f7ff The bug will be fix in the 2.3.2 release i suppose so

@snyfir the radio uses so much power in listening mode that sleeping the mcu will not help much. To get low power, the radio must be turned off.

@tekka said in NRF24L01 with Arduino Pro Mini at 1Mhz: @snyfir Can you run the same tests using the latest release, i.e. 2.3.1? It's working ! Thanks you very much @tekka and @mfalkvidd

@mfalkvidd I don't know i will try when the next release will get out

@snyfir You can manually write a new parent_id to the variable - _transportConfig.parentNodeId = ; ..This is not the only option