bmercier

We currently are not planning any change for the custom skill. IMHO, we should just remove it. It still has a few features that the smart home skill has, but they are hard to use, and having both causes confusion Sent from my iPhone using Tapatalk

The commands listed there on the wiki are for the ISY Smart Home skill. Some of these commands will only be live this coming Sunday. This includes locks support and some thermostat queries. When you use tell izzy to, you are referring to the ISY custom skill. This already supports locks, and has been so from the beginning. Starting sunday, the ISY custom skill will not be too relevant anymore, as most of the functionnality will now be available through the ISY smart home skill.

LOL

I'm an anti-procrastinator Benoit.

Hi, I found out the issue. It would happen both in Safari and Chrome whenever we are using private/incognito mode. This is now fixed, and will be in production on the next update. Benoit.

Hi Stu, I installed Firefox v52 ESR for testing, but it seems to work correctly. Do you get an error message or something? What does it do exactly? Are you using 64 or 32 bit? Thanks, Benoit

Portal login should work from an iPad. Benoit

No it's not. Try resetting your password.

Hello John, When you say "Alexa, tell isy to lock the .....", you are talking to the ISY custom skill. This has been working since the first implementation. Now, smart home skills (Alexa, lock ...) also support this since late February. This is currently developed and will be available on the next ISY Portal update. Note that you can only lock a door, or query the status. You cannot unlock. Alexa smart home skills do not support this for security reasons. Benoit

Hello Stu, My apologies if I was not clear, I was not suggesting any of this. Brighten to X and Dim to X works, but it's the same as saying turn on to x. It sets to an absolute value. So of course absolute values does not work with scenes. The solution proposed is to set a state variable to the intended dim level, then use a program to set that level to the devices that we want. More details here for brandon: 1. Create a state variable in admin console (Programs->Variables->State) 2. In ISY Portal, Select tools->Connectivity->Amazon Echo, click on Add Variable, and choose a spoken for your variable. Optionnally, you could set a turn on value to 100. That will be the dim level use if you just "Turn on" without specifying a value. 3. Then create a program like this: If $MyState is not 1000,00000000 Then Set 'MyDevice1' On '$MyState %' Set 'MyDevice2' On '$MyState %' Set 'MyDevice3' On '$MyState %' Else - No Actions - (To add one, press 'Action') The program will trigger each time the state var is change, and will always evaluate to true (Dim level will never be 1000%). In the then statement, you basically set the dim level of your devices to the same value as the state variable. TIP: In the admin console, when you are on the line to your device, click twice on the arrow just below the percent box. Note: I believe this requires firmware level 5.x Benoit.

It's a tricky one. In order to avoid groups, your alternatives are ISY scenes, programs or state variables. A scene would be the easiest. You can do things like dim or brighten. However, you can't set it to a specific percentage. What you could do is use a state var as a container to your percentage. In ISY Portal, you can assign a spoken to a state variable. On ISY, you could have a program that reacts to the state variable, and adjust the level of lights accordingly. Alexa turn on <my spoken> to <x> percent Will set your state var to the value x. Your program will take the value and set the lights accordingly. Benoit.

Hi Javi, There is currently no plans to do parsing within ISY Portal. We use conversation actions with API.AI. We use their slot filling and webhooks to ISY Portal to perform the action and return the result. Benoit.

Hi Michael, To avoid support calls, there is a popup if 5.0.9 is not installed. Pilot users like yourself do not have this check so you can continue using 5.0.8T1. Benoit.

No. The bug here is stricly related to node servers accessing ISY through the portal connection. Requests being made by ISY Portal through the permanent socket are not supposed to require authentication, but in 5.0.8, it did for some specific REST APIs. Benoit

Yes and no. A node server is basically an extension to an ISY. Properties are updated by the node server. (Example thermostat temperature) Controls can initiated by the ISY. (Changing a thermostat setpoint) So, this can be 2-way, or just 1-way. In the case of this new occupancy feature it's 1-way. Occupancy is reported as a node property that you can use in a program. Benoit

