Disconnects from meter for days at a time
Opened this issue · 2 comments
rehanson commented
This integration is great when it's working. However, every couple of weeks or so, it will stop reading data from the EMU-2 and report 0 kWh for a few days. Eventually it will start reading the EMU-2 again, and all of the energy usage that was missed while disconnected will show up as a huge usage of energy in a single moment. It makes it difficult to read and analyze our power usage over time.
rehanson commented
I get several occurrences of this error when disconnected:
2022-09-20 11:24:04.042 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:24:04.042 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:24:34.043 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:24:34.043 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:25:04.043 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:25:04.044 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:25:34.044 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:25:34.045 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
2022-09-20 11:26:04.045 ERROR (MainThread) [custom_components.rainforest_emu_2.emu2] issued command while not connected
rehanson commented
This issue hasn't happened to me in a while. One thing I always do now when I restart Home Assistant, is check the Rainforest EMU 2 entities and make sure they are reporting properly. If they aren't, I usually just need to restart again to get it working again.