paulbates

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

Eddie You picked html output format. Have you tried either plain text, or \n at the end of html lines? Paul

Jim A thought is to not check the fan. Add a statement to your program to turn the fan on when humidity is needed. along with the statement for turning on the humidifier. It gets very dry here in the winter and I want humidity cycles running to the adjusted setpoint. We're in our second season of independent humidity cycles, and Its proven to improve health here. I also have an ISY program cycle my fans periodically after a certain period of no heat, cold or humidity cycles. Paul

To follow on Lee's thought, what does the program do? Does it perform any direct device commands right before the scene is called? Direct device commands will have acknowledgements coming back at the same time that scene is called in that case. Since scene commands are not acknowledged, some devices like powerline only might miss the command I would put the direct commands after the scene, if this is the case Paul

To manipulate the keypad keys, you need to add the button(s) you want to a scene, and then turn that scene on and off. It's not what you'd expect, but its how it works. A couple of additional considerations Turning the button on and off using a scene does only that... it does not activate programs or scenes associated with manually pressing the button...however.. You can group the devices you are turning on and off with the key in the scene so that one program statement turns them on and off As an example of the second bullet, I have my attic fan and dampers controlled by 3 keys on three different keypads in different locations. In one scene, I have the the three keypad keys as controllers, and the dampers and the fan as responders. The scene totally manages the dampers, fan and keys ...on and off, no program is required. Paul

One last suggestion, it may be the ezflora itself. Factory reset the ezflora. I don't know the steps, but the manual in the box should have it. Paul

Wierd. No reason I can think of. Ideas at this point: Close, then re-run the admin console ..or.. Unplug and replug in the ezflora .. if that doesn't work... repeat step 2, delete the ezflora and add it back in again Guessing a bit at this point Paul

Did you try New Insteon Device and manually selecting the ezflora? If you scroll down the list of devices, the ezflora is 4.00 Paul

Make sure that "Relay follows input" is not checked in the iolinc's options

Bob, no those are both the same. The Portal Module installed in the ISY provides another doorway to login to the ISY, using the portal email address and password as credentials. This applies to logging in to the admin console and ISY hosted web pages. When you attach directly to your ISY, either on your LAN or through an open router port, you use your User ID and Password that you originally set up in the ISY When you attach via the portal, you use your portal email address and password.. both for web logins, and for admin console. Paul

Glad you got closer to working! The keypad could possibly be a noise problem. Did you have to replace the original keypad for the same reason, unable to communicate with it? The only other suggestion I have is to use remove from folder for the keypad, and delete it. Try to add it back in. Paul

The ISY is missing links. I would start with the restoring a recent backup. I think something happened to the ISY image Make a back up now, then, Restore from the most recent backup you have before today, and review ISY links if it looks more comparable, rerun your tests Paul

Ok, the next level is to look at the details: For each of the two devices: Tools Diagnostics Show Device Links Tools Diagnostics Show ISY Links Post the results back here.

It looks like part of steps 4 and 5 are out of order, the PLM gets plugged in and then bring the ISY up http://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_.28PLM.29

Unplug the PLM and the ISY. Wait 10 seconds. Plug the PLM back, wait 5 seconds, plug the ISY back in Repeat the restore plm Paul

I would factory reset the iolinc and then restore device. I've had problems with one in my garage that I've had to handle that way. Paul

For the garage lights, I assume that that's an iolinc, and there is a scene linking the sensor to the switches that control the lights? If so, can you click on the scene, are the switches in there as responders? Edit: Sorry, your write up said program. Does the ISY recognize the io_linc in the properstate when the door is up vs down