Hi,

I have installed 2 new Gateway with a Raspberry Pi and RFM69. During the last days I have moved one device after the other to the new gateways. Of course I have adapted all devices with a new firmware. The two old ESP8266 gateways were in monitoring,. What I noticed was that the less devices and less traffic, the less reboots could be detected, regardless of the Mysensor version started at 1.5 to 2.32. . The new RPi gateways are running very cool so far. The best thing is that you can monitor everything, traffic to the LAN and traffic to the RFM69.

Have a nice day
Stefan

Hi,
I don't have a solution yet. It's almost impossible to shut down all my sensors. What I can say for sure is that there is a lot of traffic on the gateway.
My solution is to redesign the entire environment. I have built a gateway with a Raspberry Pi 3B and RFM69 (new driver) and I am moving the most important devices first. I adapted the code (new rfm69 driver and less traffic).
During the last days I have done traffic test with very high load on the Pi, very stable.
The first 15 devices are running on the new gateway today. So far very good.
On the old gateway the error is still present without the 15 devices.
I am curious with which device is disconnected from the ESP gateway the error will go.

Have a nice Day Stefan

Thanks, works.
I hope the Pi gateway ist more stable than the ESP gateways . It will be a lot of work to move alle sensors to the new RFM69 driver :-)

Hello,
does anybody know how to change the Radio ID on Raspberry Pi Gateway with RFM 69

Have a nice day Stefan

Hi,
the problem was instantaneous. Power supply, ESp hardware, antenna I have renewed. All nodes ( which were possible ) rebooted. What helped was to reduce the traffic to the gate. The reboots are less but not gone.
Meanwhile I tried the ESP32 instead of the ESP8266 ( big crap ), then a gateway with a Raspberry Pi ( I didn't think it through, only a new RFm 69 driver and the Radio ID I can't set )
I think the project is really great, I have almost 60 Mysensors devices in use. The sensors work fine in almost every vesrion.
A real problem is the stability of the ESP8266 Gateway. I started with NFR24, the range was too bad. Now RFM 69 range is great. I have two gateways in use. The problems with the gateway are real ... Bu..Sh.t.
My controller runs on a VM so only LAN gateways work. Arduino and RFM69 with ethernet does not work with Soft Spi.Raspberry only new RFM69 driver.
This leaves only ESP8266 and RFM69 ...
Lets see what is comming up next.

Have a nice day Stefan

Hello,

my Gateway connected to FHEM was runnig fine, but now it Soft WDT reset comes up ervery 5 to 10 minutes.

23:28:26.427 -> 47243 TSF:MSG:READ,59-59-0,s=97,c=1,t=47,pt=2,l=2,sg=0:-62
23:28:34.556 -> 55377 GWT:TSA:C=0,CONNECTED
23:28:34.605 -> 55427 GWT:RFC:C=0,MSG=0;0;3;0;2;
23:29:06.330 -> 87131 TSF:MSG:READ,56-56-0,s=99,c=1,t=2,pt=1,l=1,sg=0:1
23:29:06.377 -> 87215 TSF:MSG:READ,56-56-0,s=97,c=1,t=47,pt=1,l=1,sg=0:147
23:29:07.533 -> 88331 TSF:MSG:READ,56-56-0,s=98,c=1,t=47,pt=1,l=1,sg=0:185
23:29:13.186 -> 93993 GWT:RFC:C=0,MSG=53;1;1;1;2;1
23:29:15.261 ->
23:29:15.261 -> Soft WDT reset
23:29:15.261 ->
23:29:15.261 -> >>>stack>>>
23:29:15.307 ->
23:29:15.307 -> ctx: cont
23:29:15.307 -> sp: 3ffffc80 end: 3fffffc0 offset: 01a0

it looks like, if there are to much messages to repeat (Sensor Device powerd off e.g.) the gateway resets.
09:49:14.768 -> 313389 !TSF:MSG:SEND,0-0-53-53,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:15.469 -> 314073 GWT:RFC:C=0,MSG=57;1;1;0;2;0
09:49:16.725 -> 315331 !TSF:MSG:SEND,0-0-57-57,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:16.825 -> 315406 GWT:RFC:C=0,MSG=58;1;1;0;2;0
09:49:18.074 -> 316665 !TSF:MSG:SEND,0-0-58-58,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:18.128 -> 316740 GWT:RFC:C=0,MSG=51;1;1;1;2;0
09:49:19.376 -> 318000 !TSF:MSG:SEND,0-0-51-51,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:28.051 -> 326647 GWT:RFC:C=0,MSG=53;1;1;1;2;0
09:49:29.299 -> 327917 !TSF:MSG:SEND,0-0-53-53,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:36.070 -> 334647 GWT:RFC:C=0,MSG=51;1;1;1;2;0
09:49:37.319 -> 335926 !TSF:MSG:SEND,0-0-51-51,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0
09:49:45.037 -> 343647 GWT:RFC:C=0,MSG=53;1;1;1;2;0
09:49:46.493 -> 345105 !TSF:MSG:SEND,0-0-53-53,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=NACK:0

