I'm using this example.
After B4J get connected for the first time on NODE MCU (ESP8266), everything work as expect, but when B4J client get disconnected, ESP8266 fire timer_tick event on about every 5 seconds (timer is on 1000ms), also ESP8266 don't detect client is disconnected. When I start again B4J connection is established but no data in logs on both devices. in B4J Successful is True, but there is no response from ESP8266. When I click reset button on ESP8266 everything start to work again until B4J client is disconnected again and then again after connection nothing in logs, timer tick event on ESP8266 fire on about every 5 sec instead of 1 sec. I have tested on two NODE MCU board and get same behavior.
Edit:
After client get disconnected and reconnected again, there is no data in communication for exact 10 minutes. After data start to flow, Timer_Tick fire on every 1 sec again.
Anyone know why is all behaving like this?
After B4J get connected for the first time on NODE MCU (ESP8266), everything work as expect, but when B4J client get disconnected, ESP8266 fire timer_tick event on about every 5 seconds (timer is on 1000ms), also ESP8266 don't detect client is disconnected. When I start again B4J connection is established but no data in logs on both devices. in B4J Successful is True, but there is no response from ESP8266. When I click reset button on ESP8266 everything start to work again until B4J client is disconnected again and then again after connection nothing in logs, timer tick event on ESP8266 fire on about every 5 sec instead of 1 sec. I have tested on two NODE MCU board and get same behavior.
Edit:
After client get disconnected and reconnected again, there is no data in communication for exact 10 minutes. After data start to flow, Timer_Tick fire on every 1 sec again.
Anyone know why is all behaving like this?
Last edited: