dbuss

Can you reach the ISY through the UDI portal?

Tom, Which mobile app are you referring to when you say, "my mobile app can't access anything there"?

I use similar programs with Elk and Z-Wave locks and it works well for me.

Yes, they do. Sent from my XT1650 using Tapatalk

Add a "Wait" to your first line in the "Then" Sent from my XT1650 using Tapatalk

1. Log into your Isy Portal 2. In the "Select Tool" drop-down menu select "Connectivity". 3. Then select "Amazon Echo". 4. Then click on the 'Device" tab in the "Add" ribbon. 5. Select the devise you want to add from the drop-down menu.

Did you add the new device to the Amazon echo device list in the Isy portal?

Would a Routine work for this?

You need to turn on Telnet in your device manager on your computer. If you Google turn on telnet windows 10 you will find the instructions. Sent from my XT1650 using Tapatalk

You can also use Polyglot, https://forum.universal-devices.com/forum/111-polyglot/ and a Raspberry Pi to control these devices. There are node servers in the Node Server store for each of the lights you mention. here's a great video on installing Polyglot on a Raspberry Pi. https://forum.universal-devices.com/forum/111-polyglot/ I use this method for Lifx and other node servers it works very well.

If you are using the Mobilinc portal, you cannot use the UDI portal. It needs to be one or the other. If you choose the UDI portal you can still use Mobilinc by connecting to your ISY and not using the Mobilinc portal.

Did you add the new devices to Alexa in the ISY portal? Sent from my XT1650 using Tapatalk

It seems as though you have the Isy portal for location "B" associated with your location "A" Amazon account. Sent from my XT1650 using Tapatalk

It seems that at some point you connected your Isy portal for location "B" to your Amazon account for location "A". I would remove the Isy Smart Home Skill from the Alexa account for location "A". After it's removed, I would add that skil back and make sure that it's linked to the correct Isy portal account. Then discover devices and make sure the devices from location "A" are discovered.

When you log into Amazon account "B" does it show the Echo devices at that location correctly?

Sign into Amazon account "B" and compare the devices in the two accounts.

It appears you are logged into location "B" from location "A" and your location "A" dots were added to location "B". Try signing out of the current Alexa account you are logged into on your computer and then sign again making sure you are signing into location "A" Amazon account.

I would log into Amazon Alexa for location "A" from your computer and forget all devices.. Then discover devices from your computer. Let us know what location the devices are discovered from.

Do any of your devices, groups or scenes show up when you click on "Smart Home"?

When you sign into your ISY portal for this account do your devices show up in the Amazon device List?

Are you getting this information on your smartphone app or on your computer?

Have you logged into your Alexa app on both your computer and smartphone using the same Alexa account? Sent from my XT1650 using Tapatalk

That is exactly how I had mine set up and it no longer works as it did before. As Benoit stated, there are work arounds, but I didn't find those to be a good solution for me. They may work for others though.

@Mango here's the response from Benoit as to why scenes no longer work with groups. This is the expected behavior. ISY scenes do not have a status. When Alexa queries the "device", the skill knows it's a scene and will return an error as the status is unknown. This is the drawback to exposing scenes as devices. Regarding the turn off not working, it's also expected. If Alexa think it's off, when you press the button, it will send a turn on. But after turning it on, it queries the status... which returns an error. So it is considered off. If you would like a work-around and get a status, you could wrap your scenes inside a program. Programs do have a status. So if you use Alexa to turn on a program, which turn on the scene, then the status returned will be on (program status will be true). But, if the scene is activated outside the scope of the program, or if your light is manually turned on/off, then the status of the program won't match the device. You could go a step further by adding an if your program. Example: If device is not off turn on device else turn off device. This way, the program status will always reflect the status of the light. Benoit

This thread solved my r "could not retrieve file /conf/11.prp" problem.