I have already checked with a second Gateway that there is no hardware defect. Both gateways same behavior.
Myssensors is 2.3.2 ESP Lib is the newest.

Does anybody know this problem ?

Have a nice day
Stefan

Hi,

I don't think so, in time we have just some workarounds

Have a nice day
Stefan

Hi,

i have the same problem. Using the 2.4.2 of the ESP8266 board library works fine. All later versions not.
Ther is an other Problme with the ESP Gateway. The Wifi reconnect after a soft reboot or pushing the reset switch is not working.
The gateway is trying to reconnect until it gets power on / off .

a Modification of the MyGatewayTransportEthernet.cpp helps. Wifi will be always disconnected with the boot process.

#if defined(MY_GATEWAY_ESP8266) || defined(MY_GATEWAY_ESP32)
#if defined(MY_WIFI_SSID)
// Turn off access point
WiFi.mode(WIFI_STA);
#if defined(MY_HOSTNAME)
#if defined(MY_GATEWAY_ESP8266)
WiFi.hostname(MY_HOSTNAME);
#elif defined(MY_GATEWAY_ESP32)
WiFi.setHostname(MY_HOSTNAME);
#endif
#endif
#ifdef MY_IP_ADDRESS
WiFi.config(_ethernetGatewayIP, _gatewayIp, _subnetIp);
#endif
GATEWAY_DEBUG(PSTR("GWT:TIN:Disconnect Wifi..\n")); //----------- added
WiFi.persistent(false); // --------------------------------------------------------------------added
WiFi.disconnect(); //-------------------------------------------------------------------------- added
GATEWAY_DEBUG(PSTR("GWT:TIN:Delay 500 ms...\n"));
delay(500);
(void)WiFi.begin(MY_WIFI_SSID, MY_WIFI_PASSWORD, 0, MY_WIFI_BSSID);
while (WiFi.status() != WL_CONNECTED) {
wait(500);
GATEWAY_DEBUG(PSTR("GWT:TIN:CONNECTING_wait_500ms...\n"));
}
GATEWAY_DEBUG(PSTR("GWT:TIN:IP: %s\n"), WiFi.localIP().toString().c_str());
#endif

Have a nice day
Stefan

Hello everybody,

solved !

Interrupt configuration was needed

#define MY_RFM69_IRQ_PIN 21
#define MY_RFM69_IRQ_NUM 2

Did not work with PIN D2

Have a nice day

Hello everybody,

does any of you have an RFM69 radio running with an Arduino Mega 2560?
I do not get a paring

209 MCO:BGN:INIT NODE,CP=RRNNA---,VER=2.3.0
322 MCO:BGN:BFR
339 TSM:INIT
353 TSF:WUR:MS=6000
374 TSM:INIT:TSP OK
396 TSM:INIT:STATID=77
419 TSF:SID:OK,ID=77
442 TSM:FPAR
7656 TSF:MSG:SEND,77-77-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=OK:
7731 MCO:BGN:STP
7748 MCO:BGN:INIT OK,TSP=0
9732 !TSM:FPAR:NO REPLY
9756 TSM:FPAR

If i use same scetch, same Radio modul, with an Adruino Uno or Nano it works.

By the way, i use a levelshifter to oparate with the 5V of the Arduino on the RFM 69 .

Why i whant to ise the Mega is more Flash.

Thanks a lot

Stefan

Hi to all,

after the change to RFM69 last sunday all 7 nodes are running without any connection lost. I added an alive message every 2min to the sketch. No messages have been lost.

no news, i am using the old driver

New update, no good news
It was working for 10 hours, and after restart for another 4 hours. I will stop now the use of the RS485. It is to weak for my use case. I have spend to much time for this.
A couple of weeks ago, i switched from NFR24 to RFM 69, this is very stable. I will go for a secound RFM69 Network for this use case.

New status:
the serial gateway based on the Arduino Mega with HW Serial failed after 27 hours. Same way to fix. I needed to restart FHEM and all nodes started working without any reboot e.g.
I don't think about any bus problem.
Next try is the gateway with an esp8266. Setup is done and all nodes are online. The major difference is the serial buffer of 256 bytes.
Since i have changed my wireless nodes to the ESP8266 the failure of these nodes decreases a lot.

@rejoe2
good idea, that's what is thought meanwile, and i setup a serial gateway with an original Arduino Mega using hardware serial for the rs485. This is running now for 90 min. Let's see what happens. The serial gateway is the only one i use. All other nodes gateway are using wireless gateways.

Hi to all,

