tmorse305

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

Thanks Jim, I just tried the new matter certified plug and got the same result. Maybe the matter devices are not supported yet or ever given the undocumented api. At least i can control them via the Alexa app so all is not lost.

Hi @Jimbo.Automates, I installed the new Kasa Smart Wi-Fi Dimmer Switch today. This is the version that is matter certified. The Kasa app found it ok but the NS will not discover it. I tried a NS restart and the DIscover button but no joy. I search in the log for the switch name but it doesn't appear there. There are no errors related to that device. I can see the device on my home network with an IP address assigned. Any suggestions? Thank you Update: Today I deleted the NS and reinstalled it to see if it picked up the new device. It did not and in fact missed another device that has been working fine all along. I tried a delete again and an eisy reboot but after install the new switch and the outdoor plug are both missing. I also noticed that the AC does not update until the short pole occurs. Maybe that's normal but I thought in the past when I toggled a device in the KASA app the state in the AC changed immediately. I will PM you the log file starting at the reboot/install. Thanks Jim PG3x: 3.2.1 IoX: 5.6.4. KASA NS: 3.0.21

https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Upgrade_Process_-_As_of_July_2022

To close this out, there is an issue UD has identified. Until they can fix it there is an easy work around. Simply choose another tab, then return to the tab with the camera and it will load properly. Thanks @Javi!

I tried out the new camera feature, thanks for another great addition to UD Mobile!! I have an EZVIZ camera and set up the rtsp stream. It works intermittently. When it doesn't work it comes up as a black screen or it says stopped (see attached). VLC brings it up every time using the same url .

Look in one of the NS logs: 2023-07-11 13:24:21,106 MainThread udi_interface INFO __init__:<module>: UDI Python Interface for Polyglot version 3 3.0.60 Starting...

@Geddy, @tlightne, thanks. I missed the reinstall button on the screen after the install button. Anyway I uninstalled reinstalled and its all good now. I recall a thread about upgrading NSs but I couldn't find it. The weird part is that just last week I upgraded 2 other NS by just restarting them. So maybe it's NS specific.