paulbates

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

Lee- I factory reset the SB, then relinked one of the sensors, then tested. Now it all works as documented by you / pdf. I'm guessing something wasn't right in the bridge for some time. Thank you. Paul

Thanks Lee The malfunction is on after the test and queried off as you indicate, but CO and smoke are blank, no setting either way. I've been checking the sensors, and I'm going to factory reset and re-link the smoke bridge to see if that helps Paul

I retried the the testing step Lee posted and compared to the manual, including unplugging and replugging the unit. I am getting the same results I usually receive, including now the malfunction node being on after the test. However if I query it, malfunction clears. I need to go and check each FA unit Paul

The smoke bridge device leaves some things to be desired. I had mine starting on Homeseer and migrated it to the ISY, with the same results you are reporting... eg that's working as designed I am able to get test to turn on when I test the system. And a cooking malfunction a few years ago set off the smoke indicator. (?) I'm not sure what unknown is, probably in case a newer model of detector adds a new message that the bridge doesn't know about, Its never turned on for me One other foible to report.. the low battery indicator only reports low battery for the detector the smoke bridge is linked to. If you link other detectors to your first detector, they're battery states will not be reported. Paul

Echo: Check Ecobee's site for how to discover them on the echo and what commands control them. There's a section in the FAQs for the Ecobee 3 (above link) specifically for Echo use Nodelink & ISY: You'll need to run V5 (beta) of ISY firmware, and follow the directions to install nodelink for ecobee. There's a Nodelink section of the board under Automation Shack / Nodelink There'll most likely be some learning curve involved. Paul

Matt I don't think you'll find it step by step. Here are the pieces and parts UDI has released Polyglot, which is a Pi compatible python library that can control the ISY. Polyglot is in the forum. Does it control zwave stats? Probably, I don't know for sure Sticking with the python theme, libraries would be required to pull a pop inbox, read a message and process its text. I'm sure they exist, but would have to be researched Paul:

The ISY can't receive that information directly, it would require a server like a Rasberry PI and coding. Provided you have a smartphone, you'd be better off with one of the low cost / free apps available on the site. Look under third party products, and recent posts from developers Paul

The echo now supports Ecobee with voice control. Combined with io_guy's NodeLink reporting and control through the ISY, the Ecobee becomes an even more compelling choice. https://www.ecobee.com/amazon-echo/

via Imgflip Meme Maker