i have the same problem since i changes some node to RS485. Setup
Fhem 5.8
Mysensors 2.2rc1
Gateway Arduino Nano USB to Fhem.
Nodes 5PC all Ardunino MiniPro; Energymeter, Relay,Temp DS18B20

What I found out is, the nodes are not hanging. There is no communication to the gateway. Reboot the node does not help. After a reboot of the node pairing does not work.
Reconnect the gateway to Fhen does not help.
AFhem restart works ( shudown restart). After the restart all nodes are appearing them self.

Today I will build a new gateway, using ESP8266 and RS485.
I have used USB gateway before, with several problems. After i changes the gateway for NFR24 and RFM69 from USB to ESP8266 most of the problems are gone.

I hope this will work. If not RS485 ist history and for this case Myssensors will be exchanges to 1-Wire.

It takes one or two days to get the first results.

Have a good day

Stefan

Hello,

i have done some more test benching both drivers. Sending a command on and off.
Using the new driver is like indian smoke signs, response more than 1 sec.
I just uncomment the #define MY_RFM69_NEW_DRIVER i am in a different world
The response using the old driver is below 100ms.
By the way, gateway and node are in the same small room.

Have good time
Stefan

Hello,

here are the scetches gateway an simple actor with logs. Nothing strange, i think.
I set some values ti fixed, for testing. If i use the old driver the response is imediatly.

the scetches

0_1509659557196_GatewayESP8266_RFM69.ino

0_1509659598721_RelayActuator_TestRFM69_new.ino

the logs, i switched on / off several times

log gateway

823183 Client 0: 55;1;1;0;2;1
823199 RFM69:SWR:SEND,TO=55,RETRY=0
824244 RFM69:SWR:ACK,FROM=55,SEQ=81,RSSI=-25
824267 TSF:MSG:SEND,0-0-55-55,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:1
828216 Client 0: 55;1;1;0;2;0
828231 RFM69:SWR:SEND,TO=55,RETRY=0
829277 RFM69:SWR:ACK,FROM=55,SEQ=82,RSSI=-25
829300 TSF:MSG:SEND,0-0-55-55,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:0
832936 Client 0: 55;1;1;0;2;1
832952 RFM69:SWR:SEND,TO=55,RETRY=0
833997 RFM69:SWR:ACK,FROM=55,SEQ=83,RSSI=-25
834020 TSF:MSG:SEND,0-0-55-55,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:1
837842 Client 0: 55;1;1;0;2;0
837858 RFM69:SWR:SEND,TO=55,RETRY=0
838903 RFM69:SWR:ACK,FROM=55,SEQ=84,RSSI=-25
838926 TSF:MSG:SEND,0-0-55-55,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:0
843821 Client 0: 55;1;1;0;2;1
843836 RFM69:SWR:SEND,TO=55,RETRY=0
843883 RFM69:SWR:ACK,FROM=55,SEQ=85,RSSI=-25
843906 TSF:MSG:SEND,0-0-55-55,s=1,c=1,t=2,pt=0,l=1,sg=0,ft=0,st=OK:1
900302 TSF:SAN:OK

Log node

Incoming change for sensor:1, New status: 1
58841 RFM69:SAC:SEND ACK,TO=0,RSSI=-25
58863 TSF:MSG:READ,0-0-55,s=1,c=1,t=2,pt=0,l=1,sg=0:0
Incoming change for sensor:1, New status: 0
63559 RFM69:SAC:SEND ACK,TO=0,RSSI=-25
63584 TSF:MSG:READ,0-0-55,s=1,c=1,t=2,pt=0,l=1,sg=0:1
Incoming change for sensor:1, New status: 1
68464 RFM69:SAC:SEND ACK,TO=0,RSSI=-25
68489 TSF:MSG:READ,0-0-55,s=1,c=1,t=2,pt=0,l=1,sg=0:0
Incoming change for sensor:1, New status: 0
73443 RFM69:SAC:SEND ACK,TO=0,RSSI=-25
73467 TSF:MSG:READ,0-0-55,s=1,c=1,t=2,pt=0,l=1,sg=0:1
Incoming change for sensor:1, New status: 1

Thanks

Stefan

@gohan said in RFM69 new driver delay:

ACS enabled

What i tried is before is #define MY_RFM69_ATC_MODE_DISABLED , no change

Stefan

Hello,

i am going to change my network from NRF24 to RFM69.
Using the old RFM69 driver all is working fine. Using the new driver there is a delay on the nodes with an actor. The serial output shows that the gateway sends a request to the node, getting an acknolege the message is send to the node. This delays the actor appx 1.5 seconds. For nodes eg. lights with dimming funktion not very nice.
Is there any possibility to speed this up ?

My setup is: Fhem, Mysensors 2.2 rc1, ESP8266 Gateway - RFM69, node with RFM69

Thanks for help!
Have a good day

Stefan