Jump to content

Scyto

Members
  • Posts

    618
  • Joined

  • Last visited

Everything posted by Scyto

  1. awesome, could you put a link to it in your signature?
  2. Is this by design? Any chance the topology generator will be updated to show zwave devices in scenes?
  3. 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
  4. 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.
  5. 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?
  6. 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....
  7. 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
  8. Agreed, I used what SH provided and the buttons were perfect (I used all upper case).
  9. 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/
  10. 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
  11. 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?
  12. 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?
  13. 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.
  14. Awesome I really should learn to RTFM more , I did read the IR sensor and assumed the door sensor was same procedure.
  15. 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....
  16. 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
  17. Me too, arrives same day
  18. FWIW this is my program for a similar scenario - designed to turn the light on when I open the door, but only during darkness and only if the light isn't already on. If From Sunset To Sunrise (next day) And Status 'Back of House / Back Door Sensor- Door Sensor' is 100% And Status 'Dining Room / Dining Room Cans' <= Off Then Set 'Dining Room / Dining Room Cans' 76% Else - No Actions - (To add one, press 'Action')
  19. haha I have same problem on my surface pro, so nice to hear this is on the list. I tried turning off and on the high-DPI setting on Jave program executable - strangely it does effect the size of some fonts in the java app, but not the main ones
  20. yes, I had similar issues and had to do a reset, seems to happen if comms to the device is funky it seems to corrupt it. I still have issues, for example I have 2 KPLs one controls CANS and other control SCONCES directly. I setup A thru D on one KPL to turn both the cans and sconces on at one of 4 predefined levels. So if I press say D it comes on at 75%, press D again the lights all go off and the D button becomes unlit. However if I (or usually my wife) press off on both KPLs the D button is still lit. Pressing it once toggles the D button light and effects no other change. Any suggestions how I get the D button light to turn off? I find these KPLs very difficult to manage....
  21. The battery devices I have are the motion sensor, leak sensor and hidden door sensor. Every time I wanted to make a write to them (like link to a scene) it said I had to go press the button on them to put it in linking mode. This is a hassle. Does this button change that? I ask because I don't see how I can 'write to battery devices all the time' if they need me to go and physically do something? what am I missing?
  22. I just re-commissioned my hidden door sensor and IR sensor (it was being used with a different controller). Given that to modify scene membership one has to put the sensor into pairing mode every time why not just use a program. I get this is only slightly onerous on the IR sensor (get it down, unscrew the back, press the button) but for the hidden door sensor it is annoying to have to remove it. My program worked just fine to turn lights on etc. Why not use just programs given how hard it is to modify on the fly? (PS anyone know what the jumper on the IR sensor is to 'allow full control of options by software' does and wether the ISY994i support this?)
  23. Hope this helps someone. I was testing the alerts services and could not get it to work, eventually I realized it was working fine to every email address I have except my outlook.com email. The message was not appearing in the junk mail folder either- I can only assume Microsoft has placed universal-devices.com on a block list? Anyways here is how to fix. Logon to the web version of outlook.com Click the cog (upper right) and then options Click safe and blocked senders Click safe senders add @universal-devices.com to the box on the left and click add to list >> This then ensures alerts work. It will be interesting to see what other mails from UD I was getting that vanished into the ether
  24. I am moving from using snap switch and Windows Phone 8 to iPhone 6. What are peoples favourite iOS apps to control the ISY - I need support for both Insteon and z-wave devices.
  25. @EricK - ahh I get your point this is about the other responders that actually control the load. Yes you are right if I fade up or down the dimmers or turn off the load then the A/B/C/D buttons don't reflect that. so great suggestion on the monitoring program. I will give that a go. @Everyone Else - after more testing I think I can say that setting the PLM access retry count to 2 has cured all the comms issues to the , sped up writing to the KPL (2334-2's) and cured the strange behaviors where they didn't do what they were supposed to do. ---edit--- spoke too soon, while this fixed the issues with my KPL's in the bedroom it did not for the ones in the basement, I think it is either faulty unit or issue with my mesh - is it possible to work out if both the RF and on-wire comms paths are working? ---edit 2-- For the basement KPL relocating the PLM solved the issue, so I guess there was a mesh issue for that node
×
×
  • Create New...