tmorse305

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.

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.

I see a lot of hops left=0 so it might be communication problems. Can you move the 2856D2 close to the PLM and try to restore that one?

What type of devices are they?

On Point#1, I have the exact same problem. Every time I add anything in the portal it is not found after 'discover devices'. It's been this way for as long as I can remember. The fix for me is to unlink/relink the ISY skill, then discover devices. That works every time. Funny I just assumed that happened to everyone. There was a thread about this a long time ago but I doubt I can find it. It's interesting that it works for some people.

BTW, has anyone told you lately how great this NS is? I find new uses for it all the time. My latest was using a plug to monitor my air compressor cycle in conjunction with an eisy program to purge my irrigation system for the winter. Just launch the program and it waits for the compressor to recharge (not a very big compressor) then fires off the next zone. Thanks again!

Thanks Bob, When I went back to check, everything was now working fine. I made no changes. Maybe there was a problem at the Emporia end of things.

Hi @bpwwer, I can't control my emporia plugs from the AC. Log attached, there are a bunch of errors recorded. I tried a reinstall but no improvement. Thanks for your help. VUE_11-11-2023_94729_AM.zip

ecobee has a wireless remote sensor that includes a motion sensor. You can include or exclude the remote sensor from the operation of the main thermostat. You can't exclude the main sensor. I used to have Venstars with remote sensors and lots of programs to control them. Then I switched to ecobee and ended up deleting most of my programs and letting the thermostat take control. The thermostat has impressive capabilities and does a great job mostly on it's own. You should check it out and see if it can work for your situation.

Thanks for the replies. Too embarrassed to tell you what I did wrong…. It’s all set now, caulk another one up to my aging brain.

I trying to access the AC remotely and am getting a string of text back instead. Probably some kind of error I suspect. Here's the text slightly redacted when I use the "Admin Console URL": 10https://my.isy.io/isy/725f9b1063114dc02738e**********5456098751617d1ab21cac90ed52curn:udi-com:device:X_IoX_Device:1ISYUniversal Deviceshttps://www.universal-devices.com/X_IoX_Device:1eisy52265.7.0uuid:00:xx:b9:02:60:44uuid:00:xx:b9:02:60:44urn:udi-com:service:X_IoX_Service:1urn:udi-com:serviceId:uuid:00:xx:b9:02:60:44/services.wsdl/services/eventingUDIELKWebServicesuuid:00:xx:b9:02:60:44-UDIELKWebServices/elkServices.wsdl/security/elkUDISEPWebServicesuuid:00:xx:b9:02:60:44-UDISEPWebServices/sepServices.wsdl/sepServicesUDIUYZWebServicesuuid:00:xx:b9:02:60:44-UDIUYZWebServices/zwaveServices.wsdl/uyzServicesUDIZWaveWebServicesuuid:00:xx1:b9:02:60:44-UDIZWaveWebServices/zwaveServices.wsdl/zwaveServices192.168.0.114inactivetrue13020011302000/ When I use the "URL to ISY" url I am prompted for credentials and then it says it's not found. Any suggestions? Thank you.

Hi @Javi, iPhone 12 iOS 16.6.1 set to "Always" location access with Precise Location "enabled" in IOS UD Mobile 1.1.27 Geo fence radius set to 300 I've been having good luck with the geofence performance since I increased the radius to 300. Yesterday I had an unusual thing happen, see attached screen shot. It missed my departure at 13:08 and then upon return it bounced me in and then out. Maybe my initial departure was in the queue because it was not sent initially? Any suggestions? Thank you

I just tried the webhook method and confirm that it does not require a 30 second delay. Good to know. I had one application where I needed Alexa to be more responsive than the 30 seconds would allow. I used the VirtualButtons NS and the corresponding Alexa skill and that also does not require a 30 second delay. But you only get 1 button for free. This looks like a better choice if you need more than one.

I wonder if the webhook method is subject to the 30 second throttling that occurs when the method @bmercier described. I use that method for a lot of things but always have to ensure programmatically that I wait at least 30 seconds before changing the state of the variable.

Thanks Bob, this solved the problem for me. So there is a unique usename/password for each NS? I experienced some other file corruption recently so maybe this was another casualty.

Thanks @bpwwer, I didn't think to look in the PG3 log. At exactly 18:44:00 Using the AC I tried to turn on a Kasa switch which generated the above error. I watched the KASA NS log as I did it and there were no entries (on debug level). I then checked the PG3 log and found this: 9/9/2023, 18:44:00 [pg3] error: IoX Inbound Status: UnauthorizedError: Unauthorized at Object.throw (/var/polyglot/node_modules/koa/lib/context.js:97:11) at checkAuth (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/nodeserver.js:30:56) at getNodeserver (/var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/nodeserver.js:40:11) at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/routes/nodeserver.js:166:16 at async /var/polyglot/node_modules/@universaldevices/pg3x/lib/services/https.js:48:9 Hopefully that provides a clue.

Thanks Jim, I'll open a ticket.

Hi @Jimbo.Automates, I can't communicate with any of the Kasa devices. The NS is up, the AC reports it to be connected, but if I try to operate a device I get this error message: The are no errors in the log, and no log entry of any kind is generated when I get this error. I restarted the NS and rebooted eISY but no luck. Suggestions?

Not really NS related but I thought Emporia users might see it here. Emporia is recalling some of their plug modules because of a poor ground. See photos of one I just dissected. The ground contact is one sided and has very little contact area with the plug. I received an email letting me know I had purchased a recalled plug. Just FYI

I wonder if the SD card is starting to fail.

You might try here also: https://github.com/kewashi/HousePanel/issues

Hi @kewashi, are you still monitoring this forum for Housepanel issues?

This sounds more like a HousePanel issue not a Hubitat issue. The author of HousePanel was active on this forum a while back, not sure if he still is. Here is the link to the thread:

Hopefully Kasa will continue to sell the older versions. Right now, the matter versions are more expensive but time will tell.

The switch is KS225 I now have some plugs too, they are KP125M