bmercier

Find the program ID in the admin console, then type it in the search box in ISY Portal. I think that you may once had a program with that same ID entered in the spokens. If you delete that program from the admin console, and later on create another one which would reuses the same ID, you would observe this behavior. Benoit

I don't know much iRule, but you seem to be doing it right. I think the issue is that it is trying to do straight HTTP over port 443. You need to use HTTPS. This is an excerpt from the support page: If your IP address or URL require Secure socket connection, you simply put HTTP:// in front of the IP address or URL (https://192.168.0.69) Benoit.

You can do the following; Boomark https://my.isy.io On the login: Click "Remember me", so you don't have to login anymore Instead of clicking on "Portal Login", click the down arrow and select "Go to my ISY". This will bring you directly to the UDAjax page. This preference will be saved for the next time. NOTE: You need to set your preferred ISY under My Profile for this to work. Benoit

Unfortunately, it's not possible to brighten/dim scenes with Google Home. The Google Home API only allows to set an absolute brightness, which cannot work with a scene. You may notice that you can brighten or dim a regular light, but under the cover, GH determines what the absolute level should be and sends that command. Benoit

Yes, but they will use the same spokens, just like if you have 2 echos. You will probably want to use sub-accounts to have different sets of spokens. Sent from my iPad using Tapatalk

Hello Dave, This should be working. We can investigate the logs in order to see what's happening. Could you open a ticket with the following information: UUID Program ID (You can see it in the programs lisy, in the far right column) ISY Portal User profile Date and time of your test, and please specify time zone. Thanks, Benoit.

I asked Google for clarifications, and I'm told that thermostat support has been released TODAY. It's possible that Google worked directly with others with an early release of the API, but as of yesterday, that was not available to us. So thermostat support is coming. At this point, it's a matter of priorities. Thanks, Benoit.

You may also want to try turning on and off individual devices. Maybe you have an insteon or ZWave communication problem? If the problem is indeed the scene, I'm not the best suited to help you as I personally don't use scenes much. But I know that those who could help would need more informations like what you have in the scene exactly, and we you are experiencing. They will also want to know what there is in the event viewer. I would suggest a new post in Questions and answers. Benoit

In the admin console, are you able to turn on/off the scene reliably? When you issue a command using Alexa, only a single REST API is called for the scene. Devices in the scene should all follow the settings, or not at all. In other words, either the scene on/off works, or not. If it does not work, I suspect that echo is understanding another device, and turning it on/off. But first, make sure the scene works as expected using the admin console. Benoit.

Response time with chunked encoding should be faster than without it. I measured it with my own ISY in the prod environment, and for /rest/nodes, it was 20% faster. I was getting 850ms from request to completed response, vs 1.05s without chunked encoding. That's the round trip from browser< -> ISY Portal <-> ISY. While testing I found a subtle bug that was fixed this morning. This may be what you experienced. Benoit

You should have a main device for your thermostat. Could you try with this one, instead of the AC sub device? That should work. Benoit

Yes, I confirm chunked encoding is now supported. I will investigate the response time. Thanks, Benoit

For Amazon, this is though for a thermostat, which is implicitly "inside". An outside sensor is probably not a use case they though of. Benoit

When you make a change to the spoken name, it needs to be re-discovered by Alexa first. So, you can go to the alexa app, and click "Discover" again. Alternatively, you can simply say "Alexa, refresh my devices". Also, I must add that Alexa does an automatic refresh every +/- 1 hours. So, it's probably already refreshed by now. Benoit.

Just a quick note to let you know the problem has been fixed in dev. It should be live on the next deployment to production.

Please open a ticket with the following informations. 1 - Your UUID 2 - The result of this command for the 3 devices: http://<your ISY IP>/rest/nodes/<your device address> And please reference this post. Thanks, Benoit

Then I think the geofence radius is too small. I would recommend to increase the radius to at least 2-3 houses away. In most use cases, we don't that much accuracy. Unless you have family or friends real close. Benoit

It would show true. The idea is that if anyone is home, then home is considered occupied. The status of the location is simply a OR of each members. If this is not useful, then one can simply not use a location. It's optional. Benoit

An easier way to test is to just type the URL in a browser. https://my.isy.io/api/location/<insertkey here>/report/in The URL can be triggered either with a POST or a GET. Benoit

It's coming back us as we speak Benoit

You can use Mobilinc to connect to ISY Portal. Once on ISY Portal, if you want to use Geofencing, I would recommend to use ISY Portal node server occupancy module. You can create different fences that maps to virtual devices on ISY, representing occupancy for your various geo fences. Geo fence triggering can be done using Locative. Benoit

I doubt this problem has anything to do the PLM replacement. The Alexa discovery process is independant from the ISY devices. If a device is visible in ISY Portal/Amazon echo, it should be discoverable, even if the ISY is not online, even if it does not exists anymore on ISY. Please check under My Profile. Make sure your preferred ISY is set. Also, I would try to redo the account linking on ISY Portal side, and Amazon echo/smart home skill side. Benoit

Good point, I did not realize that. However, he may be using Mobilinc without Mobilinc Portal, either through ISY Portal, an open port, or locally only. But if he is using Mobilinc portal, then obviously this will work only if Mobilinc portal has thermostat support implemented. I do not know. Benoit.

Then it should be really easy. First, can you confirm how you control you lights with echo? Alexa, turn on ... (You are using the smart home skill) OR Alexa, tell ISY to turn on... (You are using the ISY custom skill) If you are using the smart home skill, great, that's what you need. In ISY Portal, under Amazon Echo, just click Add devices, choose your thermostat, and give it a name. Then, say "Alexa, refresh my devices". And you're done. You can control your thermostat just like any other thermostat controlled by echo. If you are using the custom skill, you should instead use the smart home skill. Benoit

No need to do anything. It's just fixes. Benoit.