I just installed this plugin. I bought some Emporia power monitoring plugs, configured one (working fine in their phone app). After setting up the account name and password in the plugin, it's not seeing the device. I'm getting the following in the error log. Any hints as to what might be wrong? I'm running on the latest versions (IoX 6.0.4, PG3x 3.4.9)

Now I'm seeing the same messages but each one repeated 4 times, on 4 lines.

2025-12-26 20:33:17.369 Thread-2 (parameterHandler) udi_interface      ERROR    vue:parameterHandler: querys is type <class 'query.Query'>
2025-12-26 20:33:17.744 Thread-2 (parameterHandler) udi_interface      ERROR    vue:parameterHandler: Discovery failed: 400 Client Error:  for url: https://api.emporiaenergy.com/devices/544523/locationProperties
2025-12-26 20:34:09.596 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message longPoll
2025-12-26 20:34:09.597 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING longPoll
2025-12-26 20:34:09.597 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS longPoll message {} from Polyglot
2025-12-26 20:34:09.670 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-12-26 20:34:09.671 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-12-26 20:34:09.671 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-12-26 20:34:17.751 Thread-2 (parameterHandler) udi_interface      INFO     vue:parameterHandler: Logging in to Emporia Cloud
2025-12-26 20:34:19.681 MQTT       udi_interface.interface DEBUG    interface:_message: QUEUING incoming message shortPoll
2025-12-26 20:34:19.681 Command    udi_interface.interface DEBUG    interface:_parseInput: DEQUEING shortPoll
2025-12-26 20:34:19.681 Command    udi_interface.interface DEBUG    interface:_handleInput: PROCESS shortPoll message {} from Polyglot
2025-12-26 20:34:20.883 Thread-2 (parameterHandler) udi_interface      INFO     query:__init__: Query class initialized
2025-12-26 20:34:20.884 Thread-2 (parameterHandler) udi_interface      ERROR    vue:parameterHandler: querys is type <class 'query.Query'>
2025-12-26 20:34:21.326 Thread-2 (parameterHandler) udi_interface      ERROR    vue:parameterHandler: Discovery failed: 400 Client Error:  for url: https://api.emporiaenergy.com/devices/544523/locationProperties

Edited December 27, 2025Dec 27 by Guy Lavoie

@Guy Lavoie have you installed the Dev Package in the admin console? That use to be a reason for failure before and worth a try.

Well I already had the development packages installed, but then I thought that maybe they didn't get updated along with the OS update that came with IoX 6.0.0 so I clicked on Install Dev. Packages again (with a tail -f on /var/udx/logs/log to see if anything happened). It did in fact update lots of "14.3" files. Update successful. Then I restarted the plugin, and the error remains the same:

2025-12-27 10:07:36.821 Thread-2 (parameterHandler) udi_interface ERROR vue:parameterHandler: Discovery failed: 400 Client Error: for url: https://api.emporiaenergy.com/devices/544523/locationProperties

Sorry I'm not a programmer but it looks like something is wrong with your location settings with Emporia maybe try going through the Emporia app and check/chang your location to see if it helps.

Well my location settings look good. Right geographical location and time zone.

Other things I've just tried: setting up the plugin on another eisy. (running the same versions), adding a second Emporia plug in the app. Getting the same error, on both eisys.

Does anyone else have this running ok on a eisy with 6.0.4?

I just performed a restart of Vue in PG3 and I'm getting the same error and it will not connect. Either Emporia is having problems or they changed something and it will require a code change to get things working again. My Eisy is on 6.0.3_3 so I guess we will have to wait for @bpwwer to take a look.

8 minutes ago, tazman said:

I just performed a restart of Vue in PG3 and I'm getting the same error and it will not connect. Either Emporia is having problems or they changed something and it will require a code change to get things working again. My Eisy is on 6.0.3_3 so I guess we will have to wait for @bpwwer to take a look.

Misery loves company! Seriously though, that's "good news", in that it appears to be something external. Interesting that just a restart of your otherwise already working system caused it to fail in the same way. The fact that it's failing when getting location properties seems to indicate that it's something it only does once, upon startup, like a discovery process.

We'll wait to see how it plays out.

Thanks for checking this out (and unfortunately breaking yours)!

The plug-in uses a third party library to interface with the Emporia servers. 4 days ago, this issue was raised for that library:

Yesterday, my code that's been running for a long time started failing. It looks like its in populate_device_properties. The error is that that it can't get the "deviceGid" attribute from the locationProperties.

Emporia admits that they have deprecated the locationProperties endpoint -- it looks like without telling anyone. Sigh ...

Once that issue is resolved in the library, I can update the plug-in with the new version. But until then, I don't think there's anything I can do to fix it.

Ok, thanks for the quick respone!

I am sorry you both are going thru this. But thank you for posting. I was planning on doing some work to eIsy later today which would require a reboot but I will now wait for the update.

Thanks again!

-Tim

just started failing for me too. Hope emporia can fix the problem.

2 hours ago, photogeek54 said:

just started failing for me too. Hope emporia can fix the problem.

It's not Emporia it is the people who backwards engineer the data retrieval process that released the code Bob used to make it available for us.

Edited December 30, 2025Dec 30 by tazman

Well, so much for my luck. I postponed rebooting eisy so I wouldn't lose vue. We lost internet for most of the day yesterday. When it was restored, vue was throwing the same error as the op. I am down now also.

So its not only a reboot but also a loss of internet that will kill it.

I am not complaining, just putting it out there.

-Tim

Well mine started working again on it's own but I don't want to restart it to see if everything is good. @Guy Lavoie you can try and see if it will retrieve your devices now.

2 hours ago, tazman said:

Well mine started working again on it's own but I don't want to restart it to see if everything is good. @Guy Lavoie you can try and see if it will retrieve your devices now.

Interesting. I'm away right now but I'll certainly try it this evening. Thanks for the heads up.

Mine too! I noticed yesterday morning it was running fine. I rebooted eISY yesterday afternoon and vue did started working right away after it initialize! I haven't tried again though, didn't want to push my luck..

Well I haven't changed anything and there's been no movement on the issue reported to the Emporia library maintainers so it must be something Emporia did, maybe they were having other issues with the change and rolled it back.

What's odd is that their phone app kept working just fine, and I was even able to add a new plug. Like they didn't need this function themselves.