firstone

Find the file and right click on it and choose "Open". It will give you same error but with an option to keep going.

I'm pretty sure you can run program directly from Alexa routine. You can set it up as device or light. Don't remember for sure. But in that program you can then set up a delay and do whatever you need to do. So, basically, trigger program from routine rather than triggering program by some condition. This is how my program looks: Backyard - [ID 0027][Parent 0001] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Set 'Scenes / Backyard' On Set 'Living Room Receiver / Zone3' Power on Else Set 'Scenes / Backyard' Off Set 'Living Room Receiver / Zone3' Power off As for you sunset/sunrise program, I'd just set up another routine, like "Alexa, pretend I'm at home" and run your random lights.

I'm not sure I follow. Currently, if you go to AV device and select "Network Resource", you just get a list. All I'm asking is to add another option "Node" or whatever, and you'll get a list of all nodes with it's commands: node1 - cmd1 node1 - cmd2 node2 - cmd1 etc. I don't see why compliance, hints or anything else is needed here. Whatever the long term plans are, this seems like a fairy simple and quick changes, even if temporary.

Perhaps in the list you can just list all combinations of nodes + available commands? Basically, I've written my AVRemote with the sole purpose of using to control AV devices. I've converted it into Node server since. But I'm still stuck using original network resources based implementation because node server cannot be used for AV devices.

@bmercierAre there any plans on allowing polyglot nodes in AV devices? I see them in regular devices drop down but AV device still only list program, variable or network resource.

I do not believe it's possible to control Alexa skills from ISY. I think you best bet would be to find some network resources that can control Sony TV specifically or go with some for of IR control.

I think that's exactly the point. It's hardly a viable long term business strategy to invest into some custom security (with questionable result) and charge extra $100 for it, for instance. For every person who'll appreciate it, there will be 1000s who'd buy competitors product and save $100. Also, most if not all those exploits aren't because of some weaknesses in existing protocol bot rather dumb stuff like default passwords, simple passwords, buffer overflow from unchecked buffer, etc. In other words, problems with implementation rather than the protocol.And that, in turn, because those companies pay as little as possible and outsource firmware to other firms in offshore markets. And that, of course, goes back to price pressure. You can try to do your best to protect yourself with good firewalls, good passwords, etc. But at the end of the day, you can't loose sleep over it. if you want to loose sleep over something, read Data and Goliath or Weapons of Math Destruction.

There are commercial products already available, such as: https://www.yubico.com And prior to that there were RSA authentication devices and other brands. Those are acceptable for user authentication but in this case there is still an attack vector in the device itself. More importantly, I don't think anybody's thinking about. In one case, attacker can get into google's network or some bank or financial institution and cause billions of damage. In another case they can turn off your light or cause your fridge to defrost. I don't know if there's financial incentive here. Unless you have a giant vault full of gold controlled by IoT device. There is nothing that cannot be addressed by some crypto algo with rolling keys or some such. And perhaps it will in the future. But for now it's a pipe dream. IoT devices use commercially available solutions, oauth2, etc. Nobody's going out of the way until something else is widely available.

They put stickers on outside on devices that are covered with wall plates and whatnot. If they put it on outside of door sensor, it's unsightly and can come off. With that in mind, I think there's a function in ISY specifically for those door sensors. I think it puts it ISY into linking mode and tells you to open sensor and press button. I'm pretty sure mine was auto detected.

Tried "restore device". Didn't help. Still same issue. By "slave" i meant "a switch that doesn't control physical load". Pretty sure links are set up correctly aside from this issue. Also, this seems to be specific to load on level only. Somehow it gets temporarily overwritten after local double tap.

I have 2 dimmers connected (via links). 2477 with load and 2476 as slave. Local on level is set to 40% and the scene is also 40%. Everything works. Until I turn on to 100% on local via double tap on load switch. After that operating load switch locally always turns it on to 100%. ISY is showing 40% but the switch goes to 100%. Until I go to slave switch and turn it on to 40% from there. After that it, again, works as expected. Any ideas? Is it a defective switch? It works otherwise so not a huge deal. Just wondering.

This should be pinned somewhere or be in Alexa wiki. Unless it is and I just didn't see it.

Awesome. Thanks.

Is there a way to get "command" (on/off) from Alexa spoken command to pass to ISY program? Otherwise, I have to set up 2 programs (no big deal) with 2 distinct spoken words (inconvenient).

Noticed the same issue but this time with using ISY programs. If added as "scene', it doesn't show up in Routine actions. But if added as "light", it works .

Awesome. Thanks.

This is a good workaround. After changing it to light, it allowed me to add it as device to routine. Still doesn't explain why scene doesn't work but better than nothing.

Hue, nanoleaf and Harmony hub, controlled through respective skills, rather than isy skill.

So, yet another question about Alexa. I can't seem to include Instead based Scenes into Alexa routines. I see them in Scenes in Alexa portal (and iOS app) and can execute them. But they're missing when selection actions for Routine. Insteon devices are there. All other scenes are there. But Insteon scenes are not.

Yes, it worked with simpler names. Thanks. Didn't think "netflix" would be hard to understand but at least I know there's no issue with these devices.

As the title says. I have AV devices set up and mostly working but cannot get inputs commands to work on any of devices. I"m assuming I should be using names that you specify on the right side? When I say, for example, "Alexa, change input to netlix on TV", it just gives error beep. All other commands work fine, including changing volume to a numeric value. What am I doing wrong?

Thank you. I've missed that part about user variables and assumed "dot" notation was just a way or naming variables and it would do by name substitution. The second part works now. As for your first question, it's not tivo dvr that sets channel but rather tivo AV device in ISY Portal. Sorry if that wasn't obvious. But, everything seems to work now. Including skill setting variable. Thank you. Another annoying thing, Alexa seems to have trouble with word "tivo". Most of the time it says "I couldn't find the skill tiv-O". I've tried "tivo", "teevo" and even tried saying it as "t-ai-vo", just in case. Worked sometimes but not reliable. Works much better as "dvr". Don't think this one is the problem with the skill though.

I've been tying to set up AV devices. And by most part, they're working. Except things like set channel and set volume. Those don't seem to set state variables. Not even sure how to troubleshoot it. Another issue is that variable substitution doesn't seem to work for network resources. I've looked at some posts and copy network resource set up and still it's sending request with variable name, without substitution. Path set to /tivo/set_channel/${tivo.set_channel}, mode to Raw Text or C Escaped. Software version 4.6.2.