-
I started using this library over the weekend, and like it a lot. I had it working for about a day without issue, but then added in some new devices, made a couple of changes, including where I did client.update(update_children = True), and now I get the following on some of the iterations of my loop, but not all. I loop once a minute querying any device with has_emeter being true and send out an MQTT message with the content. I get one of these for each device object I get data from. It doesn't happen on every loop. I think it started when I added credentials related to getting data from KP125M devices I just added today. I'm not sure what to do about this, or even where to try and catch the error. Is this bad, or can I ignore it? If not, how do I fix it? I don't see where the aio session is to close.
I can post the whole python if needed, it's not super long, but the entire thing may not be better than this function which reproduces the issue. This is on Ubuntu 24.04
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I figured it out. I missed the device.disconnect() method somehow. Adding
to the end of the |
Beta Was this translation helpful? Give feedback.
I figured it out. I missed the device.disconnect() method somehow. Adding
to the end of the
for key in devices loop
seems to have solved the problem. I will leave this here as an example for others if they encounter the same issue. This isn't included in the examples but after extensively going through the docs, it is possible to sort it out.