paulbates

Michael I don't expect to get to 16, so I'm good. Thanks to you and Brian for your responses and help thinking it through. Paul

Thanks Michael, just finished that for my programs. The api is a grouping,like sprinklers, and then different types of messages are sent there... skipped, completed cycle etc. Do tell, the api limit is xx APIs? Paul

You can have a program that looks like this (I haven't tested this but it should work) if status 'light a' is on or status 'light b' is on or status 'light c' is on or status 'light d' is on ... etc... then set scene 'downstairs light key' on else set scene 'downstairs light key' off You've probably run into needing to create a scene for a keypad key to turn it on or off versus directly controlling the key, so create a one device scene with the key in it just for this purpose. For turning all the lights off, I use a program that looks for that keypad key to turn off, and control a scene with all of the lights in it as responders,. You could put them all in a scene controlled by the key, but keep in mind that if anyone turns that key on, all of the lights go on. I personally have more problems with that and use a program in this kind of case Paul

Hi Brian, sure I currently have email notifications, but looking to move to something else like PO. It's strictly an activity log that I review by group. In today's world, I have the following email folders in outlook, with outlook filters to direct the notifications based on subject line cues: Folder Function ISY First Alert Programs that monitor the first alert smoke bridge post notifications here (no actuals to date, but tests go here) ISY HVAC Log Programs the monitor my thermostats for runtimes and errors post notifications here ISY Sprinkler Log Programs that monitor forecast, amount of on property rain, defer or run schedules- post notifications here ISY Critter Detector The program the monitors motion under our deck and turns on a flood light posts notifications here The separate PO apps I create will be used to group the notifications, that's how I want to manage the bombardment of notifications.. I can look in time order, or look under the each app Once I'm sure I have PO setup right, I will eventually stop emailing. Paul

To confirm, both the kpl key and the dimmer are both in the scene as controllers (the text for both is red)? If not, remove the one that is not a controller, add it back as a controller and try again. If they are already both controllers and its not working, right click on each of the 2 devices, 1 at a time, restore device and try it again. Paul

Hi Brian- Good catch. I only had one option, a=xxxxx. It looks like I had entered something incorrectly, as it works for user and group keys now and comes under the defined app. If I don't specify app a=xxxxx, PO creates and app entry for 'E-mail Gateway' and all mail messages go there, no grouping. Whether Network resource or email group, it looks like I still need to define multiple PO apps to group the messages. The trade off then is between creating new network resources per PO group, or creating new isy email groups per PO group. These will be the paths for the different methods: ISY Network Resource -> PO ISY Notification -> gmail -> PO I'll have to touch the programs either way. Probably easier to go direct from the network resource? Paul

When you set a device as a controller for a scene, its also a responder. However an device can only be a controller for one and only one scene. You you should be able to add the keypad keys and lights as responders to the all off/ good night switch. I do that for my kitchen lights.

Thanks bgav! I tested too. Also, the user key can be replaced with the group key, that works.. and removes the need for maint on the ISY as mobile devices are added, replaced etc. The notification comes through quickly too. However, to keep the groupings I want, I need to add the +a=<apptoken> to the email address. When I do that, the ISY sends the message out, pushover counts it, but it never makes it to the device. :S Paul

bgav So I keep the same notification model, and add a email address to my groups in the admin console. That's pretty easy, I will give that a try Thanks! Paul

I'm adding pushover notifications to my ISY. I have it technically working, what I'm looking for is approaches to organizing notifications. My requirement is the ability to group the notifications; sprinkler, hvac, firstalert, etc. Today I group different types of notifications in email folders using filters. I want to keep this model in the pushover app, and I can do that in pushover: define my own pushover apps for each of those groups name them accordingly, use the appropriate app token/key in separate network resources on the ISY to send the notifications Before I head down the 'grouping by app' path, I'm looking to see if there are other approaches that can be shared, or if anyone had experience with the many predefined pushover apps might help? Paul

Przemek I just ran mine, 47 devices, 3 times in a row, 221 links each time. One other thing to check, is the serial cable to the ISY. Unplug both ends and snap back in, or see if you have a replacement cable. If that doesn't change anything, I'm going stay with it being a defective PLM, new as it may be... Paul

Przemek You'll have more than one link per device.. as you indicate keypads might have 1 per key, and then also links for scenes. The low number is too low. If you are looking at this table because your programs are not initiating from activity from the network as they should, or insteon devices are not turning on from programs as they should... that's the sign its dying its time to request a warranty replacement. Paul

Przemek I had a new one die last march, at almost 3 months to the day. How many links are you seeing, approximate high count and low count? Paul

Przemek How old is your PLM? A varying, flaky link table can be the sign of a dying PLM. Especially if its at, or over 2 years old. Paul

My bad on x10 in the console, those are not in there, but they can be tested with programs. Right click on the program in question and "run then" to test You don't need the x10 module, unless you want logical names for x10 devices instead of HC/UC Paul

Interesting thought Michael. I wonder the pendulum will swing UDI's way, at least a little, especially from this group of users? Two way IFTTT via the portal sweetens the pot for them. Paul

Thanks for taking time to write up your story. The ISY is a very capable device and UDI is unique in their close contact and support of their users. Welcome to the forums! Paul

Hi John If you watch the admin console while turning the mini remote on and off, do you see mini remote device indicate "on" when you turn it on? If you use the admin console to turn A7 on and off manually, what happens? Paul

Hi Update the If statement to use Control / switched on (as jerlands suggested), and add the 2 lines to the then clause test sensor - [ID 014B][Parent 0032] If Control '32.7A.4D.1 - Door Sensor' is switched On Then Set 'Master Bedroom / M/Bedroom light' On Wait 5 minutes Set 'Master Bedroom / M/Bedroom light' Off Else - No Actions - (To add one, press 'Action')

Tim- Yep, and that's the point, as also evidenced by the dash buttons and tags Paul

Sorry that happened. As an FYI, devices from SmartenIT like the ezflora are immune to the all on. These devices naming scheme starts with EZ-. Older versions of Insteon devices that can be controlled like switches and iolincs and the naming scheme ends with -linc; these devices listen for the 'all on' and are likely to respond to it. The 'all on' feature was removed in many of the devices manufactured in the last couple of years Paul

Are you seeing the 1010 symbols next to devices, is that the symptom? If yes, and if you have scenes and your wireless devices are sensors, this is likely expected behavior. Scenes actually exist in related devices like controllers (sensors) and responders (switches), and those devices have to be touched when a related device changes. If you have the Pro model ISY, you can click an icon to defer wireless updates till you can do them one at a time Paul

I think you'er faced with the same issue for led strings. However, for Christmas / string lights, I add the plug portion of an old phone charger, that does it. I've not had this issue with screw in bulbs, and my insteon lamplincs are gen 1.

Smarthome actually did this to replace the first defective generation of hub 1s in early 2013. One of the services SH offered was to burn the current hub's insteon ID into the the replacement hub. The replacement hub with the old ID was shipped, restore link table to the hub, and go on your way. I would gladly pay $10 more today for a replacement PLM to have that same feature; burn in my current defective PLMs address to a new PLM. Its possible, I've seen it done, but only in that one case. Paul

Another suggestion is to put all of those device set commands and 'on levels' in a single scene, and only turn the scene on. The reason is that each of those set commands in the current program sends a message out to the switch, and and then the switch sends a confirmation back to the PLM confirming. If only one switch has to retry its confirmation for some reason (line noise), that retry could block the following set command on the powerline. Also, to expand on jerlands comment on HS migration; if you had scenes in your devices under HS, I would delete and recreate them all from scratch using the ISY admin console. I migrated from HS too, and tried to have the ISY discover all of my scenes created under HS. I had some difficulties with that and ended up progressively recreating scenes function by function using the ISY. Paul