mango

Okay understood. I shall do that. Edit: This has been done for status 'unknown'. Which segways to another question: The lock has some alarm nodes. I attach a pic, They are currently blank, I am unsure how each reports if they trigger, so ideally I would like to be notified by a push notification also, especially as they are 'alarms'. This example shows node ZW002_174 Hardware Failure Alarm. Is there a way to find out how this node reports when triggered or is it simply an 'ON' or a '1' ? Is there a trick to interrogate the lock to find out how it communicates?

Hmm, interesting comment. These particular locks have a user 0 which matches for anything like locking or unlocking the lever manually from the inside or locking from the outside by pressing the Schlage button (locks without having to enter a code). I think that takes care of 'unknown'? I have user 0 setup.

I adjusted my programming and naturally everything works perfectly ? 12 users setup, and Pushover is issuing notifications correctly. Now an easy copy/paste and tweak of the folder for the back door.

Amazing, I understand more now and have a lot of info to work with, thank you.

HI Bill, I just added a pic. Here is the example code too: [FrontDoor U10] Locked Guest - [ID 0006][Parent 0005] If 'Front Door / ZW 002 Front Door Lock' Status is Locked And 'Front Door / ZW 002 Front Door Lock' User Number is 10 Then Resource '[FrontDoor U10] Locked Guest' Else - No Actions - (To add one, press 'Action')

I'm back! It's been a hectic few weeks, I am only just able to spend some time on this again. So, Mr.Bill I have a crude setup working with your strategy of 1 program per NR. but with a weird bug: Example - randomly when a user unlocks, both a lock and unlock status occurs. Do I need to insert a pause, or perhaps a stop command to else to prevent more than one trigger occurring? This happens randomly, not every time the lock is used.

Maybe something that checks layer 3 for connectivity every hour, whilst holding the failed send until it can retry with success. For my cottage (regular power outages - covered with line UPS and generator / occasional DSL internet outages - no cell signal - no 3G/LTE fail over), I was considering something running locally on a Pi or mini PC that the ISY would send to, and give the job of re-try's to a different device.

I could not work on this last night due to news of a further impending lock down here in Ontario Canada. I should be able to pick this up in the next few days, thanks again.

BOOM! Light bulb. That is gold mine information, thank you.

hmm, so I was doing it right, even with a new line, there doesn't seem to be any black magic stuff. As you say above then it may be the wrong values for Schalge locks? I'll dig deeper tonight, thanks again.

MrBill you are being most helpful thank you. I am not local to the ISY at present. It's simply a case of formatting, and probbly something very simple that I am not understanding. One of my locks is ZW002, so for battery level my command would be: ${sys.node.ZW002_1.BATLVL} From memory the body line consists of: token=x&user=x&message=x Where and how do I place 'Battery Level = ${sys.node.ZW002_1.BATLVL}' ? Everything I tried last night resulted in a TCP400 error and the message could not be sent.

Sorry another question: Is there a trick to adding ${sys.node.ZWXXXX.BATLVL} to the body of a pushover resource?

so...I have 6 physical user numbers including guest, but I also need to add user 0 for times the door is locked manually from inside or without code from the outside (pressing the Schlage button). Each user requires only 2 notifications, unlock and lock. I could further develop the project with lock jammed and unknown (Z-Wave comms error?). Is there a battery level node?

I have already used the copy function wherever it may be, thankfully. So, having lots of network resource entries has no impact on the ISY other than taking up space, correct? An entry is only called into being to run then put back freeing up resources once more?

Thanks both. I only have 6 possible users including guest so I may go with @MrBill 's suggestion. This I assume should also allow me to assign separate pushover icons per user which may be visually a plus. Coming from the land of BASIC programming many moons ago....

Hi all, Please go easy with me. Some of this is way over my head. Having recently installed some Schlage BE469 deadlocks, I have been able to setup pushover and email notifications for doors locking and being unlocked. I now want to display the user and am having difficulty making sense of how to go about it without creating a large bloated mess. Last night I've realized I may be able to do this very cleanly with the use of the correct variable syntax, but I am unsure how to apply this: ${sys.node.ZW###USRNUM} would return the correct user number. How would I convert user numbers to actual names? Any tips and hints gratefully received.

Thank you.

Perhaps a factor, but not the reason. Go back in time and you can plot the demise, prior to any global excuse.

I'm a total outsider and all I can see is Instion oblivion. I mean, who can't?

I'll buy some shares.

Thanks for the reply Lilyoyo1. I am aware of tagging but don't like doing that on forums asking for help unless it is really important. I feel if anyone chooses to contribute or follow up they will. They don't need a prod in the backside from me ? Regarding zwave, it's a cottage address and right now I have good comms between 2 zwave locks and the ISY which is located roughly in the middle. No repeaters or any other zwave devices yet.

Hmm, I wonder if this was posted in the wrong forum. I posted here specifically to address any possible zwave nuances in programming, my apologies if so.

@all For me, hearing the issue seems to return after a random tweak makes it work indicates a faulty router. 2c. It should just work out of the box, ISY networking set to default and being DHCP, static or DHCP assigned.

I'm out of gas, sorry. Re-reading your OP, you say an Echo also stopped working? Then you may have to investigate the router in depth.

Turning on UPNP on both the ISY and the router may also glean some more gold.