Scyto

Last night I was turning off my KPD manually - ust pressing the off switch. It burped (beeped / buzzed / not sure which) at me and then all the buttons LEDs came on and the little status light was red. At this point it was not responding. So I pulled the little set switch out to removed power, pushed it back in after a few seconds and now all is ok. What happened? Is the KPD about to fail?

Yeah I couldn't find one for the 599 either.

I concur. I submitted a ticket to Schlage. I have asked them about firmware updates. Lets see what they say. I did find this for the BE469 - not a lot of support in these either http://www.schlage.com/content/dam/sch-us/documents/pdf/installation-manuals/24352403.pdf wish I had known this before I bought and fitted them. I like the physical aspects of their locks over kwikset. This sparse implementation of z-wave is disappointing.

I was wondering if there was a way for the ISY to put the PLM into test mode (the 4 button tap test). Sometimes when I am walking the house it times out and I am lazy I would prefer not to walk back to the basement to tap the button 4 times again

Thanks for checking, good to know it isn't some unique issue with my setup. Shame the schlage lock seem to be feature sparse. The Kwikset will let me set user schedules from the ISY in addition to all the other features that schlage appears not to have in the control list. Do you have any idea if the is the Schlage lock itself or the support in the ISY?

Great minds think alike already did that as I can be pragmatic - just wanted to be as elegant as possible

Thanks, I took a look at control. For the Kwikset I have all sorts of interesting options around battery life, remote lock/unlocking, local unlock using key or buttons etc. For the Schlage all I get on the control option for the 'is / is not' is Access Code 1 through 30 This means there is no way to use control to alert and do what I want. 1) Should I be seeing more options for the schlage? This lock has a direct association with the ISY. 2) it is non-intuitive to me the way the logic works with status. I only get the 'locked' message when both locks start out in the unlocked state and then I lock one of them. If they both start locked and I unlock one and then lock it again I get no locked message. Is this because at the pint of evaluation both = false i.e. the evaluation of the state is done after the action, not on the action?

ok, but then why send me the true state of locked when it locks and not send it when I unlock one. For the logic to be consistent if I unlock one of the locks I should get one unlocked message and one locked message on the unlock, but it doesn't.

I have a program that sends a notification when either of two locks are unlocked. For one of these locks (a schlage FE599 Door Lock) I also get a lock notification. This doesn't happen for the Kwikset Door Lock deadbolt. The behavior I expect is to only get the unlock notification for both locks and never a lock notification. (this is the only program I have that sends notifications or queries the lock status, all the text messages indicate this is the program that generated both the unlock and lock alerts) locks - [iD 0013][Parent 0001] If Status 'Ground Floor Hallway / Front Deadbolt' is Unlocked Or Status 'Ground Floor Hallway / Front Lever Lock' is Unlocked Then Send Notification to 'Default' content 'Door Unlocked' Else - No Actions - (To add one, press 'Action')

db Maybe an alarm clock module is a good product suggestion for an ideascale site?

Yup I seem to do that with these devices a lot too....

I opted for the MMS path - that's ok for my purposes at this time. I don't worry about SMS or MMS finding me - I do international travel and sometime I have the cell off for 10+ hours and the SMS and MMS generated in the US finds me in the country where I land almost as soon as I land and turn the phone on. I have email as my backup to that.

Yes I am on ATT - how do I get it to use the mms?

I have a program that alerts me when any of my doors are unlocked. The alerts come in with source numbers that sequential. Like 1-410-100-016 from the first doo event, 1-410-100-017. I am not sure what the logic for this is, but I would like them all to stack in my iPhone messages against one contact. Is this possible? (also is there any logic to the number chosen?)

I will need to think about it a bit more, but it seems many of us hit similar issues. One idea I had for v5 was to treat (optionally) the keypad dimmers and switches as a virtual node. Meaning that one could configure the buttons at both the scene level and controller level, i.e. never even expose the two levels, keeping them both in sync. What I haven't given enough thought to is how this idea breaks for other scenarios, nor do I have enough insight to how insteon does it in their hub - maybe they came up with a different / better idea than mine. I guess this also goes to the root of me not understanding the history wrt to button grouping too

If you find a way to control the russound can you let me know. I have a speakercraft and despite having a variety of network modules and eve an iPhone app haven't worked out how to control it.,..

Also could you explain how much easier it was to program the keypads with the insteon hub? Perhaps we could persuade Michael for better workflow for these once they have virtual nodes in v5...

You used the copy function to copy scene attributes to each of the scene controllers?

I dunno, when I used the Revolv as a hub it controlled every scene - ie every device only had one association, with the hub and it didn't support the multi button devices. I have had a steep learning curve with the 2334-232, they have been nothing but strange. They key for me was ensuring I programmed at the scene level, used the copy settings to the controller in the scene and then test. I think my issues might have been excacerbated by some RF issues. So putting device retries to 3 on the 2334-232 seems to have cleared up my issues along with doing the full reset on the two problematic ones. I have no idea if this is an insteon device / PLM issue / ISY issue oh and a bug in mobilinc was making me think I had devices issues I did not have...

I just fixed the one I had issues with. When a scene was activated it would say in the ISY console that the right ABCD button was lit but it wasn't. I hard reset my KPDs set them to 3 retries for every button. Then did a complete restore of the device. Now working ok. In my case I think they were mis- programmed due to comms issues, despite multiple writes.

Ok, ignore me, doesn't sound like my issue. Just checking, you are not using software like mobilinc to call scene?

Can you do the 4 button press on the PLM and see if the LEDs blinks on the 2334-222 - I have two 2334-232 that do weird crap like this that I am troubleshooting....

Which 8 button keypad is this? Is it a pure keypad or the switchlic/dimmer that also controls load directly? Also make sure if you are switching between testing the scene via the admin console and pressing the physical button that the scene level and controller level settings are the same - use the copy scene attributes on the controller node (the node in red text that is under the scene). Also if you don't have show devices heierarchically you might want to turn that on.

I love my hikvision cameras and their iOS software and windows software is pretty neat, I can provide legal links to the SW and firmware if you pm me

Michael, I have never had my KPDs work properly, can you take a look at http://forum.universal-devices.com/topic/15327-mobilinc-doesnt-activate-scenes-correctly/ (not s mobilinc issue) and see if this is related to this thread issue?