bmercier

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

Exactly, nothing to do In portal, nor Alexa. Sent from my iPhone using Tapatalk

The scene stays in ISY. Alexa only tells your ISY to turn on or off the scene. This means that when you change your ISY scene, you have nothing else to do. Sent from my iPhone using Tapatalk

This is indeed easy and now implemented in production. Thanks for the suggestion. Benoit

This is great news. The code on ISY Portal side has not changed for a very long time now, so this tells me Google fixed something. Benoit

When you initially link with Universal Devices, you have a blue ISY Portal login page where you have to enter your ISY Portal user and password. What I'm saying is that when you want to sync your devices from ISY Portal, you have to be logged in with the same ISY Portal user and password you used to link. The Google account you use can be a totally different email address, it does not matter. Thanks for confirming that the sync works. I unfortunately have no clue why GH would return an error message.

I spent a few hours today in an attempt to resolve this. First of all, here's some information about how device sync works; 1. Device sync works by Google calling a portal API which returns the devices AND the "agentUserId", which is a unique ID to identify the user. 2. Portal can call a google API (we call it the HomeGraph API) to trigger a sync. We call it a syncRequest. It basically tells GH to call us for a Sync (line 1 above). The authentication to the Homegraph API is system wide (it's not specific to the user). The payload in the request has the agentUserId which tells GH for which user to trigger a request. Please keep in mind that the logged in user MUST BE THE SAME AS THE ONE GH WAS LINKED TO. So, whenever we ask GH to "Sync my devices", only 1 is done. Whenever we go to ISY Portal and click on to send the spokens, 2 is done, which calls 1. QUESTIONS: 1. Now, to my knowledge, 1 usually works well. Only 2 stops working after a while, for some reason. In this case, Jimbo also has a problem with 1, as per the screen shot (Thanks for the screen shot). Now, does anyone else also have a problem with 1 (Vocally request "Sync my devices")? 2. Despite the PERMISSION_ERROR with 2, can someone confirm if the sync works when we get the error? According to the logs, the sync happens and returns no errors. Benoit

You don't need 2 accounts. However, you need to have 2 user profiles, one for each homes. For your 2 user profiles, login and click my profile, make sure that "Amazon Echo and Google Home ISY" is set to "Use preferred ISY", and set the preferred ISY to their corresponding ISY. Each Amazon account will need to link with their corresponding ISY Portal user profile. So the overall link is this: Amazon echo -> Amazon account -> ISY Portal User Profile -> ISY. Benoit

Thanks for the suggestion. The feature is now implemented for Alexa, GH and also IFTTT. Benoit

Please try again, it should be working fine now. Benoit

Looks like the address is wrong. Try: http://<your isy ip>/rest/nodes This will give you all of your nodes. From there, you can locate the kpl button node and try the url with the correct address, or just cut and paste the node from /rest/nodes Benoit

In a browser, go to: http://<your isy ip>/rest/nodes/<your kpl button address>

Please post the result of: /rest/nodes/<your kpl button address> Benoit

You are definitely using 1.1.3. Sent from my iPhone using Tapatalk

1. Search for the postback url in the log: 2020-01-20 03:41:12 info: NS: Starting Subscription with postback URL https://pgc-ns-ingress.isy.io/ns/ring-<uuid>-1/event 2. Try the url in a browser, but replace "event" by "test". You should get a message saying the test is successful. This simply tests the communication to the nodeserver. 3. Now try the url in a browser once again, but remove "event", let the url finish with the forward slash. You should get a message saying "Node server is healthy". If so, this confirms you are running 1.1.3. Benoit

Looks like a PGC bug where the version number is not updated. But clearly, the nodeserver is indeed updated to 1.1.3. Benoit

This feature will be added, but it's not scheduled yet. Benoit

I'm not sure why. PGC should bring the new version when restarting. That's what James is saying. Benoit.

To my knowledge, precision can't be passed. So I just send as many digits as required after the decimal point. Like this: /rest/nodes/<address>/cmd/CLISPH/23.5/4 This is how I set the value with the uom: const valueWithUom = (t.isInsteon ? newValue * 2 : newValue).toFixed(precision) + ((t.uom && t.uom.length && !t.isInsteon) ? '/' + t.uom : ''); Benoit