This object is in archive!
Progress is slow at Zipato?
Known
Is it just me who thinks that progress is slow at Zipato?
Almost all of my 150 apps on my iPhone has been updated since Zipato updated its app.
I think in any case that Zipatos CEO Sebastain should write a short message on a weekly basis, about what they are working with and which focus Zipato have.
Sure, I have to admit that they are quick to respond if you have a problem, but then nothing happens. They answered me on the WT-2 Nexa switches, but not when they will be implemented. Only that they will be implemented, or when to change the Recommended configuration for different Nexa devices.
The same problem 
No connection
Real-time notifications may not work
Hello Jacob, I really don't understand your comment. Zipato is supporting the biggest number of protocols and devices in the world. We are even discussing here about some particular devices based on some proprietary/closed protocols which has been requested by some of our customers.
From you we got the roller shutter motor to support, which is also based proprietary protocol, as the manufacturer didn't care about the interconnectivity of that product. Although there are less than few users of this motor currently in our community, anyway, we expressed our interest to put some effort in possible integration of this protocol into our system.
On the other side you are writing here about our slow response, so I don't understand what exactly do you think we should do, and compering to which company we have slow response. Did you ever consider buying some products based on some standardized protocols at the first place? This would certainly speed up the process of integration on your side. Or did you call the manufacturer of that Nexa WT-2 switch and check how they are responsive and willing to integrate other systems?
I hope you will understand our effort to integrate as much as possible of these devices in order to support our users. And we would appreciate some patience at least for these few issues which are based solely on pure enthusiasm and willingness to help.
Hello Jacob, I really don't understand your comment. Zipato is supporting the biggest number of protocols and devices in the world. We are even discussing here about some particular devices based on some proprietary/closed protocols which has been requested by some of our customers.
From you we got the roller shutter motor to support, which is also based proprietary protocol, as the manufacturer didn't care about the interconnectivity of that product. Although there are less than few users of this motor currently in our community, anyway, we expressed our interest to put some effort in possible integration of this protocol into our system.
On the other side you are writing here about our slow response, so I don't understand what exactly do you think we should do, and compering to which company we have slow response. Did you ever consider buying some products based on some standardized protocols at the first place? This would certainly speed up the process of integration on your side. Or did you call the manufacturer of that Nexa WT-2 switch and check how they are responsive and willing to integrate other systems?
I hope you will understand our effort to integrate as much as possible of these devices in order to support our users. And we would appreciate some patience at least for these few issues which are based solely on pure enthusiasm and willingness to help.
Hello Jacob, I really don't understand your comment.
Zipato is supporting the biggest number of protocols and devices in the world.
I buy number of protocols, there Zipato are the winner, but numbers of devices. And lets say you are the winner in that aspect two. But defiantly Tellstick support more types of 433 MHz devices. But why haven’t you changed the Nexa devices association. It was a long time that I asked for this:
http://wiki.m.nu/index.php/Kompatibilitetsguide_433MHz_och_Z-wave-kontrollers#Kompatibilitetslista
That when you assign a Nexa device in the list of Nexa devices it works. Not that you have to choose another device in the list. Now when you want to add ECMR-250 you need to chose Nexa WMR-252 dimmer in the list? As soon as someone discover this it should be changed because it is a bug?
We are even discussing here about some particular devices based on some proprietary/closed protocols which has been requested by some of our customers.
This is not unique, also Tellstick is doing that and soon you will compete with Tellstick that will have z-wave version of there controller. I am more thinking of other threads that have waited 2 years for answer? Example, Logitech Harmony support? I don’t want the whole summer to pas to get support for blinds?
From you we got the roller shutter motor to support, which is also based proprietary protocol, as the manufacturer didn't care about the interconnectivity of that product. Although there are less than few users of this motor currently in our community, anyway, we expressed our interest to put some effort in possible integration of this protocol into our system.
The advantage of this particular blinds motor is that it is the same as RollerTrol that is quiet big in this segment, and to a good price. I don’t know how many users send their hardware to you, this should be a motivation to add some code? The better the total price of hardware is, the more Zipaboxes you will sell. More money in, is certainly something you will benefit from.
On the other side you are writing here about our slow response, so I don't understand what exactly do you think we should do, and compering to which company we have slow response. Did you ever consider buying some products based on some standardized protocols at the first place? This would certainly speed up the process of integration on your side. Or did you call the manufacturer of that Nexa WT-2 switch and check how they are responsive and willing to integrate other systems?
You should really go threw old threads and answer them publicly about status or plans. Now for me it looks like there is issues that never have bin considered or answered.
Yes I contacted them and they told me this:
Hey,
It never goes at creating product / apps that appeals to everyone, unfortunately.
Our focus with the experience we have since many years is that it should be simple, functional and, above all, user-friendly where there is self-explanatory.
433 Mhz is a very frequent frequency that many uses, however, it can still be encoded in such a way that the manufacturer / supplier can not release on its protocols.
We will make use of a transceiver 433 that "listens" to most of the codes within that band, but each individual code has still an API that we must adapt and build the app for, we will be ready for Nexa 433, Anslit, Provee and some others.
Z-Wave can be extremely sophisticated and fits rarely the masses of users, it's too complicated for Kalle Svensson to understand, to code, etc .. We have scaled down operations in Z-Wave yet done so that the user can combine Nexa 433 , Z-wave receiver / transmitter and Nexa wireless smoke detector at 868 Mhz,
Our app developers belonging to the advanced nature and can everything in iOS, so future adjustments are already documented.
Sincerely
Support
I hope you will understand our effort to integrate as much as possible of these devices in order to support our users. And we would appreciate some patience at least for these few issues which are based solely on pure enthusiasm and willingness to help.
I understand your effort, But app development should go faster and more often! Or at least info about what is going on in the background, there should be something to write about once a week.
Soon Nexa Bridge and Tellsticks version is her, use this time ahead of them to be even better.
Hello Jacob, I really don't understand your comment.
Zipato is supporting the biggest number of protocols and devices in the world.
I buy number of protocols, there Zipato are the winner, but numbers of devices. And lets say you are the winner in that aspect two. But defiantly Tellstick support more types of 433 MHz devices. But why haven’t you changed the Nexa devices association. It was a long time that I asked for this:
http://wiki.m.nu/index.php/Kompatibilitetsguide_433MHz_och_Z-wave-kontrollers#Kompatibilitetslista
That when you assign a Nexa device in the list of Nexa devices it works. Not that you have to choose another device in the list. Now when you want to add ECMR-250 you need to chose Nexa WMR-252 dimmer in the list? As soon as someone discover this it should be changed because it is a bug?
We are even discussing here about some particular devices based on some proprietary/closed protocols which has been requested by some of our customers.
This is not unique, also Tellstick is doing that and soon you will compete with Tellstick that will have z-wave version of there controller. I am more thinking of other threads that have waited 2 years for answer? Example, Logitech Harmony support? I don’t want the whole summer to pas to get support for blinds?
From you we got the roller shutter motor to support, which is also based proprietary protocol, as the manufacturer didn't care about the interconnectivity of that product. Although there are less than few users of this motor currently in our community, anyway, we expressed our interest to put some effort in possible integration of this protocol into our system.
The advantage of this particular blinds motor is that it is the same as RollerTrol that is quiet big in this segment, and to a good price. I don’t know how many users send their hardware to you, this should be a motivation to add some code? The better the total price of hardware is, the more Zipaboxes you will sell. More money in, is certainly something you will benefit from.
On the other side you are writing here about our slow response, so I don't understand what exactly do you think we should do, and compering to which company we have slow response. Did you ever consider buying some products based on some standardized protocols at the first place? This would certainly speed up the process of integration on your side. Or did you call the manufacturer of that Nexa WT-2 switch and check how they are responsive and willing to integrate other systems?
You should really go threw old threads and answer them publicly about status or plans. Now for me it looks like there is issues that never have bin considered or answered.
Yes I contacted them and they told me this:
Hey,
It never goes at creating product / apps that appeals to everyone, unfortunately.
Our focus with the experience we have since many years is that it should be simple, functional and, above all, user-friendly where there is self-explanatory.
433 Mhz is a very frequent frequency that many uses, however, it can still be encoded in such a way that the manufacturer / supplier can not release on its protocols.
We will make use of a transceiver 433 that "listens" to most of the codes within that band, but each individual code has still an API that we must adapt and build the app for, we will be ready for Nexa 433, Anslit, Provee and some others.
Z-Wave can be extremely sophisticated and fits rarely the masses of users, it's too complicated for Kalle Svensson to understand, to code, etc .. We have scaled down operations in Z-Wave yet done so that the user can combine Nexa 433 , Z-wave receiver / transmitter and Nexa wireless smoke detector at 868 Mhz,
Our app developers belonging to the advanced nature and can everything in iOS, so future adjustments are already documented.
Sincerely
Support
I hope you will understand our effort to integrate as much as possible of these devices in order to support our users. And we would appreciate some patience at least for these few issues which are based solely on pure enthusiasm and willingness to help.
I understand your effort, But app development should go faster and more often! Or at least info about what is going on in the background, there should be something to write about once a week.
Soon Nexa Bridge and Tellsticks version is her, use this time ahead of them to be even better.
A little harsh Jacob, but in some respects well said. To develop a system that can control such a variety of devices is time consuming and expensive. Firstly the Zipabox is a relatively inexpensive controller, with little profit margin. Zipato is not Google, Phillips, or any other large manufacturer. This is why you are others buy it. Try asking Telldus to support Zigbee or Enocean products, or Fibaro to support your 433mhz blind.
You want full integration as soon as you make a call or email, tried a professional installer, not a DIY product. Or spend the $60 on a Zipato Micro module motor controller. It is easy to pick apart an email and dissect the comments, but please go easy. Tellstick do one protocol, Zipato many. To get the products from manufacturers to test is a time consuming and expensive service. Manufacturers do not always respond or even care if their products are supported. Their mind set is, if you want it, you buy it.
While it would be nice to have a product timeline in place, this can only add to more unrest as product integration gets extended due to outside circumstances. Please think about your comments from a business standpoint. Everybody wants their particular product to integrate, but nobody wants to buy a new product to make it work. You don't buy a Toyota Corolla, then go back to Toyota and ask for a Head Up Display, Night Vision, Bose speakers, or Supercharged V10 engine.
Zipato need to make money elsewhere, whether by selling supporting products or subscriptions. We buy the Zipabox because it can support a variety of products. Products they do not earn anything from.
I buy the Zipabox because it is expandable and futureproof. What happens when Thread start to release their products, Zigbee 3.0 is operational, or Apples Homekit has numerous devices available on the market. I'm sure we will all want those products integrated asap too.
Lastly, while 433mhz support is nice, I don't think it is in the best interests of the future. 433mhz is mostly not secure or have two way communication. Why else is Telldus moving to Z-wave support. You are right about more focus should be spent on the app development. This is Zipato's face. The product the end user interacts with the most, and it is lacking.
I see everyone complaining and no one thanking the Zipato team. Their customer support has been second to none thus far. Sure some product integration is slower than other suppliers, but they do not have the range that Zipabox does.
So thank you Zipato for producing an overall great product with good product support. Now hurry up and fix that damn app.
A little harsh Jacob, but in some respects well said. To develop a system that can control such a variety of devices is time consuming and expensive. Firstly the Zipabox is a relatively inexpensive controller, with little profit margin. Zipato is not Google, Phillips, or any other large manufacturer. This is why you are others buy it. Try asking Telldus to support Zigbee or Enocean products, or Fibaro to support your 433mhz blind.
You want full integration as soon as you make a call or email, tried a professional installer, not a DIY product. Or spend the $60 on a Zipato Micro module motor controller. It is easy to pick apart an email and dissect the comments, but please go easy. Tellstick do one protocol, Zipato many. To get the products from manufacturers to test is a time consuming and expensive service. Manufacturers do not always respond or even care if their products are supported. Their mind set is, if you want it, you buy it.
While it would be nice to have a product timeline in place, this can only add to more unrest as product integration gets extended due to outside circumstances. Please think about your comments from a business standpoint. Everybody wants their particular product to integrate, but nobody wants to buy a new product to make it work. You don't buy a Toyota Corolla, then go back to Toyota and ask for a Head Up Display, Night Vision, Bose speakers, or Supercharged V10 engine.
Zipato need to make money elsewhere, whether by selling supporting products or subscriptions. We buy the Zipabox because it can support a variety of products. Products they do not earn anything from.
I buy the Zipabox because it is expandable and futureproof. What happens when Thread start to release their products, Zigbee 3.0 is operational, or Apples Homekit has numerous devices available on the market. I'm sure we will all want those products integrated asap too.
Lastly, while 433mhz support is nice, I don't think it is in the best interests of the future. 433mhz is mostly not secure or have two way communication. Why else is Telldus moving to Z-wave support. You are right about more focus should be spent on the app development. This is Zipato's face. The product the end user interacts with the most, and it is lacking.
I see everyone complaining and no one thanking the Zipato team. Their customer support has been second to none thus far. Sure some product integration is slower than other suppliers, but they do not have the range that Zipabox does.
So thank you Zipato for producing an overall great product with good product support. Now hurry up and fix that damn app.
Hi Adrian!
While I not agre on every point 100% you are right in most of them and I must at lest thank both you and Sebastian for the constructive and fast answer.
But to be fair I was expecting more when it comes to Nexa integration. I thought all there devices vas supported out of the box. I thought I bought a controller that had everything that Tellstick have + zwave. But there was a lot of problems in the beginning, with 433 MHz that I had to change, not working internal module to a external, googling on how to configure a simple Nexa dimmer. Well I like to fix with things but now I only want things to work the way I want.
You can see how long it was sent I posted the post about the, "simple switch" and still no answer. I finally discovered one way of doing it.
But I still don't know how I do the other things. And this should be a basic function right? If the things is not possible than Zipato could say so. For example, if it is not possible to make a dimmer function on Zipabox because of how the signal from the switch is read? I mean press and hold. Others have asked about this. Others have also asked about double tap 2 start dimmer cycle like Nexa, and I have not seen any answer abut that to. If it is not possible then Zipato could say so. Although I believe that it is possible.
Best regards Jacob!
Hi Adrian!
While I not agre on every point 100% you are right in most of them and I must at lest thank both you and Sebastian for the constructive and fast answer.
But to be fair I was expecting more when it comes to Nexa integration. I thought all there devices vas supported out of the box. I thought I bought a controller that had everything that Tellstick have + zwave. But there was a lot of problems in the beginning, with 433 MHz that I had to change, not working internal module to a external, googling on how to configure a simple Nexa dimmer. Well I like to fix with things but now I only want things to work the way I want.
You can see how long it was sent I posted the post about the, "simple switch" and still no answer. I finally discovered one way of doing it.
But I still don't know how I do the other things. And this should be a basic function right? If the things is not possible than Zipato could say so. For example, if it is not possible to make a dimmer function on Zipabox because of how the signal from the switch is read? I mean press and hold. Others have asked about this. Others have also asked about double tap 2 start dimmer cycle like Nexa, and I have not seen any answer abut that to. If it is not possible then Zipato could say so. Although I believe that it is possible.
Best regards Jacob!
Hi Jacob,
I agree it would be nice to have a complete list of supported products and how they work. This would influence many people before they buy. Maybe this will be on the new webpage when it is finished. I like your idea with the switch dimmer function too. Sorry never looked at it before. A good idea, not sure exactly how to use it with the puzzle maker. Have you done this with another controller? I might look into this myself when I get some time. I guess it would involve a wait command when the switch is activated then the resulting actions would determine what state it should go to. A very handy rule. Try reposting the topic but with a better heading. Something simple like "rule for double or triple tap a switch for different settings?" Some of the guys on here are awesome at this thing. Programming is not my strong point.
And keep up the critiquing, how else do we improve in life.
Hi Jacob,
I agree it would be nice to have a complete list of supported products and how they work. This would influence many people before they buy. Maybe this will be on the new webpage when it is finished. I like your idea with the switch dimmer function too. Sorry never looked at it before. A good idea, not sure exactly how to use it with the puzzle maker. Have you done this with another controller? I might look into this myself when I get some time. I guess it would involve a wait command when the switch is activated then the resulting actions would determine what state it should go to. A very handy rule. Try reposting the topic but with a better heading. Something simple like "rule for double or triple tap a switch for different settings?" Some of the guys on here are awesome at this thing. Programming is not my strong point.
And keep up the critiquing, how else do we improve in life.
Replies have been locked on this page!