Allright, I have replaced the nrf chips to those with + and... that was it, everything is working very well now
Here they are, freshly handmade

@Nca78 The euro version doesn't. Just the ULN2003A.
Unfortunately, I can't attach images for some unknown reason.

Finally
That's a single button switch.

@Flor-Sanders I think you maybe should choose not USB but Ethernet gateway in domoticz.

@rozpruwacz said in Sensebender Micro Battery Code:

@Tigroenot said in Sensebender Micro Battery Code:

consumption

OK, i upload my code to github and share it with all, but I must warn that it is work in progress and it will change a lot and is not tested very well (just on my 3 different sensors).
@Tigroenot 3uA ? hehe my multimeter showed 4uA on 2000uA range (the lowest i have) for a door/window sensor (atmega + nrf24 + battery voltage divider + pull up resistor on one of the gpios + all powered with directly from cr2032 battery), but probably the measurement error is significant ...

No error, it's just a matter of faith

@rozpruwacz Sure, please share. It will all help a lot to see from the other perspective all the smart lifehucks and to finally get to desirable 3uA sleep consumption

@tonnerre33 well, the reason for that is that livolo switch power circuit board contains two power circuits
One is a standby power which feeds the MC while all lamps are off and another one is the circuit that powers the whole system while at least one of the lamps is on (for two lamps switch).

Here it is. link

Hope it will help.

@meddie As far as I'm concerned you should use the sleep() function. Also it's a good idea to use internal oscillator down to 1mhz and set the BOD to 1,8v. Also I think reading the temperature and humidity once in 5-10 minutes is enough,and transmit if it changes. There is a thread of the forum about cr2032 temperature node.

Well, what I did is swaped the radio on the gateway, added capacitors (10-200uf), swaped the nrf chip on the nodes (nrf+ and nrf), added 1M resistor to the node for radio back compatibility, moved nodes closer to the gateway and further from it, flashed the repeater node (now it's node 10 again) with repeater function disabled.

In the end, I've got three new nodes that talk to controller ONLY through repeater node (the repeater node is further from the gateway then the new nodes). Clearing the routing table on the repeater node doesn't help, erasing eeprom of the repeater node makes it change the node ID and after restarting the other nodes they bind to the repeater again.
Strange thing is that the node 10 is with MYSBootloader (which has nrf chanel 76 set) and it talks straight to the gateway. The nodes (8,12,13) have the same bootloader and nrf chanel set to 76 and are not recognised by the gateway as soon as there is no repeater node 10.

@gohan said in Node doesn't work without repeater:

Did you restarted the gateway so that all nodes presented again? It is actually kind of weird since quite some people had issues about the nodes trying to connect to low signal gateway even if repeater had better signal.

Not only have I restarted the gateway, I have reinstalled it, now it's latest development branch.
Now I have built one more node, burned the same 1.3 MYSBootloader, and it doesn't show up on the network at all. Static parent ID and set node ID don't do a thing.

314689 TSF:MSG:SEND,255-255-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
316700 !TSM:FPAR:NO REPLY
316702 TSM:FPAR

The gateway works normally, it gets the data from similar nodes that are further that this new one... I'm very confused...

Maybe it's somethig to do with the nrf chanels? MYSBootloader? All my nodes are the same...

The range is not the issue because I tried to move it closer to the gateway, but untill I power on the repeater node it didn't work.

I sent C_INTERNAL, I_DEBUG, E to node 10, is has reset it's ID and became no 11, and after that nodes 2 and 12 starter to work through node 11. Damn it. I reset the ID of node 2, it became node 8 and continued to work through node 11. Sh*t!
Now I've got two nodes that just want that bloody repeater node 11 and don't want to deal with the filthy gateway

@sundberg84 said in Node doesn't work without repeater:

@Tigroenot said in Node doesn't work without repeater:

Please, explain it to me, shouldn't the node find another parent if the repeater is offline?

It should - and I think the limit (was before atleast) is 6 failed messages and the it should search a new way/route.

It looks like it does try to find a new way (2-2-255 instead of 2-2-10) but doesnt get a reply. Maybe the routing table in the GW still is going trhough the repeater?

The repeater is fisically off. I can see the routing table through the MYSController. Tried to clear it - doesn't seem to work.

Here is another attempt. I downloaded the latest stable 2.1.1 and here is the output:

0 MCO:BGN:INIT NODE,CP=RNNNA--,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSF:SID:OK,ID=2
16 TSM:FPAR
16 TSM:FPAR:STATP=0
18 TSM:ID
20 TSM:ID:OK
20 TSM:UPL
59 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=0,st=NACK:1
2066 TSM:UPL
2103 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=1,st=NACK:1
4112 TSM:UPL
4149 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=2,st=NACK:1
6158 TSM:UPL
6195 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=3,st=NACK:1
8204 !TSM:UPL:FAIL

475289 TSM:FPAR
475291 TSM:FPAR:STATP=0
475293 TSM:ID
475295 TSM:ID:OK
475297 TSM:UPL
475334 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=8,st=NACK:1
475770 TSF:MSG:READ,12-12-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
475779 TSF:MSG:BC
477343 TSM:UPL
477380 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=9,st=NACK:1
477872 TSF:MSG:READ,12-12-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
477878 TSF:MSG:BC
479389 TSM:UPL
479426 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=10,st=NACK:1
479977 TSF:MSG:READ,12-12-255,s=255,c=3,t=7,pt=0,l=0,sg=0:
479983 TSF:MSG:BC
481435 TSM:UPL
481472 !TSF:MSG:SEND,2-2-0-0,s=255,c=3,t=24,pt=1,l=1,sg=0,ft=11,st=NACK:1
483481 !TSM:UPL:FAIL```