smacbride

I'm having the same issue with UD Mobile on two different ISY boxes, getting: ERROR:Connection Type: oAuthPortal, Error coce 404 Also noticed that MobiLinc is not working. I am able to log into both ISY boxes via the my.iso.io. I'm able to go into the settings->system->{isy box} and then it connects and I can synchronize, however when I go to the main page I get the 404 error again. Also the "test connection" works, but still get the error from main page.

Will the i3 products be supported on the ISY boxes?

Does anybody know how to reset the Intrusion Alarm that shows up when the lock is tampered with? This went off a few days ago, and I turned off the alarm at the lock, but it still shows up as ON in the status.

Both admin console and web interface. No changes to my network or av software. Sometimes I would get a "page not found" going to my.isy.io which does suggest a DNS error, although I could reach the forums.

So a few days ago I am no longer able to log into a remote ISY box using the remote URL. It the one that looks like this: https://my.isy.io/isy/45b892c...... It just says "Not Found" I just when into the portal on line and looked at the URL and its the same one I have saved. This was working fine a few days ago. Has something changed with the remote URLs? Thanks.

One of the reasons I went with HA over using UD mobile is that I just wanted a simple buttton to turn a state variable on and off (just like a switch). I could never figure out a way to do it using UD mobile. Since then I've been able to integrate other disparate technologies into my HA setup so I'm happy with it for that. Every couple of months I re-visit UD mobile to see how the progress is doing and I think it's moving in the right direction, but it still falls behind what you can do with HA for dashboarding.

Did you un-plug the ISY box from the internet but keep it running? This would rule out any outside interference as mentioned above.

I have a three-way setup with those same switches. My HA system shows the correct status when I turn either one of the switches on/off. I have both switches setup in a scene, which also includes a button on a keypad. The scene is what I have displayed in HA. So for me its working fine.

OK, must be something on my end. I'll try re-booting my cable modem.

Is anybody else having this issue: Your connection is not private Attackers might be trying to steal your information from universal-devices.com (for example, passwords, messages, or credit cards). Learn more NET::ERR_CERT_COMMON_NAME_INVALID

I've used the Aeotec sensors and they work well with the ISY

You can check out Home Assistant, but the app requires that you have a hub running their software somewhere in your house. I've been doing it for about 6 months so far and I'm very happy with the results.

That looks like the correct procedure. Have you tried to restore from a backup?

For mine I programmed an Insteon four button KPL and I have the various buttons turn on different colors. Here is an example for turning on the violet mode, it turns on the strips and then ramps them up over 3 seconds. (The variable is used for my Home Assistant dashboard)

I recently installed some Fibaro RGBW switches and they had the same nodes. For mine the Color Switch sets the various color channels. The multilvel switch turns them off and on in various ways. The energy meter nodes show you how much energy is being used. On the Fibaro switches, they have inputs that control the switch in various ways. You can attached a thermometer and have it change color based on temp etc. Also you can have manual switches attached that turn various things on and off. I believe that the other nodes are for those purposes. For mine I just put them all into an "ignore" folder. The 'Color' and the 'Multilevel' nodes are the only ones you need for programming it with your ISY.

They haven't been discontinued, just out of stock at the moment.

I'm using the Schlage BE469ZP and have never had any issues with it. It's been over a year now. During the winter I upgraded to the new 500 series chip in my ISY box and it still works fine. It gets used with my iPhone app at least twice a day, never had any issues. The only thing I couldn't figure out was having the ISY respond to an intrusion alarm on the lock.

@shbatm I tried that and got the same results. It turns on the light but the status flips back to off: 2021-06-09 07:30:28 DEBUG (MainThread) [pyisy] ISY Request: https://my.isy.io:443/isy/{unique_url}/rest/nodes/57%20FA%20EF%201/cmd/DON 2021-06-09 07:30:29 DEBUG (MainThread) [pyisy] ISY Response Received. 2021-06-09 07:30:29 DEBUG (MainThread) [pyisy] ISY command on sent to 57 FA EF 1. 2021-06-09 07:30:31 DEBUG (MainThread) [pyisy.events.websocket] ISY HEARTBEAT: 2021-06-09T07:30:31.986441 2021-06-09 07:30:34 DEBUG (MainThread) [pyisy.events.websocket] Starting websocket connection. 2021-06-09 07:30:34 DEBUG (MainThread) [pyisy.events.websocket] Websocket Server Not Ready. 2021-06-09 07:30:34 DEBUG (MainThread) [pyisy.events.websocket] Stopping websocket connection. 2021-06-09 07:30:34 INFO (MainThread) [pyisy.events.websocket] PyISY attempting stream reconnect in 60s.

