Troubleshooting

The product listing for the step-up that the OP is using says: Sucks the juice out of your batteries. Sounds like it delivers on what it promises.... :rolling_on_the_floor_laughing:

@electrik Looks like you're completely correct. I don't know if I've ever used that function to manually add something to the dashboard, or if it was only long enough ago that I don't remember doing it that way. When I saw that warning about it not being editable, I thought that was an issue that I needed to address. (To me, it sounded like I wouldn't be able to turn a light on or off, for example.) However, if that is not needed, then I guess I'm set! Now all I need to do is compare my code to the example code and make modifications where necessary to make mine show up. Thank you so much!!!

Thank you so much! After using #define MY_TRANSPORT_WAIT_READY_MS 1, I was able to see something on the display. Then I started looking for why the transmission wasn't working. The problem was that the rs485 5V connection had a shaky connection.

On my test node I have enabled Echo and am using if (message.isEcho()) It is working. I have searched and searched and looked at the API docs but am still unclear : If the node sends a value, should it be able to read that same value back in the echoed message. I know I can use message.sender , message.type etc, but how would I print the whole echoed message and/or the echoed value.

Yeah I'm changing up the circuit die to inaccuracy... Is a arduino nano 5v powered from usb.....

thanks guys, ill add it to my code tonight and see how it goes

@Yveaux I'm sure it's in the forum posts somewhere but I don't have time to look for it. Maybe you could do a list of what is and isn't possible in void receive to mitigate further confusions?

So after more then 67h the gateway hangs again. This is the debug output: (di 01-09 09:58:49.398) 243740964 RFM69:SWR:ACK,FROM=31,SEQ=60,RSSI=-98 (di 01-09 09:58:49.398) 243740969 THA:SND:MSG LEN=9,RES=1 (di 01-09 09:58:49.398) 243740974 TSF:MSG:SEND,0-0-31-31,s=2,c=2,t=3,pt=0,l=2,sg=0,ft=0,st=OK:11 (di 01-09 09:58:49.585) IC<CR> (di 01-09 09:58:49.585) IH<CR> (di 01-09 09:58:49.585) 243741189 THA:DATA:AVAIL (di 01-09 09:58:49.641) 243741241 RFM69:SAC:SEND ACK,TO=31,RSSI=-71 (di 01-09 09:58:49.703) 243741246 RFM69:CSMA:RSSI=-100 (di 01-09 09:58:49.703) 243741253 THA:RCV:MSG=1F1F000A2103020B (di 01-09 09:58:49.703) 243741256 THA:RCV:MSG LEN=8 (di 01-09 09:58:49.703) 243741261 TSF:MSG:READ,31-31-0,s=2,c=1,t=3,pt=1,l=1,sg=0:11 (di 01-09 09:58:49.703) 243741268 GWT:TPS:TOPIC=ms-rfm-from/31/2/1/0/3,MSG SENT (di 01-09 09:58:49.703) IC<CR> (di 01-09 09:58:49.703) IH<CR> (di 01-09 09:58:49.703) IC<CR> (di 01-09 09:58:49.703) IH<CR> (di 01-09 09:58:49.703) 243741282 THA:DATA:AVAIL (di 01-09 09:58:49.733) 243741334 RFM69:SAC:SEND ACK,TO=31,RSSI=-68 (di 01-09 09:58:49.737) 243741339 RFM69:CSMA:RSSI=-96 (di 01-09 09:58:49.742) 243741345 THA:RCV:MSG=1F1F000A21030A0B (di 01-09 09:58:49.747) 243741349 THA:RCV:MSG LEN=8 (di 01-09 09:58:49.752) 243741354 TSF:MSG:READ,31-31-0,s=10,c=1,t=3,pt=1,l=1,sg=0:11 (di 01-09 09:58:49.759) 243741361 GWT:TPS:TOPIC=ms-rfm-from/31/10/1/0/3,MSG SENT (di 01-09 09:58:49.766) IC<CR> (di 01-09 09:58:49.767) IH<CR> (di 01-09 09:58:49.862) IC<CR> (di 01-09 09:58:49.862) IH<CR> (di 01-09 09:58:49.911) 243741466 THA:DATA:AVAIL (di 01-09 09:58:49.915) 243741518 RFM69:SAC:SEND ACK,TO=31,RSSI=-69 (di 01-09 09:58:49.921) 243741523 RFM69:CSMA:RSSI=-97 (di 01-09 09:58:49.926) 243741529 THA:RCV:MSG=1F1F000A21171642 (di 01-09 09:58:49.978) 243741533 THA:RCV:MSG LEN=8 (di 01-09 09:58:49.978) 243741538 TSF:MSG:READ,31-31-0,s=22,c=1,t=23,pt=1,l=1,sg=0:66 (di 01-09 09:58:49.978) 243741545 GWT:TPS:TOPIC=ms-rfm-from/31/22/1/0/23,MSG SENT (di 01-09 09:58:49.978) IC<CR> (di 01-09 09:58:49.978) IH<CR> (di 01-09 09:58:59.817) IC<CR> (di 01-09 09:58:59.817) IH<CR> (di 01-09 09:58:59.881) 243751420 THA:DATA:AVAIL (di 01-09 09:58:59.881) 243751473 RFM69:SAC:SEND ACK,TO=31,RSSI=-71 (di 01-09 09:58:59.881) 243751478 RFM69:CSMA:RSSI=-100 (di 01-09 09:58:59.881) 243751485 THA:RCV:MSG=1F1F000A21171643 (di 01-09 09:58:59.909) 243751488 THA:RCV:MSG LEN=8 (di 01-09 09:58:59.909) 243751493 TSF:MSG:READ,31-31-0,s=22,c=1,t=23,pt=1,l=1,sg=0:67 (di 01-09 09:58:59.909) 243751500 GWT:TPS:TOPIC=ms-rfm-from/31/22/1/0/23,MSG SENT (di 01-09 09:58:59.909) IC<CR> (di 01-09 09:58:59.909) IH<CR> (di 01-09 09:59:09.771) IC<CR> (di 01-09 09:59:09.771) IH<CR> (di 01-09 09:59:09.771) 243761374 THA:DATA:AVAIL (di 01-09 09:59:09.860) 243761427 RFM69:SAC:SEND ACK,TO=31,RSSI=-70 (di 01-09 09:59:09.907) 243761432 RFM69:CSMA:RSSI=-101 (di 01-09 09:59:09.907) 243761439 THA:RCV:MSG=1F1F000A21171644 (di 01-09 09:59:09.907) 243761442 THA:RCV:MSG LEN=8 (di 01-09 09:59:09.907) 243761447 TSF:MSG:READ,31-31-0,s=22,c=1,t=23,pt=1,l=1,sg=0:68 (di 01-09 09:59:09.907) 243761454 GWT:TPS:TOPIC=ms-rfm-from/31/22/1/0/23,MSG SENT (di 01-09 09:59:09.907) IC<CR> (di 01-09 09:59:09.907) IH<CR> (di 01-09 09:59:11.447) MQTTP topic (di 01-09 09:59:11.578) ms-rfm-to/31/2/2/0/3<CR> (di 01-09 09:59:11.578) 243763051 GWT:IMQ:TOPIC=ms-rfm-to/31/2/2/0/3, MSG RECEIVED (di 01-09 09:59:11.578) 243763059 THA:SND:MSG=00001F120203023132 (di 01-09 09:59:11.578) 243763065 RFM69:SWR:SEND,TO=31,SEQ=65,RETRY=0 (di 01-09 09:59:11.578) 243763072 RFM69:CSMA:RSSI=-98 (di 01-09 09:59:11.578) IC<CR> (di 01-09 09:59:11.578) IH<CR> (di 01-09 09:59:11.578) IC<CR> (di 01-09 09:59:11.578) IH<CR> (di 01-09 09:59:11.578) 243763088 RFM69:SWR:ACK,FROM=31,SEQ=66,RSSI=-96 (di 01-09 09:59:11.578) 243763092 THA:SND:MSG LEN=9,RES=1 (di 01-09 09:59:11.578) 243763097 TSF:MSG:SEND,0-0-31-31,s=2,c=2,t=3,pt=0,l=2,sg=0,ft=0,st=OK:12 After this, nothing happens anymore. I'm out of ideas...

@nzbaxterman You are welcome - It's a bit difficult to imagine the setup you want, but here a bit more to try and help. All sensors in the barn will need to communicate with 'something' in the barn. Due to all metal walls you may get reflections that will affect signals so moving antennas 20mm at a time to try and find the 'sweet spot' will probably help. Outdoors a 200m run will need a 500mW Nrf24l01+ or you could use lora radios. With the nrf it would be cheap and good to use a yagi (directional) antenna just for this link. You will want a yagi mounted at the barn and at the water tank pointing directly at each other. A helping hand an some walkie talkies would make this reasonably easy! Mount antennas a high up as you can and avoid any obstacles in the path between antennas (including trees). Let us know how it turns out! ;)

@mfalkvidd said in PWM control: requestedLevel = requestedLevel > 98 ? 100 : requestedLevel; Thank You @mfalkvidd it works that way! Domoticz still showing me his 99% but at least the fan is going 100%. Thank you for your help, sometime thing can get easier :)

