tmorse305

Sorry markv58, I didn't see your post when I replied to Teken. The update to v1.0.8 solved the problem. Thank you and Teken for your help.

Set precision to 1 on the temp state variable, rebooted RPI, Updated Profile again, restarted AC, but no luck. Interesting that when the Polyglot restarted all of the nodeservers came up running except VIrtual. I had to restart it manually. Not sure if that offers anyone a clue.

Thanks Teken, I had already tried everything in your first paragraph before reaching out for help. I rebooted Polyglot first, then ISY. Tried another Profile Update and AC restart but still no joy.

Is there something else I need to do to see the additional fields? I'm running 1.0.7, I updated the profile and restarted the AC, ran the 'then' part of the program twice but I still see this. Thanks for all the work you have done on this nodeserver!

If you have an Alexa within earshot you could have it say "Shed door opened" when the breach occurs.

Is the door sensor Insteon as well? Is the door sensor available in your ISY or is the email being sent to you some other way? If you have outside spot lights that hit the shed, then you could set those off when the door is opened. Tell us a little more about your setup.

I use this program to keep track of the battery level in the MS. I can't take credit for it, I found it in a thread here years ago. It uses the light/dark sensor to confirm that the motion sensor is still alive. If the light/dark sensor doesn't toggle in less than 26 hours I get a message to check the battery. DW Motion Battery Check Copy - [ID 0076][Parent 0001] If 'Outside / Driveway-Sensor / Driveway-Dusk.Dawn' is switched On And 'Outside / Driveway-Sensor / Driveway-Low Bat' Status is Off Then Wait 26 hours Send Notification to 'Text-Tim' content 'Battery Check' Set 'Outside / Driveway-Sensor' Write Changes Run Program 'DW Motion Battery Check Copy' (If) Else Wait 5 minutes Send Notification to 'Text-Tim' content 'Battery Check' Set 'Outside / Driveway-Sensor' Write Changes

I'm glad you figured it out, I was getting ready to suggest a support ticket, you seemed to be doing everything correctly.

Alexa is treating it as a light, that's why it displays the on/off controls. A light will never show up it the trigger list. Could you try deleting it from Alexa and then rediscovering it? Don't touch anything in the portal, it seems ok from there but it is not coming through correctly. In your last picture the type is "other", that's not correct, the description doesn't make sense either. Compare to mine. Is the state variable 'Motion' the first one you defined? That's what the (1) would suggest. Just checking.

You're right it should show up under the 'Smart Home' listing. The reason it's not showing up for you is that Alexa thinks it's a light. Try deleting 'cottage motion' from Alexa and rediscovering it. It should show up as a motion sensor not a light.

Based on screen #2, you have defined the Alexa Category as a light not a motion sensor. That's why it's not showing up in the routine choices. Go back to the portal and double check the Alexa Category. It should say Motion sensor, see screen shot. The only ISY devices that show up in Alexa as those defined in the portal, if they're in Alexa you must have create the link in the portal. For the August lock to show up you must have enabled the August skill for Alexa, or through the portal.

Open the portal go to Select Tool > Connectivity > Amazon Echo Click on "Variable" at the top of the window Use the pull down to find your state variable 'motion' (It has to be a state variable) Choose Alexa Category "Motion Sensor" Set the variable value that you decide means motion Give it a spoken name Save Discover devices on Alexa Your variable should now be a device with the name you gave it. Create a routine with your variable as the trigger, create a spoken action (BTW the action could also include your Amazon plug!) On the ISY side the variable value that equals motion should always be present for 30 seconds or more so Alexa doesn't miss it. Then reset it back to a "no motion" value. If you use other values for the variable just remember that every time the value changes you restart the Alexa 30 second debounce even if it didn't trigger the motion. For example say 0 is no motion and 1 is motion detected. If you change the variable value to 2 Alexa considers that the same as 0 and restarts the debounce interval.

