Short update from my side.
I experienced a lot of time outs with ‘homeduino’ after switching to ESPimaticRF. I used a setup with a NodeMCU as homeduino device. It was set to send and receive RF and also use a NodeMCU set as Node as second send/receive device. This set up gave me a lot of timeouts which could be ‘mended’ by restarting Pimatic.
This weekend I switched the ‘homeduino’ to a Wemos D1 min. This didn’t change anything. Without scientific proof it resulted in even more time outs.
So I looked into the wiring. Originally I had the RF3400 transmitter and receivers connected to the 5V pin on the ESP-module. I changed this to the 5V pin of my Pi (and grounded the ESP-module to a ground pin on my Pi). I have done this yesterday around 1600 hours. Since this change, I have not had to restart pimatic. RF on/off switching is working and keeps working for quit a while know (in the old setup I would have had several time outs).
So it seems this has solved my issues, though it is to early to celebrate.
For reference My Pimatic set up has several rules switching several RF lights and lights are also switched through the app (some 10 lightpoints). Besides that I have 6 temp/hum sensors that transmit every 1 minute or so, a weather station (temp/hum/windspeed/winddirection/rain) and a door sensor. I have removed all rules with dimming options.
Fingers crossed for know. I while report later this week on the progress, number of needed restarts due to time outs.
UPDATE - 30-1-18 @ 10:50 >> It is still running stable. Experienced no timeouts so far. I have now reenabled rules whitch include dimmers. I’ll wait and see how that goes.
@ruudvddries said in Announcement: ESPimaticRF coming soon:
I experience the issue with switches and dimmers.
I have changed the power supply for pimatic. But I still have homeduino connection losses.
Before I used an arduino nano. It remember it was connected on grounds to the raspberry pi. Is this also needed for a nodeMCU?
Any thoughts are welcome!