Topics created by CrankyCoder

@CrankyCoder How far apart are the node and gateway? What is between them? Can you post any photos of of each with the wiring?

Small update. I switched to a radio from different batch and seemed like that fixed it. Saw the smart sleep message in mqtt until I went to bed. But around 4:30am it stopped again. Im going to go pull it again and see what it's outputting. I feel like I need to hook up a bluetooth hc-05 or something so i can just connect over bluetooth at this point to get the serial data lol

I suppose you are using a arduino pro mini when you speak of a newbie board. So effectively it is not easy to connect a laptop to the serial output. I don't think the arduino will reset when connecting, but it's not convenient. So to detect if it is the relayboard, can you deconnect it from the newbie board and let run the node like this. If it works now for some time, we are sure it is the relayboard somehow influencing the arduino. If it still freeze, it is not the relayboard and we must continue to debug...

So here's the latest. I checked and the PI was already set to static ip and not dhcp reservation. However, I made 2 changes and have been ok for 3 days now. i changed ports on the switch. Not sure if it mattered, but i have plenty. this is the one I think may have more impact. Since it seemed the carrier was dropping, but coming back, I started wondering if maybe something was triggering an auto renegotiation for nic speed. So I went in to the switch and have it hard set to 100 FULL instead of auto. I still have the debug running and gonna let this run for quite some time just to make sure im feeling it's ok.

@crankycoder Ok on the heater, but what I was getting at was if it is mains borne interference, appliances elsewhere might also trigger the phenomenon but you hadn't noticed as you were not in THAT room.... Sounds like you have some rogue amateur wiring there, for kitchens and bathrooms a ground wire is mandatory for safety I always understood, on a metal ballast case it provides RF shielding. Perhaps you could shield the board for your Light Module if the caps don't sort it out?

@alexsh1 the reason i am using the 18650's is the fact i have a steady stream of them coming in for my large battery packs. I have a couple hundred that aren't dead but just aren't quite up to to the standard i am putting in my big packs.

@thucar thanks ill check it out

checking it out now

not sure about in sleep mode. But here is the sensor i am using. https://smile.amazon.com/gp/product/B00Q9YBIJI/ref=oh_aui_search_detailpage?ie=UTF8&psc=1

Im using an 18650. currently it's sitting around 3.9v. Do you have a link to the proper "mysensors" way of handling watch dog? Im not opposed to trying it. Especially if it gets hung up trying to do something then maybe the WDT while it's awake may help.

@yveaux Did you find some time already to have a look at this?

@mfalkvidd I will put up a write up on what i did. Including my health check script (which may address some of the other items on how I handle the failures ect) Keepalived with the check script and health script is what I use to keep tabs and it also moves that virtual IP back and forth allowing for the same ip to stay in use and restart the binary when needed

You could give a try without reflashing nodes , just save the current binary

So, what's the answer? For those finding the thread: If you are not using battery sensors, then it's fine to make all of them repeaters. After 20 failures to send, nodes will try looking for other pathways. In that case having multiple repeaters is useful if a node fails. It might be that it takes some more space/memory on your arduino?

@crankycoder I do not know if I understood you correctly ... void request (uint8_t childSensorId, uint8_t variableType, uint8_t destination); Suppose you have a node with ID 100 sends request (1, 24); (= request (1, 24, 0)) This means that the node with ID 100 requests the information with the last value for sensor 1 with the type VAR1 that is on the controller for the node with ID 100. (not at sensor 1 on the gateway (ID 0) Ie at such request of a node with ID 100 requests value as though at itself (that last value which is on the controller). request (1, 24); request (1, 24, 0); It is the same. ps/// I understood .. on OpenHub there is no implementation of the MySensors module

any idea how often heartbeat messages would be sent?

@CrankyCoder thanks! 8-)

If you can figure out a way to control them maybe using an optocoupler, it could be an option

@CrankyCoder said in Rain Barrel Sensor: Looks like one of the versions of your code you are polling every 15 seconds. That still your interval? Yes I poll every 15 seconds and update only if there is a change, then every 15min i poll and post the results regardless of he result. This keeps the node showing as live in domoticz. I also only use the percentage as the trigger for a level change, this allows for a bit of variation before a change is recorded. You can see in the graph for the last 24hrs that it remains static.

@Jan-Gatzke I haven't messed with the pi gateway yet, but I am thinking maybe doing something like drbd (disk replication)

so my 1 message a second is literally like nothing as far as the mysensors RF protocol is concerned. Shouldn't impact at all?

Ive started out with openHAB2. I was using a Ethernet gateway and tested the mysensors binding but found the combo was too limited. I much prefer having the MQTT gateway and the data be accessible to anything that subscribes, although I also now use openHAB to republish its item changes to MQTT as well which is probably a better approach. I don't think the main new features in version 2 are very mature at the moment as well, discovered things for example get put in to a non human readable database and the web ui's are not fully functional. With that being said I'm using node red to provide node ID's and configuring items manually and since beta3 it's been solid as a rock.

wdt.h is included on Arduino IDE. This example show how it's work: #include <avr/wdt.h> int counter=0; void setup(){ wdt_disable(); Serial.begin(9600); Serial.println("Starting..."); delay(1000); wdt_enable(WDTO_8S); } void loop(){ wdt_reset(); Serial.println(counter); counter++; if(counter==5){ while(true){} } delay(500); }```

@TheoL I think I may already be using your code just can't figure out how to send messages to the node. I am using a mqtt client gateway. So I have my mqtt nodes but looking for the format of the messages to send, and then I can try to get it in to openhab.

@cimba007 Thanks for the details. Let me get you back some info. yes, my buttons are setup like the pullup example image i didn't think the multimeter would do it, but at this point i am willing to try anything I will pull my mini tonight and remove everything and do a test. my code only wakes up when button is pressed or every 24 hours. so it shouldn't come on while testing. Ill try with my code and with the sleep example you referenced. Thanks!!!!

You can put 100uf on each even 200uf would not be able to handle only one tx, so.. but you need them at least for coin cells. you would need more capa to handle tx..but the more capa the more time they take for recharging, and the recharging if big, increase internal res of the coin cell and that's not so good too; to prevent this that would need a current resistor limiter..etc a whole balance! On mine for instance, I have 100uF for coincell, 100uF for PIR and 86uf on radio. Fresh varta coincell 3.02V, after multiple presentation tx 2.85V if I remember, not so bad. but that's an homemade pcb. Another notes, it's better to use ceramic capacitor (because of leakage, if you want to optimize), and better smd, but that's not your case I think.

Hello I gave you some tips for button cell on your other thread. In addition: if you are using interrupts only then your power consumption should be extremely low, I don't think it's necessary to wake up regularly to send battery level. If you don't do it then then you have even lower consumption because the watchdog timer is turned off, my CR2032 door/windows nodes using the sleep method from MySensors draws less than 2uA, there can be no visible change in battery level except if you leave your node in a closet for one year

@scalz oh sweet. More info Very cool. Did anyone find a good location for the memory chips? I am not opposed to ali but amazon prime would be better

Just finished switching them out with 100's. MUCH better. Still having a fail on startup. looks like it's when it's sending the framework version TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=ok:0100 !TSP:MSG:SEND 1-1-0-0 s=255,c=0,t=17,pt=0,l=5,sg=0,ft=0,st=fail:2.0.0 TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=6,pt=1,l=1,sg=0,ft=1,st=ok:0 TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=11,pt=0,l=10,sg=0,ft=0,st=ok:WallSwitch TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=12,pt=0,l=3,sg=0,ft=0,st=ok:1.1 TSP:MSG:SEND 1-1-0-0 s=1,c=0,t=3,pt=0,l=0,sg=0,ft=0,st=ok: Request registration... TSP:MSG:SEND 1-1-0-0 s=255,c=3,t=26,pt=1,l=1,sg=0,ft=0,st=ok:2 TSP:MSG:READ 0-0-1 s=255,c=3,t=27,pt=1,l=1,sg=0:1 Node registration=1 Init complete, id=1, parent=0, distance=1, registration=1 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:0 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:0 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:0 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:0 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:0 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:0 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:1 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:1 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:1 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:1 TSP:MSG:SEND 1-1-0-0 s=1,c=1,t=2,pt=2,l=2,sg=0,ft=0,st=ok:1 TSP:MSG:READ 0-0-1 s=1,c=1,t=2,pt=2,l=2,sg=0:1 Connected much faster and 3 presses of both buttons all succeeded.

@tekka yes my radio module operates on 3.3V ams1117 I use the regulator to reduce the voltage 3.3V

@Jason-Brunk I am not sure but maybe you can use incoming message to listen to the NRF network. Read more about how to use incoming message here https://forum.mysensors.org/topic/4195/how-to-find-out-if-message-was-successfully-delivered

@Jason-Brunk small value resistors can do the trick but you better try two silicon diodes 1N4001 or similar in series with the power line. Each diode give you around.0.7 volt drop.

can you login to the mqtt server with any mqtt client for computer (like mqtt spy or similar)?

ah, good point on the gateways. Ill have to test it out with the mqtt-client-gateway For RS485. Do you happen to have any examples as how it's setup from a hardware perspective if you have say 3 nodes? Do you connect node -> gateway x3 or do you go node -> node -> node-> gateway?

@Jason-Brunk I would recommend going for something newer like this: https://github.com/hallard/WeMos-RFM69 there is a lora version if you want to be too innovative: (currently not working with MySensors) https://github.com/hallard/WeMos-Lora The GWs above are very small - you can choose a custom enclosure easily. PS My recommendation would be RFM69 rather than NRF24

I found that thread late last night. I read through the WHOLE thing before going to bed. I have my evening plans set for tonight. I don't have any sensors really in use now, it's just more for testing. So I am all over this!!

@NeverDie Yes, you are correct - it is based on ATMega1284P. So not relevant My point is that I'd rather stick to the datasheet rather than overclock, but that's just me. And yes I realise that Moteino is overclocking, but the size, voltage and flash are really appealing to me.

Ok I got it to work. I misunderstood how the interrupts worked. Got it now. The culprit was the if statement detecting if the state changed. Since the state was being maintained while sleep, it wasn't firing when I pushed the button. Thanks for everyones help!!

Thank you. New to mysensors still so I didn't know if there was a "framework" method thanks again!

awesome!! thank you!