apostolakisl

Both of those programs have "then" clauses which change the status of a device which is in the "if" clause. So the program will re-trigger itself and trigger the other program, possibly back and forth. If you want to check the status of a device in the "if" and based on that status change that status in the "then", then you must disable the program and have an additional program which does a "run if" on that program. The key here is to understand triggers. STATUS is a trigger upon ANY change in the device. CONTROL is a trigger only upon execution of THAT SPECIFIC command (ie switched on).

the red left edge means the last time the program did something, it was the "else" clause. disabling a program means it won't spontaneously run. In other words, the "if" clause will only check its own conditions when something else tells it to "run if". Typically another program or less likely from an outside REST command or by someone manually telling it to "run if/then/else".

See, you did figure it out. ?

Yes, putting the number "1" works (in place of the variable).

It works from a browser. I did not include the authentication in the url, I entered it into when requested afterwards.

Sorry, not sure exactly what you mean by the above. This is what the ISY network resource lists in the "actual" box. Again, this all works using my port forwarding directly to ISY. GET /isy/randomlettersandnumberscutandpastedfromportal/rest/vars/set/2/1/${mod.weather.temp.current} HTTP/1.1 Host: my.isy.io:443 User-Agent: Mozilla/4.0 Connection: Close Content-Type: application/x-www-form-urlencoded Authorization: Basic thenumbers/lettersgeneratedbyencoderusingmyportalusername/password Note:I do use a special character in my password, if that matters. Below is what actually works using port forwarding GET /rest/vars/set/2/1/${mod.weather.temp.current} HTTP/1.1 Host: myurl.no-ip.biz:443 User-Agent: Mozilla/4.0 Connection: Close Content-Type: application/x-www-form-urlencoded Authorization: Basic thenumbers/lettersgeneratedbyencodeusingmyregularuser/password

That was a typo (in the forum only). It is set to my.isy.io

I left my port as 443, which is what I was already using for https

Not working. I started with my working network resource and copied it. I was already using https, so no change. Changed host to: my.iso.io Added to the path all the info preceding the /rest . . .: /isy/lotsofrandomlettersandnumbers/rest/vars/set/2/1/${mod.weather.temp.current} Changed authorization to: logon username for portal (my email) logon password for portal And it gives me an error, tcp client read response fail

So on an ISY network resource from one ISY to another that currently works, I copy and paste the "URL to ISY" into the "Host" section, and leave all else the same? Including the "authorization"? Is this in the wiki? I didn't see it, but that doesn't mean it isn't there.

I'd like to send a REST command to the ISY through the portal. I have two ISY's at different locations and they send some info back and forth. Currently using my self-signed certificate to do this. But now that I have portal, I would like to close the port forwarding and go through the portal. The only way I see to do this is via IFTTT (though I'm not even positive on that since I haven't actually tried it), but that just adds a whole other step and confusion. I can turn the GeoFence nodes on/off via a URL that the portal generates. I would very much like URL's that can control other nodes/variables/programs/etc.

If you are doing this from a webbrowser, you only need to put credentials in once. After that, the session does not require you repeat the credentials for further queries. If you are doing this from outside your LAN, using http is wide open. Your user/credentials will be wide open to anyone who wants to intercept your traffic. This is easy pickin if you are on a public wifi. You need to setup https on your ISY.

The wiki doesn't point out that for every change you make to your echo configuration on the portal, you have to "discover devices" from the echo. For someone like me who has already configured the Google home and used the update button on the portal, this is not at all intuitive. The "live update" button would seem to be declaring itself as updating echo as you make changes, when in fact it is not. The wiki only says this about that button: Proactive State Update This will require the live update to be active. When you go to your Amazon Echo device list, make sure to enable the Live Update -- NOTE: This may not be working properly at this time I'm not even sure what the above means or if it is currently working or not. And if it needs to be on, why do we even have the option of turning it off? IN SUMMARY: 1) Wiki needs to document language for using inputs on AV 2) Wiki needs to explain what the live update button is for in more clear terms. I don't know why echo needs to receive status updates from my devices. Does that mean if I manually turn a light on, echo knows it? 3) Wiki needs to point out that for any and all changes to your echo configuration in the portal, you need to "discover devices", even if you haven't added any devices.

OK, I see where to hover now. Still, should put the language in the wiki. This stinkin language is quite specific and so hard to remember. Seriously, it is like the SNL skit where the old people keep yelling crap at their alexa.

Ive tried hovering over every different thing there is and I don't get any dialogue boxes. Using Chrome.

Yeaahhhh! It is the word "change" I needed. Need to add that to the wiki.

I kind of realized that after I unlinked the device and realized you had to do the discover. But still, nothing on input selection. I have changed the volume and turned it on/off, but no input. Alexa says stuff like that device can't do that or hmmmm . . .

OK, but I still did "forget" and discover, the device is there on the alexa app.

The device is there and other features work. I am trying things like "alexa set input to satellite on device" and "alexa set device input to satellite" I'm feeling like that SNL skit here.

I have toggled the live update, I have gone in and "forgotten" the AV device and re-discovered.

I"ve tried all kinds of things from just numbers (numerals or written out) to things like satellite and CD and seedee.

I'm having trouble getting the AV inputs to work. What is the correct language? The wiki does not include the language for inputs.

I added an AV device to my Alexa without any errors in the process. But it didn't work. I finally unlinked then relinked it and now it works.

You are correct, it has been quite some time since most (maybe all) Insteon devices required a reboot after setting up links.