Cannot set value to virtual device via http

Same here. Always 404. Weather not working and also ifttt work around not working.

Basically sunrise/sunset functionality totally broken...

same for me..

seems to be that zipato want to make all users angry. after several weeks of problems with the weatherstation (sunrise/sunset), all users moved this function to IFTTT by setting attributes via the API. after all users completed this changes, zipato changed the API so that it is not possible to change attributes..

I will now move to another provider..

Same here, totally unreliable. Did anyone reverted to the old firmware to see if the API calls work?

Same here. I did some investigations. It appeared that they have changed the url of a http device. Previously its was http://.......?value1 / value2=value. Now every endpoint has a diifferent uuid and ?value=. So no number. And of course completely incompatible with the previous solution.

Without any warning. I have some 10-15 virtual devices. It makes me sick. Leaving Zipato after 5 years. Lack of communication, poor software development, poor support and lousy promises and so on.

Cheers!

I agree John, Yesterday I've created also sunset/sunrise rules using ifttt and that also doesn't work anymore. What's next? controller advise? I'm using the zipatile b/c of the fact that it has the integrated touch screen.

Thanks zipato for changing all the uid since this last update.

i have more than 30 webhook request using those previous uid and now i have to edit all my configuration.

bye bye zipato

Hi all

I use a Light Sensor for my backup. That works very well (Nacht/Night is the virtual sensor that usually the zipabox activated or deactivated by sunrise or sunset. This virutal sensor control all other rules / Lichtsensor = Light/Lux Sensor) :

I didn't upgrade the firmware (and won't for a while..) but yesterday all my IFTTT routines failed. Can Zipato please comment when (or whether) this will be restored.

If you create a new virtual device, you are not getting a response url back using : GET /virtualEndpoints/{uuid}

Also have problems with my http requests. This is totally unacceptable. What kind of service provider makes changes without even inform the customers? We don't even know if this was changed on purpose (work as designed) or somebody had some bad luck when thinking...

In the version 1.3.29 the virtual devices are also not working anymore! So it has nothing to do with the new fimware!

No, I think they have done some changes in their cloud environment without thinking it through enough.

Do you still experience this problem?