I’ve the same issue, although occasionally when I restart Home assistant after removing it from the configuration and not using that component it works for a period of time. Sometimes 20 minutes to up to 8 hours (only set it to retrieve Electricity).
Previously on versions I think from 0.91 it stopped working and rebuilt my raspberry pi since but still can only get it working for a short period of time. I’m using virtualenv and python 3.5.3
When the loopenergy component stops sending any updates parts of the home assistant interface stop working (such as edit and remove component in the interface) or restarting home assistant from the configuration. so have to force stop the daemon to get it working again.
One time when I enabled both the electricity and gas collection after not being on for weeks it then caused my PC (not the raspberry pi running home assistant) to be unable browse to the https://www.your-loop.com/user/login page like it my internet IP (shared with the raspberry pi) was being throttled/denied,
Could it be collecting the information from the website too aggressively it is throttled loop energy cloud service side?
That’s interesting. I’m not getting the throttle… I can still access it from other machines on my network just fine.
I also don’t get the home assistant lock ups (I can still use all items on the interface).
I thought I got it working by changing the ’ to " around my keys so it would throw an error on restart and then changing them back and restarting again. It only worked for 4hours on my electricity sensor but not at all on my gas and is not pulling through new values.
It would be great if we could get this working again. I thought about trying to use it to trigger the house being empty (if < Xkwh usage over Xtime then make me as away).
I don’t get it all the time, and when home assistant locks up it’s only certain components like edit the visual configuration, attempt to add/remove item and if you click Save it gets stuck.
However I tried another approach by adding the following to the logging:
logger:
default: warn
logs:
homeassistant.components.loopenergy: info
I had to restart the raspberry pi as well and could get the loopenergy to work for around 40 minutes before it reported;
2019-05-28 20:00:51 WARNING (LoopEnergy Event Thread) [pyloopenergy.loop_energy] No updates for 60 - reconnecting
2019-05-28 20:00:51 WARNING (LoopEnergy Event Thread) [pyloopenergy.loop_energy] Retrying socket connection
2019-05-28 20:00:52 WARNING (LoopEnergy Event Thread) [socketIO-client] www.your-loop.com:443/socket.io [connection error] recv disconnected by SSL ([SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:2090))
2019-05-28 20:01:08 WARNING (LoopEnergy Event Thread) [pyloopenergy.loop_energy] Retrying socket connection
2019-05-28 20:01:09 WARNING (LoopEnergy Event Thread) [socketIO-client] www.your-loop.com:443/socket.io [connection error] recv disconnected by SSL ([SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:2090))
2019-05-28 20:01:25 WARNING (LoopEnergy Event Thread) [pyloopenergy.loop_energy] Retrying socket connection
I think so - I forgot to save the log entries so couldn’t see for certain, but now after multiple restarts it’s coming up with
2019-06-08 09:14:54 WARNING (LoopEnergy Event Thread) [socketIO-client] www.your-loop.com:443/socket.io [connection error] recv disconnected ([Errno 11] Resource temporarily unavailable)
2019-06-08 09:14:55 ERROR (LoopEnergy Event Thread) [pyloopenergy.loop_energy] Could not connect to https://www.your-loop.com
2019-06-08 09:14:56 ERROR (LoopEnergy Event Thread) [pyloopenergy.loop_energy] Please check your keys are correct. Terminating
So I’m going to leave it unconfigured for a while and check a later time. It does still let me log on via another machine on the same network to the www.your-loop.com website though.
If it’s easy to do a test from scratch or try the hassio version?
Log Details (WARNING)
Sat Jun 08 2019 10:53:56 GMT+0100
(GMT+01:00)
www.your-loop.com:443/socket.io
[connection error] recv disconnected by SSL ([SSL: SSLV3_ALERT_BAD_RECORD_MAC] sslv3 alert bad record mac (_ssl.c:2488))
Sorry if formatting is messed up, copying and pasting from the log on a phone is a nightmare
Does look similar to the message I received if I recall - not sure if it’s a client or server side issue. Have you ever logged an issue before in HA? I think it’ll be good to say the problem happens on hass.io and hassbian 0.94
Had my loop turn up today, fitted it, added the component and then proceeded to see the same errors above about checking my keys are correct.
Confirmed they’re correct as I’ve succesfully used the secret/serial on the pyloopenergy python module seperately.
I imagine so.
Although I’m not up to speed with all the back end so not sure how to check the pyloopenergy module so will take your word for it
Previously people have been able to work out what’s wrong and offer ways of cobbling a fix together while we wait for an official fix to be pushed through, however this time it seems more difficult.