bmercier

In the dialog box, click on the question mark to get help.

In ISY Portal, under Connectivity | IFTTT / Webhooks, you can enter devices there and have them be triggered from an external source. This is triggered using a simple HTTP GET. To get the URL, click on the icon besides the X. You could control this using IFTTT or anything that can trigger call urls. This could be as simple as a few URLs in an email for your installer. This is relatively safe as only the devices entered there can be triggered. However, if you have other webhooks for different purposes, then this gives away the key. I would change the key after the installer has passed. Benoit

ISY Scene exposed as a Google Home Scene When you add a scene in ISY Portal, and leave the Google Home Category to Scene, please be aware that the scene will not show in the device list which may lead you to think it's not discovered. But no, the scene is there and can be controlled. ISY Scene exposed as a Light When an ISY Scene is configured with the Google Home Category Light, Switch or Outlet, Google Home will think your scene is an actual device. When clicking on the device in the App, this will query the device, which obviously is not possible in the ISY world. Until now, ISY Portal would return an error as a scene can't be queried. Previously, the Google Home app would show an error, but would still allow the user to turn on/off the device. But recently, the GH app changed and if the query fails, it no longer allow the end user to turn on/off the device. The following fix has been implemented: When the scene is queried, portal now returns it as off, instead of an error. In the app, the device will show as off, which can be inaccurate. However, the app now allows to turn on/off the device, and will show the "normal" state after a turn on / turn off. EDIT 2020-05-06 ISY Scene exposed as a Light has been enhanced. When the scene is queried by GH, ISY Portal will check the status of a member of the scene and use it as an indicator of the scene status. It will use the first controller node, if available, or otherwise the first node. If this node is non-zero, the scene will be considered On. It may not be 100% accurate because a scene turned on could in fact turn off a device, but the assumption is that in most cases, when turning on a scene, we want to turn on devices to a certain preset other than zero.

I concur I don't know either, unfortunately. Benoit

The initial goal for the set/raise/lower syntax was to provide a generic way to control devices and not specific to Fanlinc. So the presets for low / medium / high are: 25, 50 and 80%. On a fanlinc, anything below 50% is low, 50 to nearly 99% is medium, and 100% is high. Perhaps I could enhance this by having different presets when a fanlinc is detected. Will talk to Michel. This could help you:

It must be that Nest locks are not recognized as locks by ISY Portal. Please send me the output of: http://<your ISY>/rest/nodes/<your lock device address> If using the admin console, you can unlock your front door, then yes, the ISY skill will allow you to unlock the door through Google Home. Benoit

Unfortunately no.

Try to discover devices. When choosing open/close, in addition to the on/off, you should see ‘device state’ with an enable button. When choosing raise/lower, in addition to the on/off, you should see a ‘device state’ slider allowing you to select from 0 to 100. Sent from my iPhone using Tapatalk

Try controlling them from the Alexa app to rule out potential pronunciation issues. Sent from my iPhone using Tapatalk

You could use a state variable to control your blinds. The variable will have a value from 0 to 100%. Then, use a program to do whatever you want based on the state variable, such as: If {MyStateVar} > 0 Then Set {MyBlindA} to {MyStateVar} Set {MyBlindB} to {MyStateVar} Set {MyBlindC} to {MyStateVar} Else Set {MyBlindA} to 0 Set {MyBlindB} to 0 Set {MyBlindC} to 0 Benoit

In the original post, I was talking about a limitation where lowest value you could use was 1. Amazon fixed the API, I changed the skill so that 0 is now allowed. Benoit

You can now control your locks using Google Home. To enable this feature: On ISY Portal, go to Select Tools | Connectivity | Google Home Add a lock to your device list, then save Ask "Ok Google, sync my devices" Things you can ask: Ok Google, lock <spoken> Ok Google, unlock <spoken> Ok Google, is <spoken> locked? Benoit

No worries

There has been no changes to this area of ISY Portal for a very long time (Years). Specifying the 443 port should not cause a problem, it's the port used by default when using https, but it's also completely unnecessary. I think the browser might had the authorization header set for different credentials in cache, and removing the 443 might have reset/changed it (?). Benoit

When logging in to ISY Portal, try to use web access to turn off the device in question. If this works (it should), you can see the URL used in the developer console (use F12 to open it). If it doesn’t work in a browser, then it must be that the URL or the credentials are different. Sent from my iPhone using Tapatalk

I know the credentials are valid. Please do what I recommended. Sent from my iPhone using Tapatalk

Use the same credentials you used to login to ISY Portal. Then make sure the ISY is in the account and has been authorized. Round indicator must be green. Benoit

Fix is in production. When using a fanlinc, requesting to set the speed to medium will indeed set it to medium. Benoit

Can you do me a favor? Please try: http://<your isy>/rest/nodes/<your fanlinc>/cmd/DON/128 And let me know if this turns it to medium. At this moment, when setting to medium, the actual value passed is 127. Thanks, Benoit

In that admin console, can you close your garage door by issuing a turn off on the iolinc device? Open/Close are synonyms for turn on/turn off. I think your iolinc is configured to momentarily close contact when you issue a turn on, which triggers your garage door movement. Benoit

The ISY skill now supports Open / Close / Set / Raise / Lower semantics.

The ISY skill now allows for more ways to interact with devices. You can now use Open/Close, Raise/Lower and Set syntax to set devices and variable values. To enable this feature: On ISY Portal, go to Select Tools | Connectivity | Amazon Echo Edit one of your "spokens" In the Alexa Category, choose one of these new options: Device with Open/Close syntax Device with Set/Lower/Raise syntax Save your "spoken" After changing the Alexa Category, ask "Alexa, discover my devices" When you use "Device with Open/Close syntax" In addition to the regular turn on/turn off, you will now be able to say: Alexa, open <device> Alexa, close <device> Alexa, is <device> open? When you use "Device with Set/Lower/Raise syntax" In addition to the regular turn on/turn off, you will now be able to say: Alexa, open <device> Alexa, close <device> Alexa, set <device> to <close | low | medium | high | maximum | open> Alexa, set <device> to <any number from 1 to 100> Alexa, raise <device> Alexa, raise <device> by <number> Alexa, lower <device> Alexa, lower <device> by <number> Alexa, what is <device> set to? Please note that this Alexa category is available for devices and state variables only. In the case of variables, when setting up your spoken, it is recommended to use a turn off value of 0, and turn on value of 100.

Yes and no. ISY Portal interprets 0 as a Open, and tells Alexa. To my knowledge, that how other devices work. Benoit

I have no clue. @Michel Kohanim might be able to help here. Benoit

What is the result of /rest/nodes/n001_dsc1_z03 ? Most likely, the issue lies with the value used by the nodeserver to represent open/close. Benoit