paulbates

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

You're welcome. Glad it worked.

Hi, Did you try factory resetting the 2476, then do a restore device to it? I have older togglincs that act flaky after years of running correctly, that usually fixes it. Paul

As a related topic, I've wanted to see market penetration and trajectory for Insteon / Zwave / Zigbee / Wifi iot devices. How many are out there, and how much is it growing? I've asked next market if that was something they would look at but no response

Hi, welcome to the ISY and the forums! I also migrated to the ISY about a year and a half ago from another windows based solution, for the same reason. What's important to the program folder structure is that it helps you. My structure is by function / room as shown in the picture as a reference, but there's no single way to do it. Paul

AJ Constraints for outbound initiated traffic is more of a statement of if you trust the device initiating outbound transactions. Its been common for a while for home based "server" functions, including the HA appliances, NAS's, Smart TVs, thermostats, cloud backup up solutions like webroot, idrive.. etc, to pick the port that they would like to use. The isy is a very specific purpose network appliance, not a formal full feature OS with capabilities that can catch a virus, etc. I'm good with that being unpublished Paul

I'm guessing it doesn't always want to use something specific, there's some value in "security by obscurity". The port would have to be guessed by potential hackers.

AJ If there are firewall rules preventing devices from accessing the internet, that would explain it. The portal model assumes that the ISY can "phone home" from an outbound perspective. Paul

Follow up topic: The SB is i2cs. I'm wondering if anyone has upped the retries for messages initiated from it. I have no problems in general insteon signal wise, but want to be sure that SB messages get through, I set it to 3 retries. Since the SB is not very active, my assumption is that a setting of 3 would be reasonable and increase the insurance that the message makes it to the PLM. My SB is not linked to other devices, it just notifies the PLM Thoughts? Paul

Teken, That's a great question, that might be related. I'm keeping an eye on it, but I have a battery swap schedule for most of my battery sensor devices, so I may not find out. Paul