Scyto

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?

awesome, could you put a link to it in your signature?

Is this by design? Any chance the topology generator will be updated to show zwave devices in scenes?

ahh I see, I thought it was for ordering buttons - see I was being dumb I wonder if you could use a PDF editor to edit these http://cache-m2.smarthome.com/manuals/12063_KeypadLinc%20square%20labels.pdf and http://cache-m2.smarthome.com/manuals/12063_KeypadLinc%20wide%20labels.pdf

Lucky [censored] (or rather congratulations on making a smart purchase decision) BTW communication means the AC / Furnace / zone controller / Thermostat have smarts and data they send each other.

Perhaps I am dumb, why do you need a template and can't use the form on the site? http://www.smarthome.com/insteon-2401c8-custom-etched-8-button-set-for-keypadlinc.html Is it because you don't want centered text?

Be very sure that if you are using Bryant evolution communicating system (and I see that you might not be) that you fully understand moving to any non Bryant / non communicating thermostat. I have a carrier system and do not want to loose some of the communicating features. This basically means I am locked in to the carrier shitty thermostat (I will never buy carrier because of this - the house happened to come with it). It is possible if you have a communicating system to move to nest / ecobee etc - but it may mean you need one thermostat at the location of the old sensor and the correct wiring back to the main unit and find they right way to control your dampers. There are folks who have done it with nest and ecobee (irrespective of the ISY) For example see ecobees info here and look at their forums https://ecobee.zendesk.com/entries/21650694-Carrier-Infinity-Bryant-Evolution Good luck! PS this is really just my rant against Bryant / Carrier proprietary communicating systems....

I don't know about the NAPCO However integrating the DSC Powerline Series (NOT THE NEO) is absolutely possible using a community made utility. This allows the ISY state variables to be populated so that the ISY knows when any sensor activated, the system armed / disarmed and lets you send commands back to the DSC for arming etc. My first integration I finished this week - when my front door opens the ISY turns on internal lights. The only sensor on the door is the DSC one. I suggest you start with this forum http://forum.universal-devices.com/forum/40-dsclink/ - this the app you run on Windows, Linux that talks to the DSC, you will need an EVL board to do this http://www.eyezon.com/?page_id=176 (link updated) I run DSCLink on raspberry pi (I have had minimal linux experience so this can be done by the motivated beginner) Let me know if you have any more questions. PS I build and commission the entire alarm myself - not sure what happens if you have one installed by an alarm company and they lock you out... I can also send you the (legal) link to the DSC programming software if you buy one

Agreed, I used what SH provided and the buttons were perfect (I used all upper case).

Hi, I might be the blind leading the blind (I have my own set of issues on these devices ) For 1 - did you define the ramp rate at the scene level for each of the devices? Also I notice if one does this then clicks the device under the scene the locally applied ramp rate is different. I am unsure how these two ramp rates in the scene interact - might want to try playing? For 2 - for the sub button if you want to make it control a scene you have to set it is a controller - so you would say no to the responder message. FWIW this is what my topology output shows for my KPD - it is an example of where use the ABCD buttons to control the %brightness of the load attached to the on/off load buttons (I am using the keypad dimmer) http://forum.universal-devices.com/topic/15314-mobilinc-connect-with-4223-not-working/

In my house the load and line are never white - just the neutral. Both my load and line and black. So I concur get a $10 voltage detecting pen

Awesome, sounds like a great partnership. Does the OEM have to code up the portal (because I am sure they want something that looks nice for the iGeneration and it might be custom to their OEM implementation) or did you create a new portal? If you created new portal can we get it to?

I have ~30 insteon SWL and KPD, with a few non-dual band devices, my assumption was that I didn't need to worry about bridging the two sides of my supply or noise as there would be a redundant mesh in the house of the RF and the power line and that the repeating nature of the devices would ensure that all the RF devices would act as bridges and help route messages around any gaps in the dual mesh? Is this flawed thinking on my part and I should have bridge and filters? I have had few reachability issues - most seems to be limited to just the 5 button KPDs when programming them - I still think there is an inherent fault in those devices....

Agree I need to be more precise. So to be super specific I am talking about two 2334-232 Keypad Dimmers. This is neither a SWL or a KPL as the term linc is not used in their name. I had said SWL because I knew KPLs didn't control loads directly like the 2334-232 does. So can we agree on the forum these are called KPDs? I was being lazy in terms because this was 2334-232 thread and while it may have only 5 responders it does have 6 buttons - that's how many the wife counts And back to the matter at hand which solution should I try first a scene or editing/creating my programs to turn of the A/B/C/D LED when it detects the 2 load buttons was pushed or held?

I perhaps should have been clearer. There is ONLY a 6 button SWL not a KPL (I was using the term KPL a little loosely) that said I will see if I can create a scene that when the load buttons are used on the SWL it turns off the A/B/C/D buttons, I was worried that doing that would turn the scene(s) off that the A/B/C/D buttons control, rather than just the LEDs. Let me try and I can post results back here.

Awesome I really should learn to RTFM more , I did read the IR sensor and assumed the door sensor was same procedure.

Glad to help, I can only guess the universal-devices domain is on some spam list. I wonder if there is a way to get it removed....

Not sure I quite understand. The other level is not a scene, this a switchlinc dimmer so it is just the load - are you saying I should make the D button a responder to the load on/off