This object is in archive!
Virtual Sensor
Known
Hi,
Since the last firmware, the virtual sensor, do not propose the switch activate or desactivate URL, We can not see these option ? It is normal ? there are alternative solution ?
Thanks
The same problem 
No connection
Real-time notifications may not work
I made test few minute ago by creating new virtual sensor and i had the same issue . . .
May be zipato will be delete this functionnality not really securised and user wil have to use API.
Team may give more detail to users when delete features . . . it's really bad when we discover that . . .
I made test few minute ago by creating new virtual sensor and i had the same issue . . .
May be zipato will be delete this functionnality not really securised and user wil have to use API.
Team may give more detail to users when delete features . . . it's really bad when we discover that . . .
Yes, can you explain us (quickly please, because we can 't create new virtual sensor, but also new virtual meter !)) how can we mange for updating status of a virtual sensor from an external application (like pushinbox for example) ?
Yes, can you explain us (quickly please, because we can 't create new virtual sensor, but also new virtual meter !)) how can we mange for updating status of a virtual sensor from an external application (like pushinbox for example) ?
I tried via the url but I get an error 403 Tomcat . . . This is what I feared , this feature has been removed and of course without any information of users, it's nice! ! !
It's these little touches that put me off against zipato !
And by the way , I feel that this is not the only fonctionnalié . .. Now when I include my Fibaro FGK101 I little used or tamper nor the external button . . .
How can we have confidence in this box?
I LOVE ! ! !
I tried via the url but I get an error 403 Tomcat . . . This is what I feared , this feature has been removed and of course without any information of users, it's nice! ! !
It's these little touches that put me off against zipato !
And by the way , I feel that this is not the only fonctionnalié . .. Now when I include my Fibaro FGK101 I little used or tamper nor the external button . . .
How can we have confidence in this box?
I LOVE ! ! !
Hi sébastien,
Thanks for this fast reply. . .
It's a good news . . i know you prepare lot's of change . .. but you could understand that is not plaisant for us . . .
Can you tell me if is the same problem for the Fibaro FK101 because according the support's team it's normal operation that tamper and external button not appaer in device manager . . . because at final we loose feature of this Fibaro module like scene...
Hi sébastien,
Thanks for this fast reply. . .
It's a good news . . i know you prepare lot's of change . .. but you could understand that is not plaisant for us . . .
Can you tell me if is the same problem for the Fibaro FK101 because according the support's team it's normal operation that tamper and external button not appaer in device manager . . . because at final we loose feature of this Fibaro module like scene...
Can you explain us how can we mange for updating status of a virtual sensor from an external application until the new interface is coming ? it should be here one week ago as you said, so how much should we wait again ? (3 weeks ago you tell me to wait 1 or 2 weeks only for virtual meters bug !)
I know you are working for a new versionbut it is vers annoying to have the possibility to do nothing with our boxes !
Can you explain us how can we mange for updating status of a virtual sensor from an external application until the new interface is coming ? it should be here one week ago as you said, so how much should we wait again ? (3 weeks ago you tell me to wait 1 or 2 weeks only for virtual meters bug !)
I know you are working for a new versionbut it is vers annoying to have the possibility to do nothing with our boxes !
I wouldn't say it's not possible to do anything with the box:-) Currently there is an issue with the API key within a URL, as we are switching APIs in behind. This will be fixed very soon.
As for the FGK101, it has a tamper and external switch in one. So this is not a real feature but hack, which is currently not supported by Zipato, as we consider tamper very serious. However, if customers like it, we will support it.
I wouldn't say it's not possible to do anything with the box:-) Currently there is an issue with the API key within a URL, as we are switching APIs in behind. This will be fixed very soon.
As for the FGK101, it has a tamper and external switch in one. So this is not a real feature but hack, which is currently not supported by Zipato, as we consider tamper very serious. However, if customers like it, we will support it.
Sebastien , I never said we can not do anything with the zipabox , maybe you 've mixed my answer with that domoteek . I just said it is not pleasant to discover a feature is no longer available. Your message is reassuring for users, but we can not guess that the problem is temporary.
On the FGK101 I do not absolutely understand your réponce . There are two weeks my FGK101 was properly included in zipabox . I used it for my letter box . I did not use the original magnetic contact, but an external magnetic contact . I created rules on the external button using scenes modes (double click or triple click) . Everything worked !
Unfortunately , after a battery change , it has lost the connection to the box . Have not found any other solution I have excluded from the network and have included it again and now I am told I can not use it as before because it is supposedly not supported by the zipabox ? This is a feature that has been removed it is no doubt for me or my box and then my module has a problem. . .
Sebastien , I never said we can not do anything with the zipabox , maybe you 've mixed my answer with that domoteek . I just said it is not pleasant to discover a feature is no longer available. Your message is reassuring for users, but we can not guess that the problem is temporary.
On the FGK101 I do not absolutely understand your réponce . There are two weeks my FGK101 was properly included in zipabox . I used it for my letter box . I did not use the original magnetic contact, but an external magnetic contact . I created rules on the external button using scenes modes (double click or triple click) . Everything worked !
Unfortunately , after a battery change , it has lost the connection to the box . Have not found any other solution I have excluded from the network and have included it again and now I am told I can not use it as before because it is supposedly not supported by the zipabox ? This is a feature that has been removed it is no doubt for me or my box and then my module has a problem. . .
As for the FGK101, is should work as before now. However, I wouldn't recommend device as a security enabled if it allows messing around with the tamper.
As for the FGK101, is should work as before now. However, I wouldn't recommend device as a security enabled if it allows messing around with the tamper.
So can you explain us how can we use our virtual senor ? can you explain how should we use the api beause I am not a developper, that's why i choose a zipabox ! but if I have no other choice than using API, can you at least eplain us how we should use it please ? I would'not said i am not positive, but after waiting nearly 2 years, i Think it is my right to wait for a stable version now ! You can understand that we can't listen to "you should" wait a little bit" anymore ! We are hearing it since 2 years !!!
So please at least explain us how to deal with this bug usint the api please !
Thanks for your coming tutorial !
So can you explain us how can we use our virtual senor ? can you explain how should we use the api beause I am not a developper, that's why i choose a zipabox ! but if I have no other choice than using API, can you at least eplain us how we should use it please ? I would'not said i am not positive, but after waiting nearly 2 years, i Think it is my right to wait for a stable version now ! You can understand that we can't listen to "you should" wait a little bit" anymore ! We are hearing it since 2 years !!!
So please at least explain us how to deal with this bug usint the api please !
Thanks for your coming tutorial !
Hi,
Any news about this issue ?
This is stil not possible to get activate/desactivate URL for virtual sensor from new interface.
Thanks
Hi,
Any news about this issue ?
This is stil not possible to get activate/desactivate URL for virtual sensor from new interface.
Thanks
Replies have been locked on this page!