drprm1

I would appreciate this

That icon is only meant to mean its a motion sensor. It has no bearing on options or state of the sensor. Might suggest a factory reset and add back to ISY to see if OFF commands are being sent

Understood. Thanks for the info and help

Went to dyndns to change and realized I have two health checks one http and one https. Again only http://xxx.com/80 is up and down

Roger that. I’ll change and report. Thanks,

As far as I know I never set up anything at my house, using this domain name, on my router or computer. As far as multiple devices on port 80, I’ve only specified ISY to use 80 through port forwarding on my router. Here are the settings

Was wondering about this Have domain through Dyndns and have what is called a “Health check” feature. Not quite sure what it does or what it checks on. So it points to my ISY ( http://xxxx.com:80) All day it will go down then come back up Know Just wondering why this is happening and if I need to change something thanks!

Got to be that. When I hit on the locative app it downloaded the app so it wasn’t on my phone or the update changed the setting for it. Im sure (?) I can figure it out now Thanks for pointing me in the right direction

Sorry, I am using locative.

Used to use locative but switched to the Isy portal occupancy node

Updated iOS on phone to iOS 12 and now portal occupancy isn’t updating. Is there a new setting I may have overlooked to get this working again? Thanks

Alexa won’t unlock locks without giving an access code number. But if you have some sort of workaround to get it to open locks and it hears the command from outside, or anywhere, why wouldn’t it open it?

I checked junk mail the other day and saw nothing. I was thinking maybe I put in the email incorrectly....I’m saying that on the support ticket page that it never showed that my message made it through and no buttons would respond. It looked like it was stuck or it had timed out. I have no time outs on my email. Thanks for telling me what to check!

Of course I spoke too soon. Getting the messages again. Grrrrr

Michel, No big deal but I never saw a response on my ticket. I know you responded but I’m not sure what email it went to. I responded about not getting a response via the support ticket page twice but it kept timing out and I couldn’t tell if the message was being sent. I simply stopped because I didn’t want to pester you while you’re working on the device mentioned in “where to next”.!!! On further digging I read to check cables and network switches between my ISY and router. I verified all cables were fine. My ISY was wired behind two switches so I ran a new dedicated cable back to my router....Haven’t had any error messages since. ??

https://wiki.universal-devices.com/index.php?title=ISY-99i_Series_INSTEON:Networking:Mobile_Notification

This message keeps popping up. I have 5.0.13A firmware and UI. Using the new Zwave dongle. I’ve restarted ISY and AC. Cleared java cache. No joy... i cant even save a program because this keeps popping up. Thanks for the help, Also getting this occasionally

I might be imagining this because I don’t remember when I enabled this feature but I think it started after I started using “brief mode” on my echos. ???

Using 5.0.13a

I too am getting these messages. Also getting “the skill for that device is not enabled, please enable the skill and try again”. Even though it says that the command is executed normally.

Thought I’d ask. Recently another forum member ordered a new ISY before finding out the power supply was bad. ?

Did you verify your ISY’s power supply is good?

Sorry, meant to say moved ISY closer

Recently started getting into zwave. Have small amount of zwave devices; 4 door sensors, 2 thermostats, 4 sirens, and 3 Schlage locks. Pretty stable system until 5.0.13a. It seemed like everytime I started the AC there were communication error pop up boxes.(usually the zw door sensors) Also had to move the ISY closer to one Schlage lock to get it to include. The system worked well and it didn't seem like the comm issues I'd see in the AC were affecting anything. Installed new dongle, restored zw a couple of times, queried everything, and did node synchronization. Everything came back, got a few ghost nodes which I put in their own folder.Had to activate each door sensor to wake them up. The Schlage locks all had comm errors with red exclaimation marks. I found that if I selected one then hit "options", then query, the lock would work fine. Even the one lock I had to move closer to the ISY started working correctly without having to move anything. When I open AC now I get none of the annoying zwave comm errors that I was getting before. Right now everything works great. (then it's only been a couple of days) *The only thing I didn't do was a network heal. Reluctant to do one since everything working well.

After installing the new dongle is it okay to specify “query at restart” again, or do we leave it off?