Xathros

Duh. Thanks Lee. Guess I've spent too much time recently dealing with wireless devices... Now all I need to do is search out what scenes and programs will need to be adjusted after the delete and add. -Xathros

Thanks Michel, Turns out, this is the one device that is the hardest to deal with in my entire installation. Its the fanlinc in my MBR fan. I had a hell of a time stuffing that into the box as the fan has a very small canopy and the bracket fills most of it. Funny thing is, this device appears to be working just fine. Guess I have another project for this weekend. Hope I can get to the set button without having to pull the fanlinc out of the box. -Xathros

Hi Paul- I more suspect just a corrupted file than an actual problem with the SD card. Its not that old and I doubt I'm anywhere near is max number of writes at this point. -Xathros

Hello, I am seeing a lot of this: Mon 2015/11/16 11:42:28 PM System -110014 /CONF/149DAC.REC in my error log lately. It is always with this one file. What is this file? I'm thinking it may be a network resource rule but I'm not sure. If it is, is there any way to tell what rule ID it belongs to? Is it safe to delete? Thanks in advance. -Xathros

That is excellent news and a far cry from the days when Amazon wouldn't even acknowledge UDI's existence. Lets hope this is the beginnings of a good working relationship between UDI and Amazon. -Xathros

Well, you can use the portal for remote access to your ISY without the need for port forwarding in your router. -Xathros

You most certainly can, however, that doesn't solve the problem here. He is using a single Lamplink with multiple scenes each using a different OnLevel to control MANY activities. Off only has a single OnLevel of 0% How to know which activity the single Off is directed at? There are 100 (or 255 depending on how you get there) flavors of "on" but only 1 flavor of "Off" -Xathros

The portal does not offer anything currently for integration with Sonos. You would continue to use network resources for that. The Portal will allow integration with Amazon echo once the skill is approved and published by Amazon (hopefully within 10-ish days based on other threads) and may offer IFTTT integration somewhere further down the line. No other integrations have been announced that I am aware of. -Xathros

Hi Chuck- The only solution I see would be to set your programs up using integer variables to toggle the activity with each "Scene On" call and not use Off at all. While not a perfect solution, I think it's better than what you are currently doing and would double the total number of possible activities available via the single lamplinc. To accomplish this, your programs would need to set the lamplinc back to Off after toggling so that the same scene can be called a second time and result in a change of status at the lamplinc. Example Code: If Status 'Lamplinc' is 50% And $i.FamTV is 0 Then Resource 'AVControl - FR DirecTV DVR On' Resource 'AVControl - FR Onkyo On' Resource 'AVControl - FR Samsung TV On' $i.FamTV = 1 Set 'Lamplinc' Off Else (nothing to see here) If Status 'Lamplinc' is 50% And $i.FamTV is 1 Then Resource 'AVControl - FR DirecTV DVR Off' Resource 'AVControl - FR Onkyo Off' Resource 'AVControl - FR Samsung TV Off' $i.FamTV = 0 Set 'Lamplinc' Off Else (nothing to see here) Thoughts? -Xathros

Big517- Answers depend on your route. Currently, you can set up the WeMo or Hue emulators using info found in this thread. That method does require a middleman computer like a Pi or an always on Windoze box. This method does not require the portal. If you wait for the ISY Connected Home/Skill to be approved, then you will need the portal but there won't be a need for a middleman computer or any of the emulators and mapping tools in this thread and setup is expected to be very straight forward using the Spoken name field for scenes/devices and program names all taken straight from the ISY. For the going the Pi route, I believe there is only one REQUIRED piece (The emulator). The mapping tool while not REQUIRED, does make set up MUCH easier. The mapper is not running full time - just used for configuration via a Windoze box. The emulator runs full time on either Windoze or a Pi. Hope that helps. -Xathros

This is a good reason for using Lamplincs in place of Range Extenders for a phase bridge (as @Teken regularly recommends)... Pseudo virtual devices.

Not given the current unknown situation with the wiring. At a minimum, you would need 3 insulated conductors running from the switch box to the fan box (assuming the power was available in the fan box). -Xathros

Just got distracted by the day job and spaced the fact that the scene name was the interface to the Alexa command... Glad I could be of assistance! -Xathros

In this case there MUST be a third location(Second switch location or junction box) that both the wall box and ceiling box run to and gather power from. I still have a sneaky feeling that there are more wires in the ceiling box. Can you pull the fan bracket and look further up into that ceiling hole? -Xathros

So between my initial concept and the 2nd rev using different On-Levels, I managed to completely miss the whole point of my point! Of course this will work! Feeling a bit like an idiot.... -Xathros

Well, it doesn't really. My initial thought here was a device or button would represent one activity and allow for On/off = start/stop. Multiplexing many commands into it via brightness levels would require rather odd language with Alexa thus taking you right back to the unnatural usage you are trying to avoid in the first place. Worse yet, you would need to remember what brightness a particular task is assigned. At that point, the "Alexa, tell Izzy to run ..." implementation is better in my opinion. -Xathros

2 blacks and 2 whites at the wall switch? Or one black and one white? -Xathros

What you describe above makes not sense to me. There needs to be more than 2 wires at either the ceiling box or the wall switch box. Maybe they are hiding above the fan hanger in the ceiling box. The KPL will not directly control any load. Cap it's red wire. Instead, Scenes and/or programs will be used to instruct the Fanlinc based on input from the KPL via Insteon links. Here is what I suspect you have and need: -Xathros

Seems viable to me! Might require some testing to ensure multiple commands are not executed as the Lamplinc ramps up or down through several brightness levels on it's way to the level most recently requested. -Xathros

No. Simply Name a button or device for simplicity with Alexa. Example: Scene "Family Room TV' with only 'FamilyRoomKPL-C' as a responder. Program: If Status 'FamilyRoomKPL-C' is On And Status 'FamilyRoomKPL-C' IsNot Off Then Resource 'AVControl - FR DirecTV DVR On' Resource 'AVControl - FR Onkyo On' Resource 'AVControl - FR Samsung TV On' Else Resource 'AVControl - FR DirecTV DVR Off' Resource 'AVControl - FR Onkyo Off' Resource 'AVControl - FR Samsung TV Off' Then when you say "Alexa, Turn On Family Room TV" she will turn on the scene called "Family Room TV", the program will see the status change on the KPL button and issue your resource calls. Same with "Turn Off Family Room TV" Make sense? In addition, for those who don't like to talk to electronics, you have a KPL button that performs the same function. -Xathros

I can see a workaround involving a physical Insteon device like a LampLinc or even a KPL button. You could name a KPL Button Scene for "Family Room TV" and have a program that monitors the Status of that button. When the button turns on, the program runs then and issues your network resource commands to turn on the AV equipment. When the button turns Off, the program runs else to shut things down. Granted, this would be better with a virtual device but seems like a viable workaround in the meantime. -Xathros

Well no, but, programs can call other programs so it is possible to at least chain things together. -Xathros ]

Thanks for the update. Fingers crossed! -Xathros

Excellent! I'm sure you will be happier with the switch as you have it now. Glad you got everything working. Thanks for posting back. -Xathros

So then the issue with using Izzy would be the humans remembering to call the skill "Izzy" but the device "ISY"? I think I understand. -Xathros