Create a variable on ISY and expose it as either a contact sensor or a motion sensor depending on what you want to do with it on the Alexa end. Expose the variable to Alexa on the portal. Then create an Alexa routine that uses the exposed variable as a trigger and then create what ever action you desire. I have several of these in use. Just remember the 30 second debounce interval. Changes will only trigger the action if they are > 30 second apart. Examples of how I'm using this: I have a WIreless Tag on my birdfeeder. When a squirrel gets past the barrier (not too often) Alexa says "motion at birdfeeder". I have an Insteon Motion sensor outside on my driveway, when triggered Alexa says "Driveway motion".

I don't have an Amazon plug so I can't try this but I think this would work. Create a variable in ISY and expose it as a contact to Alexa via the portal. Then write 2 routines on your Alexa that triggers the plug either on or off when the ISY variable changes. Not ideal though because there is a 30 second debounce on the contact input so you can only cycle the light on 30 second intervals or longer.

DId you try to reboot Echo?

Thanks Benoit, Since it works fine with as a contact sensor, it seems you can leave the other as is. Regards, Tim

Hi Benoit, The door sense(open/close) is now correct in Alexa. I also created a routine using the door as the trigger condition and that also works. I configured the door in the Portal as a contact sensor. I also tried it using the new category 'Device with Open/Close syntax'. When Alexa discovered it this way it comes through as a device that displays as 'Power is On/Off'. That was a surprise, is that correct? Thanks for fixing this, it works correctly when configured as a contact sensor. Tim

@saphotoexpress, thanks for making the upgrade to 5.x. Sorry to see the contact sensor is still an issue. I'm sure UD will fix it an upcoming revision.

I'm not running 5.0.16C yet but I would say the the problem has not been corrected yet. If you're up for trying something else I would reset all and start over this time add the repeaters first, make sure they install correctly and appear correctly in the console. Then add one lock. Once added, operate the lock a few times, open and close the door a few times before adding the second lock. What I found was when the lock was initially installed only one node appeared in the console. Then after I operated the lock the second node appeared. That said even if the 2nd node appears it looks like there might still be an issue with the lock configuration in 5.0.16C.

That might be the difference. I’m running 5.x software. If you open the door and then lock it does it show as locked? The 4.x software might not support the contact. This last time I tried the 5.x software it showed the 2 nodes but the contact node did not work correctly. Sent from my iPhone using Tapatalk

Did you install and configure(in the August app) the door position sensor when you installed the lock? When I had my lock installed, it looked like this.

Great news, I'm glad you got it working. I'm curious how the 2 nodes for each lock show up in your ISY, is it Door Lock and Door Lock 2?

I ran into the null database issue too when I first tried to set up the lock. I fixed it by factory resetting the dongle, 2 plugs, and the lock. On the next attempt everything was included. It's the nuclear option but as long as you don't have too many devices it's not that bad.

Does the lock show up in your ISY like this or does in now appear as a lock and contact sensor?

From my experience communication with the August lock is very unreliable even with repeaters. The communication with the lock is far more complex than with a simple plug or switch. There was an issue with the lock joining with the ISY, I'm not sure it has been fixed yet. The lock is 2 devices, the lock and a contact sensor to indicate door position. The 2 nodes were not created correctly in the ISY and added to the communication issues I was having. I let UD know about the problem so it may be fixed already. I stopped trying to connect it directly to ISY as the connection was so unreliable. I now use a dedicated Hubitat located very close to the lock and connect Hubitat via the portal. This has proven to be pretty reliable but not perfect. Occasionally the lock status in Habitat and the lock do not agree. There were zwave issues with the August lock by their own admission. August lock support finally downgraded the software in my lock to a version that was more stable but I suspect still not perfect. The version I'm running is "undefined-1.59.0-1.8.15". I also tried IFTTT but there was an issue at the time (~6 months ago) that delayed the communication to the IFTTT servers. As a result lock change status could take upwards of 10 minutes to receive. August lock claimed that was an IFTTT issue but I use IFTTT for lots of things and this is the only device that acts like this. I hope you have better luck, I like the lock but communication outside of the August App is troublesome.