@mfalkvidd That did it, thanks

If your Dallas DS18B20 was purchased on ebay or amazon or elsewhere other than DigiKey, Mouser, etc, it is likely counterfeit and will not work in parasitic power mode and will give a -127. Here's a sketch to help determine of the Ds18B20 is genuine and rule-out shoddy counterfeits: https://github.com/cpetrich/counterfeit_DS18B20 I wasted countless days and days with remote sensors only to find they were counterfeit.

@sundberg84 Hi, I'm not using level converters becuse I use a ProMini with 3,3V (with W5100 and rfm69hw). Maybe I have a small clue: The Interrupt Pin is high all the time. It seems that the interrupt request from the RFM Module is not processed. I cant see interrupts when I start a node. (With a working setup with ESP8266 and RFM69, the pin is low most of the time except when new packets arrive from a sensor).

@nono8223 I've this same problem... stock for days. I tried powering the radio directly with a 3.3volts regulator and capciator between GND and 3.3V pin of the nrf24 but still no luck. I don't want to duplicate posts but the details of my issue can by found here @Eme said in MySensors Raspberry Pi Gateway + Domotics Controller: Please someone help me...

@vidin you can implement the blinking in MY_INDICATION_HANDLER. There are some examples in the forum. Search link: https://forum.mysensors.org/search?term=My_indication_handler&in=titlesposts Check them out and try writing your own. If you get into trouble, just post how far you got and someone might be able to help you get further.

@pw44 and so, my first assbled gateway looks like: [image: 1597751792977-img_6624-resized.jpg] [image: 1597751803145-img_6623-resized.jpg] [image: 1597751823802-img_6634-resized.jpg] [image: 1597751837693-img_6633-resized.jpg] [image: 1597751850496-img_6632-resized.jpg] Now i will try a more robust version, with external antenna.

I have two cheapo ebay NRF24L01+PA+LNA. As has been posted elsewhere nearly all are fake. I only use one at a time for my gateway. I had to do lots of fiddling to get them to communicate with my nodes . This included shielding and using an aluminium plate as a ground plane (someone criticized this but it worked for me). Ive posted about it somewhere on here. More recently I took delivery of a shielded Ebyte module and it has worked great. I have loads of the cheap NRF24L01+ modules in my nodes. Some I have added 12.5cm antennas and some dipole antennas. It does make a difference if drop outs are a problem on the more distant ones.

@KevinT yes in general subghz radios have better range than 2.4ghz. I might have farther nodes but for example, I have one rfm69cw at 55m from the GW and it's ok, with many obstacles on the path (7x rock walls, a part of the roof is metallic, metallic doors etc). This depends on many factors of course