@shbatm Disabled the local ISY integration: The problem still exists. Added the debug to the config (this turned off the light, but it still shows as on): 2021-06-08 15:47:09 DEBUG (MainThread) [pyisy] ISY Request: https://my.isy.io:443/rest/nodes/57 FA EF 1/cmd/DOF 2021-06-08 15:47:09 DEBUG (MainThread) [pyisy] ISY Response Received. 2021-06-08 15:47:09 DEBUG (MainThread) [pyisy] ISY command off sent to 57 FA EF 1. 2021-06-08 15:47:15 DEBUG (MainThread) [pyisy.events.websocket] Starting websocket connection. 2021-06-08 15:47:15 DEBUG (MainThread) [pyisy.events.websocket] Websocket Server Not Ready. 2021-06-08 15:47:15 DEBUG (MainThread) [pyisy.events.websocket] Stopping websocket connection. 2021-06-08 15:47:15 INFO (MainThread) [pyisy.events.websocket] PyISY attempting stream reconnect in 60s. 2021-06-08 15:48:15 DEBUG (MainThread) [pyisy.events.websocket] Starting websocket connection. 2021-06-08 15:48:16 DEBUG (MainThread) [pyisy.events.websocket] Websocket Server Not Ready. 2021-06-08 15:48:16 DEBUG (MainThread) [pyisy.events.websocket] Stopping websocket connection. 2021-06-08 15:48:16 INFO (MainThread) [pyisy.events.websocket] PyISY attempting stream reconnect in 60s. 2021-06-08 15:49:16 DEBUG (MainThread) [pyisy.events.websocket] Starting websocket connection. 2021-06-08 15:49:17 DEBUG (MainThread) [pyisy.events.websocket] Websocket Server Not Ready. 2021-06-08 15:49:17 DEBUG (MainThread) [pyisy.events.websocket] Stopping websocket connection. 2021-06-08 15:49:17 INFO (MainThread) [pyisy.events.websocket] PyISY attempting stream reconnect in 60s. Here is the health status: Universal Devices ISY994 Host Reachable ok ISY Connected true Last Heartbeat Time Event Socket Status reconnecting

I posted a few days ago that I upgraded to HA 6.2 and it was working, but I have since discovered an issue. I have HA setup with two ISY boxes, one local using a local IP, one in a vacation home using the UD portal URL. Since upgrading to 6.2, the local ISY works, but the one using the portal URL does not. When you turn on a light in the HA dashboard, the light turns on but then the display in the dashboard immediately toggles showing the light as off, even though it's still on. Re-loading the integration shows the correct status, but then when you toggle the light off, it immediately flips back to show on. I tried upgrading to 6.3, and the problem still exists. I reloaded a 5.5 snapshot and the problem went away, everything is back to normal. So something in the 6.x branch has broken the connection to my ISY on the UD portal.

Just an FYI, I upgraded to HA core 6.2 this morning and everything is working fine for me.

The UD mobile app is a new thing. Most people setup their ISY boxes using the admin console installed on a PC. I would start with that, get things working, then sign up for a Portal account (that gives you the remote URL) then try out the UD mobile app. Somewhere on this website there is a getting started WIKI with all the information you will need to get it up and running. Try this out: https://www.universal-devices.com/start/

I use my ISY with a mixture of Insteon and Z-wave. I use Z-wave thermostats(Honeywell and GoControl), Schlage locks, Aeotec leak sensors, and Fibaro RGBW controllers, with Insteon for most of my lighting and electrical outlets that are automated, and a few Insteon leak sensors. I have a vacation home setup with a mix as well. My systems all work just fine. I know some people have had issues communicating with their locks, but I haven't experienced that problem. You have to research the z-wave device and make sure it will work with the ISY, but so far most of the name brand devices work just fine. And yes, your ISY box acts as the z-wave hub.

I think the problem is that if you have a lot of lights, the programming gets messy. It would be nice if you could check the status of a scene, but I don't think you can, only the devices.

Hi @Javi, They are zwave devices, so I think those are handled as nodes in the ISY. So they should work ?