I investigated the logs. You are right, this will not work with 5.0.8. I just recalled I had that problem with 5.0.8. Testing was done with 5.0.8T1 (5.0.8 with a temporary fix) 5.0.9 will be required. Benoit.

You can try it with 5.0.8+, it does work. There is a known bug that may happen when adding/removing mobile devices. If it happens, just retry it after a few minutes. This is likely to be fixed in 5.0.9. When your mobile devices are created successfully, it's stable. Benoit

I don't think it's possible with Amazon Echo. This does not answer you questions, but FYI, you can do that with Google Home, with the help of Chromecast audio. Benoit

Can you confirm what you are saying to Alexa? Is it: 1. "Alexa, tell izzy to turn on test"? (This is for the ISY skill) 2. "Alexa, turn on test"? (This is for the smart home skill) These are 2 totally different things. The error message that you get seems to refer to the custom skill (option 1). Try option 2. Benoit

It was created initially at the request of a forum user. I believe the purpose was to document the list of spoken, probably for a chart to help users build it. An export was easy to do, as it is simply a dump of the spoken table in the correct format. An import could certainly be done, but requires more development efforts. We need to implement validations, and provide an import error log to the user. This is currently not in the plans. Benoit.

Hi Larry, Please make a search for "every". It should find it. Having an empty name, which is the first column, is precisely the bug that was solved. When the name is not there, the UI should still show the line, but using the spoken as the name. If you still have difficulty with this entry after doing a search, please PM me your uuid. Other bugs: Variables used are not highlighted in the pulldown menu list, as other categories are. This is on purpose. This allows you to enter multiple spokens for the same variable, but with different turn on values. Duplication displays "Device already has a spoken" instead of "Scene already has a spoken" Thanks, this is now fixed. Displaying 100 entries, when returning to the list screen, displays off the top of the webpage and it is not accessible or scrollable to access titles or items in that section. Which browser are you using? Please PM me a screenshot. Thanks, Benoit.

Thanks for the bug report. I was able to reproduce the problem, and this is now fixed. For those entries that are incorrect, please just edit and re-save them, the ISY name will be refreshed. Then, on the next Alexa discovery, the ISY name will be picked up as well. Thanks, Benoit.

The echo app allows you to create groups of devices. This can be useful if you want to turn on or turn off multiple devices at once. However, the recommended way would be to handle groups at the ISY level, either through the use of scenes, programs, or even state variables (Yes, state variables are now supported). The problem with Alexa groups is that whenever you turn on/turn off a group, Alexa will send multiple command individually that end up being queued for the ISY. You will notice that if you have large groups, all devices will be turned on or turned off one after the other, but that takes some time to complete. Handling groups natively on the ISY will speed up the process. Also, it's worth noting that when you use large groups, timeout errors in ISY portal are generated which are monitored by UDI and Amazon. They are expected when groups are used, but still, it's better not to have them. Benoit.

I recommend the upgrade. Everything that is working in V1 works equally well in V2, so there are no drawbacks at all. Thermostat support is a big plus, and it's working well too. There are some concerns discussed here on the forum related to the auto mode. But if you just use off/heat/cool, it works well. Benoit.

The "ISY smart home skill", is a smart home skill, which means that it fits the Alexa built-in home automation framework. It has more limited capabilities compared to a custom skill, but the speech recognition is much better. It allows to: Turn on, Turn off, Turn on to x%, brighten, dim, set temperature to, increase temperature, decrease temperature. Devices can be an ISY device (most of them, locks for example are not supported), a scene or a program The way to invoke a smart home skill: Alexa, turn on <device> The "ISY skill" is a custom skill, in Amazon's terminology. A custom skill can basically do anything as you have the freedom to define all the possible ways of asking for something, and the corresponding action. The ISY custom skill was developed prior to the smart home skill, and since the latest release of the smart home skill, there is less and less interesting use cases. Examples of things the ISY skill allows to do which you can't with the smart home skill: - Get the current temp of a thermostat - Get the current setpoint(s) of a thermostat - Change the mode of a thermostat (smart home skills allow to turn it off) - Lock/unlock The way to invoke this skill: Alexa, tell izzy to turn on <device> Benoit.