Heollo @bpwwer,

Not sure where to turn as I seemed to be having problems with both Vue and YolinkLocal.

I installed 6.0 a last weekend. Since then Vue works for about 3 days then doesn’t update values or control switches. A reboot fixes it for another few days.

This morning, I had PGx open in Eisy_ui and in the bottom right side a red warning kept popping up, something about Slot 13 (Vue) was...I am sorry I don’t remember exactly what it was but it seemed to indicate Vue was using too many resources to quickly, is how I interpreted it..

Alternately another warning about slot 15 (YolinkLocal) was struggling as well.

 

Unfortunately, I didn’t capture when vue became unresponsive, but I think I did capture today's events.

I reboot and so far so good.

I will also add that whatever is going on seems to have affected other plug ins today, devices turning on and off by program were taking way to long.

 

I am on 6.0.0_04

With everything up to date as of yesterday.

I have PM’ed you the logs from today.

Thank you!

-Tim

What I see in the log is that the Emporia server is returning 500 - internal server error for all the requests between 12:15am and 7:25am. During that time nothing will get updated since the server isn't responding with anything but the error. After that, the server starts responding with data and continues to do so through the end of log. It doesn't look like the plug-in was restarted at 7:25.

A 500 error is a pretty generic error. It simply means that the server encountered an error while trying to handle the request. Since the server is able to handle the requests from the plug-in normally, this tends to rule out the plug-in sending an invalid request.

It's possible that the Emporia server is overloaded and doesn't have the resources to handle the request, but I believe there are other errors it could return to indicate that. Most likely is that the server handling the request simply can't connect or access the data from their internal database, which generates an error and that's passed back to the plug-in.

Most of the errors showing up the log are coming from the libraries used by the plug-in to make the request. The plug-in is throwing one error too, and I could trap that, but it won't be able to handle all the other errors that get logged when the server doesn't respond properly.

From this log, I don't see anything that would indicate that the plug-in would be causing any resource issues with PG3x or IoX. In fact, when these errors are occurring, it's putting less load on PG3x and IoX because it's not sending any status updates to them.

Thank you for looking into it for me.I

I will keep an eye o other plugins.

Thanks again,

Tim