apostolakisl

Clear your java cache. https://www.java.com/en/download/help/plugin_cache.html. If you just type java in the windows search box you'll see the java admin as an option. Delete all temporary files and applets. Then download the following. https://isy.universal-devices.com/start.jnlp It will put the iox launcher icon on your desktop and it will always get the right version. Even multiple versions if you have multiple isy's.

Both units are working now. I don't know why. The only thing I know of is that we had a circuit breaker pop that caused the wifi AP and managed switch that these thermostats use to reboot. But I find it hard to believe that this was fixed by that. Everything else on those devices worked fine before and after and I was able to get responses on port 80 doing "curl" queries from the polisy.

Today, I tried hit "discover" again, and for whatever reason, it finds the t7850 thermostat. The one that was working with nodelink. Still not finding the t7800 with the wifi adapter. I have no idea why today it is finding the one thermostat when it wouldn't before. I changed nothing.

For what it's worth. I have been using gmail for at least a decade now and it still works just like always.

Yes, new Alexa is not so literal. If you say "all lights" it doesn't look for something called "all lights", it behaves more like a human you asked to turn off all the lights. I think it is a better approach, but it takes some adjustment. I find it much better since I no longer need to say precisely the words, I can just say something that a reasonable person would recognize. And it is way better for people who don't know the words at all. And you can throw in a bunch of extraneous words like "could you please" kind of language and it doesn't mess it up.

Not exactly, you had touse the portal when you exposed the scene to Alexa in the first place. But it is much simpler to expose your Insteon/ISY scene to Alexa as a light or a switch and skip the routines. There are two independent designations here. 1) What it is in ISY, 2) What it is in Alexa. The two do not have to be the same. Notice that, in the portal, when you expose a device or scene (or variable, or program. . ) to Alexa, you have the option to tell Alexa it is any type of thing you want, it doesn't have to match what it is in ISY. Anything designated as a "light" or "switch" in Alexa will respond directly to voice commands. Anything designated a "scene" can only be addressed in a routine. I really don't know why you would designate something as a "scene" to Alexa. Both scenes and lights/switches are allowed to be targets of routines, so it isn't that. I guess if you want access to a device from an Alexa routine but don't want any "spoken" to trigger it, then setting it up as a scene will do that. When you set the "spoken" for a scene, it really isn't even that, it is just the name of it, speaking its name to Alexa won't do anything.

This is screwy, but. . . If you have an Insteon/ISY scene and you want Alexa to control it as if it were a single light, you just tell Alexa it is a light when you set it up in the ISY portal. When you add the scene, you need to start from the scenes tab so the portal gives you a list of all your scenes to select from, but from within the "spoken mapping" setup page, select that it is a light in the Alexa category.

I changed the T7800 to https and set a username and password. Nodelink when set to http gave the error that the connection was refused. I changed to https and added the username and password and now the error is a timeout error. So it seems that the thermostat is accepting the https authorization but then ignoring whatever command nodelink is issuing to it. I can only assume that there is something going on with a firmware mismatch.

I just successfully added the T7850 to Nodelink.

yes, I can ping both of them. Mostly the response times are in the 5-10ms, though a few are much longer. EDIT And I get a response on port 80. Not sure if I should check any other ports.

Polisy isn't connected to wifi, it is hard wired, only the thermostats are connected to ssid's. They are all on the same corporate vlan. No firewalls between devices. From a pc on the same vlan I get responses from the IP address of the thermostats. The manual also shows that it has options to http vs https. But once you turn on api, it greyed out to http. Perhaps https could be selected first and then you turn on api?

Yes, they are all on the same network as the polisy and of course the wifi is password secured, though that shouldn't have anything to do with anything. They connect to star net and I can ping them and I can go to the http:// address of the units and get a response. Lots of things on that network that polisy connects to fine. I set them to enabled local api right away when I first configured them. I have rebooted the one via a full 60 seconds power down. The http is just the venstar reporting that it is not requiring authentication for the api. I imagine yours says the same thing. Both of mine are identical on the page that toggles the api on/off.

@paulbates @hart2hart The local api is enabled on both of them. It was off by default and I clicked to turn it on. There is a second line that is greyed out that says it is http. If local api were off, I'm not sure I would get anything when I go to the url. For exmple, if I do a sensor query I get this. {"sensors":[{"name":"Thermostat","temp":73.0},{"name":"Space Temp","temp":73.0}]}

Chat GPT thinks it is the v5 firmware. It thinks when skyport is connected it restricts the local api. I don't know. I don't know how to get the older firmware to try. I suppose I can try disconnecting skyport.

I just installed a second Venstar T7850 this time. Same exact thing. So either there is some setting on the thermostat I am not setting correctly, or something is up with the node.