Last night the api for Emporia Vue went down, came back up this morning. It seems I was not the only one, there were some reports on their forum. I waited a couple of hours after it was back up but the Vue plugin did not seem to connect back up to the emporia server, at least none of the values were ever updated in IoX. 

Once I restarted the plug in all the values repopulated in IoX and it has seemed to run and control emporia switch plugs just fine.

I went to look at the logs but they never populated in PGx. I do have rolling logs from PGx but not sure what I am looking for.

PGx f/w 3.2.16

Vue 1.0.26

IoX  5.7.1

If you would like to look at the logs, please let me know where to send them.

Thanks!

Tim

Mine is not working either.  The error that I think is the issue is:

2023-11-19 10:12:10,140 Thread-2   udi_interface      ERROR    vue:parameterHandler: Discovery failed: 500 Server Error: Internal Server Error for url: https://api.emporiaenergy.com/devices/132567/locationProperties

I think something was up with the Emporia api server.  I had a similar problem last weekend that resolved itself.

Edited November 19, 20231 yr by tmorse305

Thanks!

Did you restart the Vue node server after Emporia was back up and running?

Mine started working after restarting the node server.

I had tried a restart a few times this morning but no luck.  When I saw your post I tried it again and it's now running.

6 hours ago, tmorse305 said:

Mine is not working either.  The error that I think is the issue is:

2023-11-19 10:12:10,140 Thread-2   udi_interface      ERROR    vue:parameterHandler: Discovery failed: 500 Server Error: Internal Server Error for url: https://api.emporiaenergy.com/devices/132567/locationProperties

I think something was up with the Emporia api server.  I had a similar problem last weekend that resolved itself.

This looks like it happened during device discovery.  If device discovery fails, the node server will simply give up.   The most common reason it would fail there is because the username/password isn't working and it doesn't really make any sense to keep re-trying.  

So in the case where the service is down and the node server tries to start, you will need to restart the node server after the service is back available.  That's pretty much by design.

All of the actual authentication is handled within the third party library that the node server uses. I'm not sure if that can handle the service going down or not.