This object is in archive!
"Old" virtual switches do react on URL request, new ones not
In Progress
Every virtual switch has a URL (Endpoint STATE). This URL ends with a "state=". If one puts a 1 at the end, the respective switch changes to true/on or with a 0 to false/off.
This works fine for virtual switches which are some month old. New switches do not react on this method. I tried this with a ZIPABOX and also with a ZIPATILE. New switches do not react.
The same problem 
No connection
Real-time notifications may not work
I jave same issue. No explanation why. Zipato, do you know?
I jave same issue. No explanation why. Zipato, do you know?
Hello. At my house it works.
Hello. At my house it works.
Yeah the problem seems to be individual for a handful of users.
We're looking into it, for starters you will get a couple of questions in your tickets in order to help us out.
Yeah the problem seems to be individual for a handful of users.
We're looking into it, for starters you will get a couple of questions in your tickets in order to help us out.
I have the same issue. My old virtual switches defined in previous Firmware versions still works on the latest version when triggered from the HTTP command but the new ones defined in the latest firmware version doesn't work when they are triggered from an HTTP get request.
Olivier
I have the same issue. My old virtual switches defined in previous Firmware versions still works on the latest version when triggered from the HTTP command but the new ones defined in the latest firmware version doesn't work when they are triggered from an HTTP get request.
Olivier
Someone (I forgot who) noticed this a while ago, at the beginning this person even figured out how to obtain the http link to upload values using HTTP commands, however after a few months that stopped working too... I will search for the post.
Someone (I forgot who) noticed this a while ago, at the beginning this person even figured out how to obtain the http link to upload values using HTTP commands, however after a few months that stopped working too... I will search for the post.
It was me. The thing is that i had even a ticket made for this and guess what. After about 3 month the ticket was resolved. I have tested with the latest firmware on a couple of controllers and it works. The link in the switch state endpoint is working fine.
It was me. The thing is that i had even a ticket made for this and guess what. After about 3 month the ticket was resolved. I have tested with the latest firmware on a couple of controllers and it works. The link in the switch state endpoint is working fine.
Just to prove see the link.
https://community.zipato.com/topic/hidden-feature-https-link-for-virtual-switch
Just to prove see the link.
https://community.zipato.com/topic/hidden-feature-https-link-for-virtual-switch
So basically anyone who has problem, open ticket
So basically anyone who has problem, open ticket
Awesome, I wasn't sure if was you or David, both masters on Zipato. Thank you.
Awesome, I wasn't sure if was you or David, both masters on Zipato. Thank you.
I had to create a new virtual switch lately and suffers from the issue. I opened a ticket but support didn't resolve it, support only asks to be patient: "thank you for contacting us with this issue. This is a known issue and we are working on resolving it. Thank you for your patience."
Not reassuring given the fact that this is a 13 months old issue. And this has been my workaround with IFTTT until support for Google Home. Now I know that Google Home is not a priority anymore and that development has stopped, I am desperately stuck and considering an alternative box.
I had to create a new virtual switch lately and suffers from the issue. I opened a ticket but support didn't resolve it, support only asks to be patient: "thank you for contacting us with this issue. This is a known issue and we are working on resolving it. Thank you for your patience."
Not reassuring given the fact that this is a 13 months old issue. And this has been my workaround with IFTTT until support for Google Home. Now I know that Google Home is not a priority anymore and that development has stopped, I am desperately stuck and considering an alternative box.
I just tried again today and the new switch worked. I have create a few for the future !
Edit : The first one worked, and the second and third one don't work, and the fourth one worked. So it's not that it doesn't work for some users, it's that it doesn't work consistently, but it might work if you keep trying. It's the luck of the draw! Crap!
As explained in this thread https://community.zipato.com/topic/hidden-feature-https-link-for-virtual-switch
When it works you get attributeUrls through the API:
{ "link" : "endpoints/171bd7b9-a080-4db6-8212-95c937acf307", "apiKeys" : [ "1d2e3909-fd9f-4a0a-b5be-02f22e692d4b" ], "attributeUrls" : [ { "attribute" : "state", "attributeId" : 11, "uuid" : "c0691474-5754-439f-b4ce-2a6298ec055d", "url" : "https://my.zipato.com/zipato-web/remoting/attribute/set?serial=xxxxxxxxxxx&ep=171bd7b9-a080-4db6-8212-95c937acf307&apiKey=1d2e3909-fd9f-4a0a-b5be-02f22e692d4b&state="; } ], "category" : "ONOFF", "icon" : { "link" : "https://my.zipato.com/zipato-web/v2/types/system/HTTP+device";, "name" : "HTTP device", "endpointType" : "virtual.http", "relativeUrl" : "/virtual.http.png" }, "showIcon" : true, "supported" : false, "templateId" : "", "userIcon" : null, "uuid" : "171bd7b9-a080-4db6-8212-95c937acf307" }And you don't get the url when it doesn't work:{ "link" : "endpoints/1ed68118-a368-4665-8413-9f023b777fd9", "apiKeys" : [ "538e7cca-c413-4056-a4ac-949137800ed0" ], "attributeUrls" : [ ], "category" : "ONOFF", "icon" : { "link" : "https://my.zipato.com/zipato-web/v2/types/system/HTTP+device";, "name" : "HTTP device", "endpointType" : "virtual.http", "relativeUrl" : "/virtual.http.png" }, "showIcon" : true, "supported" : false, "templateId" : "", "userIcon" : null, "uuid" : "1ed68118-a368-4665-8413-9f023b777fd9" }I just tried again today and the new switch worked. I have create a few for the future !
Edit : The first one worked, and the second and third one don't work, and the fourth one worked. So it's not that it doesn't work for some users, it's that it doesn't work consistently, but it might work if you keep trying. It's the luck of the draw! Crap!
As explained in this thread https://community.zipato.com/topic/hidden-feature-https-link-for-virtual-switch
When it works you get attributeUrls through the API:
{ "link" : "endpoints/171bd7b9-a080-4db6-8212-95c937acf307", "apiKeys" : [ "1d2e3909-fd9f-4a0a-b5be-02f22e692d4b" ], "attributeUrls" : [ { "attribute" : "state", "attributeId" : 11, "uuid" : "c0691474-5754-439f-b4ce-2a6298ec055d", "url" : "https://my.zipato.com/zipato-web/remoting/attribute/set?serial=xxxxxxxxxxx&ep=171bd7b9-a080-4db6-8212-95c937acf307&apiKey=1d2e3909-fd9f-4a0a-b5be-02f22e692d4b&state="; } ], "category" : "ONOFF", "icon" : { "link" : "https://my.zipato.com/zipato-web/v2/types/system/HTTP+device";, "name" : "HTTP device", "endpointType" : "virtual.http", "relativeUrl" : "/virtual.http.png" }, "showIcon" : true, "supported" : false, "templateId" : "", "userIcon" : null, "uuid" : "171bd7b9-a080-4db6-8212-95c937acf307" }And you don't get the url when it doesn't work:{ "link" : "endpoints/1ed68118-a368-4665-8413-9f023b777fd9", "apiKeys" : [ "538e7cca-c413-4056-a4ac-949137800ed0" ], "attributeUrls" : [ ], "category" : "ONOFF", "icon" : { "link" : "https://my.zipato.com/zipato-web/v2/types/system/HTTP+device";, "name" : "HTTP device", "endpointType" : "virtual.http", "relativeUrl" : "/virtual.http.png" }, "showIcon" : true, "supported" : false, "templateId" : "", "userIcon" : null, "uuid" : "1ed68118-a368-4665-8413-9f023b777fd9" }Replies have been locked on this page!