I use a few Wemos D1's with displays to provide weather information, 6 key items. Temp, heat index or wind chill, humidity, wind speed, wind gust speed and wind direction. We have severe storms and soon possible tornadoes, so it is very nice to have this available in the house and in our basement.When I was essentially running an MQTT broadcast off of my HA server everything was great. Fast forward to today and it is far from great. I have started trying to use HTTP to send commands to the ESPEasy main display unit and then I pass it to the other units with ESPEasy P2P. The second part works great, but the first part kills my HA server (RPi2) within a couple of hours.
I am using an automation to call a shell command to pass the data
Automation
Code: Select all
- id: "Broadcast Real Temp HTTP"
alias: 'Broadcast Real Temp HTTP'
initial_state: 'off'
hide_entity: false
trigger:
- platform: time
minutes: '/2'
seconds: '30'
action:
- service: shell_command.wu_temp_http
wu_temp_http: 'curl http://192.168.1.186/control?cmd=event,RealTemp={{ states.sensor.pws_temp_f.state }}'
After a couple of hours these 6 automations result in my database going offline and the system just starts acting odd.
I will fire up the automations and catch some logs if anyone thinks they may be able to help. The info gets to the Wemos units at first and then over time the Wemost units do not get some of the data some of the time. The load on the main unit does not seem high, but it does seem that the problem could be that the unit is not taking the command.
I am running the latest nightly build on the systems involved. About to the point of downgrading the main unit that RX's the data, so that I can run 2 MQTT instances and then P2P the data to the other units. But, that is a timebomb as well. Something will change in P2P and the old version will not work...
