garybixler

Do you have port forwarding set up for the ISY through the router?

Not sure where that update would be. Is it the parameter 9 in the advanced config of the ZEN?

Yes you are right. It is a secondary button. So far they seem to work (lit up) only with other Insteon devices set as controls in a scene. Thanks Gary

I have a question on the way a scene acts that has an Insteon button of an 8 button switch and a Zooz ZEN 71 on/off switch. Both are controllers. When the Insteon button is pushed on the ZEN switch responds with an on and the opposite with an off. All good. But when the ZEN switch is turned on which shows up in the scene as on the Insteon button isn't turned on (lit up). I just assumed that the ZEN would also turn the scene on. I did a work around with a program that will turn the scene ON/OFF with the ZEN switch status. All works as I like but just curious about the scene control differences. I'm guessing that because there is no link between the Insteon and ZEN is the problem. I just thought that the ISY would turn on the scene between two different devices. Thanks Gary

Try control instead of status.

Was wondering if there might be a Z wave connection map available at some time in the future. Would be great to visualize the Z Wave network to determine if and where a repeater might be needed. Also to see a device's neighbors. Thanks Gary

Yes I forgot to mention that I use the browser for device management but need to go to the app for routines and such.

I'm wondering if the difference in disabling and reenabling the skill might be if it is done through the app or a browser. I used the browser and didn't lose any routines or devices. I did need to add the devices back into the routine and enable the routine.

I did have the same issue and am working again. Other than an upgrade the disable and re-enable is suppose to fix the issue with 5.4.0. I can't verify that because mine was fixed before that was known. I had upgraded to V5.4.0_2 which so far has fixed the issue. A skill disable enable may be necessary.

@tmorse305 I think what was ment is to disable and re-enable your motion sensors on the ISY.

One thing that has worked for some is to go to your Alexa app and disable and re-enable the device. If that doesn't work an upgrade may be needed. Also there is a 30 sec timer on the device to prevent bouncing. So it may not work immediately.

If looking from the top of the board in the correct orientation the leds are marked d4, d5, d6 with d6 being the the third led. It would be the left led if viewed from the front. Just my guess. Still can't get the 6* push to work.

@macjeff With further testing I see the switch on Alexa turn on and off with the variable change. So the problem must be in the return response from Alexa.

I too discovered that variables aren't triggering Alexa responses.

I upgraded to 5.4 using SSH and have the rapidly blinking left LED. Gary

Hi, Just wondering if there would be any interest in creating a Genmon node server on PG3. Thanks Gary

Hi, Just tried V 3.1.3 and found one issue. When the leak sensor (Type 34) is queried the tag web site sends a notification that it could not call URL for "LeakSensor 5". I copied the info from that query. The other tag types work fine. Thanks Gay New Text Document.txt

Good News. All seems to be working perfectly. Thanks So Much. Gary

Did close and reopen AC several times just to be sure. I sent the Log. Thanks Gary

OK also this is what the AC shows.

Basically the AC is blank. It doesn't appear that any changes are loaded into the NS from the tag. I raised the temp on the tag but no changes were seen at the NS. Also GV12 doesn't change when wet.

I already had the leak sensor installed but the NS doesn't seem to see it as a leak sensor after update. It acquires the tag type of the last tag viewed. I tried deleting the node in the NS reboot and discover but can't get the NS to recognize the leak sensor. Basically no data is loaded into the ISY. I think it is present in the NS. I attached a snippet. Thanks Gary

That's odd, I have just tested the 'Seconds Since Updates' and all seems to be working perfectly. I Covered the tag with foil and after 5 mins or so it went out of range. There may be up to a 30 second delay until the NS server gets the out of range. I assume that is the polling interval and out of range doesn't trigger an immediate update. Thanks Gary

I couldn't say. I have never tried removing the battery.

@JimboNot sure if removing the battery will result in out of range. What I do is wrap the tag tightly in aluminum foil for testing. Usually the tag is in my car for determining if it is home or away. I set the tag to record every 30 seconds to give the fastest response and if out of range to search every 5 minutes. I query the tag from a driveway sensor so it would never need to wait the 5 minutes. As the out of range may take 5 minutes or more I tried using the 'seconds since update' but was to inconsistent. Hopefully the update will work better. Thanks gary