This object is in archive!
Z-wave device lost
Known
Hi,
I just noted that my Qubino flush dimmer has disappeared from both device manager and the rules. This happened without any changes made to the system. I have rebooted and now also upgraded the firmware but the device is still lost. Any ideas?
Thanks
Ola
The same problem 
No connection
Real-time notifications may not work
Thanks Jimmy,
I guess i can just add it again. But the question remains. How can I trust this sytem to guard my house?
Thanks Jimmy,
I guess i can just add it again. But the question remains. How can I trust this sytem to guard my house?
I have had this problem many times, this same night a device zwave heavy duty of Aeon Labs has disappeared to me. I have it installed 6 months ago and today suddenly it is not. It is very frustrating and creates a lot of mistrust in this system. Again, I have to add it again and go over all the rules where it was included.
I have had this problem many times, this same night a device zwave heavy duty of Aeon Labs has disappeared to me. I have it installed 6 months ago and today suddenly it is not. It is very frustrating and creates a lot of mistrust in this system. Again, I have to add it again and go over all the rules where it was included.
I have had the same issue a week ago, one of my qubino's (flush 1 relay) vanished from device manager I opened a ticket regarding power consumption not being reported in my qubino flush shutter and zipato said they would work on it. I assumed this "disappearance" had to do with them working on my box and maybe modifying descriptors, I had to unwire the qubino, add it again, wire it again to the shitch and fix all rules, Zipato support's answer was very dissapointing;
"The most important thing is that now everything is as before. We will try to explore your issue."
This needs to STOP!! I thought this was more of a fat finger on zipato support, but this looks more like a glitch in the processors, Zipato must give us a professional answer, it is a pain to add qubinos again to the system and rebuild the rules, not mentioning the grief that this causes, the automation that is supposed to help our life easier is busting our chops!!
I have had the same issue a week ago, one of my qubino's (flush 1 relay) vanished from device manager I opened a ticket regarding power consumption not being reported in my qubino flush shutter and zipato said they would work on it. I assumed this "disappearance" had to do with them working on my box and maybe modifying descriptors, I had to unwire the qubino, add it again, wire it again to the shitch and fix all rules, Zipato support's answer was very dissapointing;
"The most important thing is that now everything is as before. We will try to explore your issue."
This needs to STOP!! I thought this was more of a fat finger on zipato support, but this looks more like a glitch in the processors, Zipato must give us a professional answer, it is a pain to add qubinos again to the system and rebuild the rules, not mentioning the grief that this causes, the automation that is supposed to help our life easier is busting our chops!!
Just to share the pain. Same happened to me with a qubino flush shutter module. After installation in the wall it's gone. Not even as off-line - but really gone.
Zipato always offers new bad suprises and just when you wan't to give up everything it works for a short time to keep you on the leash.
For what I've spent just in working hours I could operate all houses and flats of a reasonable city for the next 100 years :-(
Just to share the pain. Same happened to me with a qubino flush shutter module. After installation in the wall it's gone. Not even as off-line - but really gone.
Zipato always offers new bad suprises and just when you wan't to give up everything it works for a short time to keep you on the leash.
For what I've spent just in working hours I could operate all houses and flats of a reasonable city for the next 100 years :-(
Today it happened again, this time with one of my Zipato RGBW bulbs. I guess this is due Zipato platform changes, not qubino devices... Zipato is dropping the ball again without any warning.
Today it happened again, this time with one of my Zipato RGBW bulbs. I guess this is due Zipato platform changes, not qubino devices... Zipato is dropping the ball again without any warning.
Support says issue is under investigation, developers don't know the reason why. Also they say they think this might be a zwave issue since other manufacturers are experiencing the same problem, sounds hard to believe but that is the response so far.
Support says issue is under investigation, developers don't know the reason why. Also they say they think this might be a zwave issue since other manufacturers are experiencing the same problem, sounds hard to believe but that is the response so far.
I just had one of my Aeon Micro Switch G2 v2 in wall switch automatically removed from the z-wave network.
All the related rules became invalid. I opened a ticket few minutes ago, let's see what zipato say.
Also, from yesterday i had sync issue but without having any error: modify a rule, save, sync, system reply that sync was good. Reload the dashboard and the rule is the old one. Lot of time wasted.
I dont think is related, but when I notice that my device desappear i was using imperihome making a reload of the devices.
Do you use it also? I dont think this is the issue, but just to have all the possible clues.
I just had one of my Aeon Micro Switch G2 v2 in wall switch automatically removed from the z-wave network.
All the related rules became invalid. I opened a ticket few minutes ago, let's see what zipato say.
Also, from yesterday i had sync issue but without having any error: modify a rule, save, sync, system reply that sync was good. Reload the dashboard and the rule is the old one. Lot of time wasted.
I dont think is related, but when I notice that my device desappear i was using imperihome making a reload of the devices.
Do you use it also? I dont think this is the issue, but just to have all the possible clues.
I reported the same issue several months ago. This happened to me only with Qubino modules and not any other, so I assumed it's a qubino bug.
In most of cases the reason for this device loss is that they enter an arbitrary Add/Remove state without doing any action on them. I don't know if there is any "help" in it from zipabox controller. But when they are in this add/remove state, any device reset procedure (which is done when you click "Add new device" -> "Z-wave") can affect them.
So basically you loose devices when they enter an arbitrary add/remove state and you try add new devices.
Only 2-3 times on 15-20 my device was lost in other circumstances that Add new device procedure.
And I've found out a workaround for this. From z-wave network properties I click "Add device" before I add new device from Device manager. If this procedure times out, then no of my devices is in arbitrary add/remove state. If it is, then I see message like "Device with NodeId = XX already added" and I know that I need to make a circuit break on that device to get it out from add/remove state. Without a circuit break such device would be affected by add/remove procedure until removed from network.
So to avoid loosing Qubino modules:
1) go to Z-wave network properties -> Add node and wait for timeout
2) If you see "Device with NodeId = XX already added", then circuit break this device and repeat procedure
3) If you have timeout, do normal Add new device -> Z-wave device procedure using your new device you want to add to network
I reported the same issue several months ago. This happened to me only with Qubino modules and not any other, so I assumed it's a qubino bug.
In most of cases the reason for this device loss is that they enter an arbitrary Add/Remove state without doing any action on them. I don't know if there is any "help" in it from zipabox controller. But when they are in this add/remove state, any device reset procedure (which is done when you click "Add new device" -> "Z-wave") can affect them.
So basically you loose devices when they enter an arbitrary add/remove state and you try add new devices.
Only 2-3 times on 15-20 my device was lost in other circumstances that Add new device procedure.
And I've found out a workaround for this. From z-wave network properties I click "Add device" before I add new device from Device manager. If this procedure times out, then no of my devices is in arbitrary add/remove state. If it is, then I see message like "Device with NodeId = XX already added" and I know that I need to make a circuit break on that device to get it out from add/remove state. Without a circuit break such device would be affected by add/remove procedure until removed from network.
So to avoid loosing Qubino modules:
1) go to Z-wave network properties -> Add node and wait for timeout
2) If you see "Device with NodeId = XX already added", then circuit break this device and repeat procedure
3) If you have timeout, do normal Add new device -> Z-wave device procedure using your new device you want to add to network
Thank you Thomas, this is very good to know. I added a new device (a zwave lamp) a couple of days before the switch lost, so can be possible that it was the moment when the switch was removed but I notice it just later.
Thank you very much for this workaround. I will try to follow your instruction before adding the next device.
Thank you Thomas, this is very good to know. I added a new device (a zwave lamp) a couple of days before the switch lost, so can be possible that it was the moment when the switch was removed but I notice it just later.
Thank you very much for this workaround. I will try to follow your instruction before adding the next device.
I don't think this is related to the adding method of devices, also not specific to Qubino, I got a Zipato RGBW bulb removed from the network, and on both times I experienced (first a qubino module, then the Zipato bulb) I wasn't working with the controller. According to Zipato team this issue is under investigation and they mentioned this might be happening because another controller had an "impact" on the network, which I don't know how that can happen, I indeed have to zipatiles at home plus the zipabox with all devices, but right now the zipatiles act only as dumb tablets logging into zipabox.
I don't think this is related to the adding method of devices, also not specific to Qubino, I got a Zipato RGBW bulb removed from the network, and on both times I experienced (first a qubino module, then the Zipato bulb) I wasn't working with the controller. According to Zipato team this issue is under investigation and they mentioned this might be happening because another controller had an "impact" on the network, which I don't know how that can happen, I indeed have to zipatiles at home plus the zipabox with all devices, but right now the zipatiles act only as dumb tablets logging into zipabox.
Hi Alberto,
I dont know, but for sure I have just 1 controller (a zipabox). Not any others (nor zipatile or others). So I dont think this can be the issue (unless the controller is maybe one of my neighbor, but I really dubt that. As far as I know there are very few people that use z-wave actually, and have one near my home should be at least very rare).
What I know is that in the last days, due to the vacancy, I play a lot with zipato. First to solve an issue where the network heal fail for all the devices. Then with a rule that fail to syncronize without giving any error, and now the device lost. I know there is same server issue, but I dont know how much my problems are related to them or to a poor zwave protocol (I really hope in an issue with the zipato server, otherwise it means that the whole zwave "thing" is bugged and we have to move to a different solution).
Hi Alberto,
I dont know, but for sure I have just 1 controller (a zipabox). Not any others (nor zipatile or others). So I dont think this can be the issue (unless the controller is maybe one of my neighbor, but I really dubt that. As far as I know there are very few people that use z-wave actually, and have one near my home should be at least very rare).
What I know is that in the last days, due to the vacancy, I play a lot with zipato. First to solve an issue where the network heal fail for all the devices. Then with a rule that fail to syncronize without giving any error, and now the device lost. I know there is same server issue, but I dont know how much my problems are related to them or to a poor zwave protocol (I really hope in an issue with the zipato server, otherwise it means that the whole zwave "thing" is bugged and we have to move to a different solution).
Today again.
Wall Switch gone in Devicemanager and Rules.
Today again.
Wall Switch gone in Devicemanager and Rules.
@Alberto, Zipato support told me the same thing about logging over half year ago. They found nothing. Since that time some devices were gone. In vast majority of cases during inclusion of other devices.
Arbitrary device readiness for inclusion/exclusion is only fact I have that influences device removal from network. Most of my devices are Qubinos, so I can't tell if other brands act this way.
@Alberto, Zipato support told me the same thing about logging over half year ago. They found nothing. Since that time some devices were gone. In vast majority of cases during inclusion of other devices.
Arbitrary device readiness for inclusion/exclusion is only fact I have that influences device removal from network. Most of my devices are Qubinos, so I can't tell if other brands act this way.
Guys,
I think that the assumption of Thomas could be correct. Reading from the manual of my AEON switch it say:
"While the Micro Smart Energy Switch G2 is powered in a 3-wire system,
the external switch/button can be toggled to initiate pairing into the
Z-Wave network. or the internal button can be pushed to initiate pairing
into the Z-Wave network, if Micro Smart Energy Switch G2 was not put
into in-wall box."
Basically, switching the light 3 times (I dont know how fast) put the switch into the inclusion/exclusion mode. Once in exclusion mode, it is sufficient to click on "add device" on zipabox to remove the switch. So It could be really easy to get mistake (like a rule that switch the light 2 times followed by a manual switch for example).
I dont know about others device, but if you can confirm that all the lost device could be put in the inclusion/exclusion mode WITHOUT pressing manually any button, that could be the root cause.
If we can confirm this, maybe zipato can introduce a middle step into the inclusion process: after founding a device, it should ask to the user if the user want REALLY remove the founded device. Actually the process is fully automatically (when you start the inclusion, the first step is to exclude a founded device). I think Zipato must prompt the user before automatically remove what found.
Guys,
I think that the assumption of Thomas could be correct. Reading from the manual of my AEON switch it say:
"While the Micro Smart Energy Switch G2 is powered in a 3-wire system,
the external switch/button can be toggled to initiate pairing into the
Z-Wave network. or the internal button can be pushed to initiate pairing
into the Z-Wave network, if Micro Smart Energy Switch G2 was not put
into in-wall box."
Basically, switching the light 3 times (I dont know how fast) put the switch into the inclusion/exclusion mode. Once in exclusion mode, it is sufficient to click on "add device" on zipabox to remove the switch. So It could be really easy to get mistake (like a rule that switch the light 2 times followed by a manual switch for example).
I dont know about others device, but if you can confirm that all the lost device could be put in the inclusion/exclusion mode WITHOUT pressing manually any button, that could be the root cause.
If we can confirm this, maybe zipato can introduce a middle step into the inclusion process: after founding a device, it should ask to the user if the user want REALLY remove the founded device. Actually the process is fully automatically (when you start the inclusion, the first step is to exclude a founded device). I think Zipato must prompt the user before automatically remove what found.
No, this does not make sense. No way everyone is so "unlucky"that while in inclusion process someone would accidentally do an exclusion command. No way. This is something else.
Another reason why the backup feature is urging...
No, this does not make sense. No way everyone is so "unlucky"that while in inclusion process someone would accidentally do an exclusion command. No way. This is something else.
Another reason why the backup feature is urging...
Hi,
have you been doing any network healing before noticing device getting lost ?
Hi,
have you been doing any network healing before noticing device getting lost ?
@Attila.
I think that the add device command in voluntary. What is not wanted is the device that go "alone" into the inclusion/exclusion mode. Of course this is just a guess. I have added a device (a lamp) just 2 days before i notice the lost one (a switch). Maybe is not related.
@Chistian
yes I was playing with the network heal a lot during the last week. But I'm pretty sure that after the last one the swith was still there (I checked the nieghbor section of all my devices to see if they were updated, and they do.
@Attila.
I think that the add device command in voluntary. What is not wanted is the device that go "alone" into the inclusion/exclusion mode. Of course this is just a guess. I have added a device (a lamp) just 2 days before i notice the lost one (a switch). Maybe is not related.
@Chistian
yes I was playing with the network heal a lot during the last week. But I'm pretty sure that after the last one the swith was still there (I checked the nieghbor section of all my devices to see if they were updated, and they do.
You can't put a Z-Wave device in inclusion/exclusion mode without user interaction.
A middle step wouldn't help here, once you put a controller in exclusion mode and if a Z-Wave device is in range and in exclusion mode, that device will be removed from its current network. We can't change this since this is done automatically by the Z-Wave protocol.
You can't put a Z-Wave device in inclusion/exclusion mode without user interaction.
A middle step wouldn't help here, once you put a controller in exclusion mode and if a Z-Wave device is in range and in exclusion mode, that device will be removed from its current network. We can't change this since this is done automatically by the Z-Wave protocol.
Marko, all those people including me just wrote that their devices were put into inclusion/exclusion mode without interaction. Moreover I definitely say, that when Qubino devices are in this mode they stay in it indefinitely long. So *every time* I enter Add device mode in z-wave protocol properties tab *the same device* is reported as "already added" and I don't even know what device it is because only it's ID is displayed. I have to do a circuit break to get such device out of that state. And each time it can be different device - there is no rule in that matter.
So please - don't write theory where people discuss about practical problems and their causes.
Marko, all those people including me just wrote that their devices were put into inclusion/exclusion mode without interaction. Moreover I definitely say, that when Qubino devices are in this mode they stay in it indefinitely long. So *every time* I enter Add device mode in z-wave protocol properties tab *the same device* is reported as "already added" and I don't even know what device it is because only it's ID is displayed. I have to do a circuit break to get such device out of that state. And each time it can be different device - there is no rule in that matter.
So please - don't write theory where people discuss about practical problems and their causes.
OMG It just happen again to me :(
just woke up and discover that one of my two Fibaro motion sensor disappear. Lost. Vanish. In the rules is reconginzed as Unknow (and the rules marked as NOT VALID) and in the Zwave devices list is just missing.
How can **** be possible this? That's the second time in two months. If this system is also sold as security alarm (And it is) how can be accettable a bug like this? Regardless all the time that I have to spend to reinclude the sensor and do again the rules that actually are NOT VALID, but what happens if something bad happens and the alarm is not working because one (or more then one) sensor are just removed by themself? I think you should be considered as responsible due the fact that this bug was reported ages ago and not yet fixed. I think a bug like this should prevent you to sell the product as a security system. How can be this considered *secure* by Zipato? I mean, at least having a backup system in place or any other workaround that in case like this can "on fly" restore the system should be the priority number one. Or at least enable the log file on the operations. do you think is normal that is impossible to understand why and when this happens? how can you fix this without a log?
ps: Just to be extremly clear: I was sleeping, so no action by me on the controller or on the device. The device is battery powered (while the previous disappear for me was a main powered switch). Last time I used the device was 23pm last night, and it worked (it turn automatically the light in one room on, and it worked). This night I woke up at 2 or 3 am to drink and I notice all the light in my house on. So the rules based on one variable that check the motion was not working. this morning i checked and i found the device is missing.
@Zipato: I love you and i love your system, but this is really unacceptable.
OMG It just happen again to me :(
just woke up and discover that one of my two Fibaro motion sensor disappear. Lost. Vanish. In the rules is reconginzed as Unknow (and the rules marked as NOT VALID) and in the Zwave devices list is just missing.
How can **** be possible this? That's the second time in two months. If this system is also sold as security alarm (And it is) how can be accettable a bug like this? Regardless all the time that I have to spend to reinclude the sensor and do again the rules that actually are NOT VALID, but what happens if something bad happens and the alarm is not working because one (or more then one) sensor are just removed by themself? I think you should be considered as responsible due the fact that this bug was reported ages ago and not yet fixed. I think a bug like this should prevent you to sell the product as a security system. How can be this considered *secure* by Zipato? I mean, at least having a backup system in place or any other workaround that in case like this can "on fly" restore the system should be the priority number one. Or at least enable the log file on the operations. do you think is normal that is impossible to understand why and when this happens? how can you fix this without a log?
ps: Just to be extremly clear: I was sleeping, so no action by me on the controller or on the device. The device is battery powered (while the previous disappear for me was a main powered switch). Last time I used the device was 23pm last night, and it worked (it turn automatically the light in one room on, and it worked). This night I woke up at 2 or 3 am to drink and I notice all the light in my house on. So the rules based on one variable that check the motion was not working. this morning i checked and i found the device is missing.
@Zipato: I love you and i love your system, but this is really unacceptable.
I also lost one qubino device from network during night yesterday and it could have been around 23:00-0:00 CET. As in @m4dt3o case, no action was taken from my side when it happened.
I reported to Zipato support a case over half year ago and they've done nothing since that time. This is one of most frustrating bug in their system, as it requires redefining all rules, groups and scenes that involved missing device. Please fix it!
I also lost one qubino device from network during night yesterday and it could have been around 23:00-0:00 CET. As in @m4dt3o case, no action was taken from my side when it happened.
I reported to Zipato support a case over half year ago and they've done nothing since that time. This is one of most frustrating bug in their system, as it requires redefining all rules, groups and scenes that involved missing device. Please fix it!
Same happened to me yesterday witho two domitech zbulb
Same happened to me yesterday witho two domitech zbulb
This is worrying, I have yet to experience this and hope I never will. especially for a client.
Can you rejoin the device? the device itself is not faulty is it? has anyone raised a ticket and had a response?
This is worrying, I have yet to experience this and hope I never will. especially for a client.
Can you rejoin the device? the device itself is not faulty is it? has anyone raised a ticket and had a response?
Backup should solve this problem.
Backup should solve this problem.
Yesterday my next device disappeared from zipabox device list. I start to think, that it's a bug in their code and that device is still in the network but it's not displayed in devices registry. That device was purely remotely controlled and there was no button connected to input, so there was no possibility to exclude that relay from z-wave network. And very irritating thing is that they don't look for such bugs in their software, but try to explain to people that they probably removed devices accidentally :/
Yesterday my next device disappeared from zipabox device list. I start to think, that it's a bug in their code and that device is still in the network but it's not displayed in devices registry. That device was purely remotely controlled and there was no button connected to input, so there was no possibility to exclude that relay from z-wave network. And very irritating thing is that they don't look for such bugs in their software, but try to explain to people that they probably removed devices accidentally :/
I drilled down the problem and found out, that devices that were lost from z-wave network are still visible as neighbor nodes in "advanced tab" of their neighbors. Instead of device name there is GUID value of the node. In my opinion those devices were not excluded from z-wave network but simply deleted from device list by a bug in zipato cloud software. After you notice a disappeared device in your network check other nodes for GUIDs in neighbor list. I use API method getDevices for frequent (once a week) device listening and save it to file. It helps in such situations to display differences in device list using a diff tool, like https://www.diffchecker.com/ I paste current output of getDevices and former version and see differences. It can also tell you what lost device stands for particular GUID in neighbor list.
I drilled down the problem and found out, that devices that were lost from z-wave network are still visible as neighbor nodes in "advanced tab" of their neighbors. Instead of device name there is GUID value of the node. In my opinion those devices were not excluded from z-wave network but simply deleted from device list by a bug in zipato cloud software. After you notice a disappeared device in your network check other nodes for GUIDs in neighbor list. I use API method getDevices for frequent (once a week) device listening and save it to file. It helps in such situations to display differences in device list using a diff tool, like https://www.diffchecker.com/ I paste current output of getDevices and former version and see differences. It can also tell you what lost device stands for particular GUID in neighbor list.
Yesterday after upgrade to 1.2.22 six (SIX! 6) devices dissappeared from z-wave network, including two battery powered devices (sensors) and four wired. I'm not sure if it was immediately after upgrade, as I didn't check rules if they became invalid, but problems occurred when evening (sunset) rules haven't started. Battery powered devices report normally to the box as they signal no problem with connectivity or range. The problem is that box doesn't have them in registry.
It's hard to explain how frustrating is when one needs to reinclude devices and fix many broken scenes and after few weeks, up to two months such incident happens again.
As there is no updates to support tickets related to this critical failure, I ask Zipato on this forum - what do you do to fix this fundamental flaw of your software?!
Yesterday after upgrade to 1.2.22 six (SIX! 6) devices dissappeared from z-wave network, including two battery powered devices (sensors) and four wired. I'm not sure if it was immediately after upgrade, as I didn't check rules if they became invalid, but problems occurred when evening (sunset) rules haven't started. Battery powered devices report normally to the box as they signal no problem with connectivity or range. The problem is that box doesn't have them in registry.
It's hard to explain how frustrating is when one needs to reinclude devices and fix many broken scenes and after few weeks, up to two months such incident happens again.
As there is no updates to support tickets related to this critical failure, I ask Zipato on this forum - what do you do to fix this fundamental flaw of your software?!
My door sensors also stopped working today. I thought it was low battery, but I switched it and it did not work. I had to delete and re-add to the Zipabox. I noticed a lot of slowness in the responses and status update (Open / Closed). The rule involved in these sensors also stopped working.
My door sensors also stopped working today. I thought it was low battery, but I switched it and it did not work. I had to delete and re-add to the Zipabox. I noticed a lot of slowness in the responses and status update (Open / Closed). The rule involved in these sensors also stopped working.
Alessandro,
Your issue seems to be a different issue, seems to be related to overall performance rather than z-wave devices dissapearing from the routing map of zipato controllers. Try to update to latest official firmware and performing a complete zwave network heal.
Alessandro,
Your issue seems to be a different issue, seems to be related to overall performance rather than z-wave devices dissapearing from the routing map of zipato controllers. Try to update to latest official firmware and performing a complete zwave network heal.
Yesterday happened again. A device disappeared from configuration, device manager and device browser. Rules that uses it became invalid.
How is it possible?
And, how to fix it???
Yesterday happened again. A device disappeared from configuration, device manager and device browser. Rules that uses it became invalid.
How is it possible?
And, how to fix it???
I suggest to open a ticket with support (support.zipato.com)
Happened to me in the past with Aeon Range Extender.
I suggest to open a ticket with support (support.zipato.com)
Happened to me in the past with Aeon Range Extender.
Thanks Simone, I've opened a ticket yesterday but still no answer ...
When happened to you the support was able to restore the device or you ended up in manually re-adding the device?
Thanks Simone, I've opened a ticket yesterday but still no answer ...
When happened to you the support was able to restore the device or you ended up in manually re-adding the device?
happening again and again ... hope that Zipato shall explain us once how to prevent this
happening again and again ... hope that Zipato shall explain us once how to prevent this
Again today - added new actors to the z-wave network and again other actors got dropped for no apparent reason. It seems the issue still persists. So annoying!
rules are broken and adding the actor back in the network is always a pain as it need to located / disassembled from the installation and then rejoined. Once that is done you can start fixing your rules.
worst part of it is, the rules are now broken so you never know if the automation is still working or the whole execution of the rules seize to function.
To track the actors i started labeling them all with an identification code which is stored in the website (name). When 1 is lost i can find it because there is a gap in the numbering, dig up the blue prints of the electrical system and find the damn thing.
@Support; When is this getting fixed!
Again today - added new actors to the z-wave network and again other actors got dropped for no apparent reason. It seems the issue still persists. So annoying!
rules are broken and adding the actor back in the network is always a pain as it need to located / disassembled from the installation and then rejoined. Once that is done you can start fixing your rules.
worst part of it is, the rules are now broken so you never know if the automation is still working or the whole execution of the rules seize to function.
To track the actors i started labeling them all with an identification code which is stored in the website (name). When 1 is lost i can find it because there is a gap in the numbering, dig up the blue prints of the electrical system and find the damn thing.
@Support; When is this getting fixed!
Hi
I had this problem also today with firmware 1.3.10. After that I've updated to 1.3.13 as Mislav from Zipato mentioned in another thread that with firmware 1.3.13 this problem has been fixed! I hope so....
Thanks
Beat
Hi
I had this problem also today with firmware 1.3.10. After that I've updated to 1.3.13 as Mislav from Zipato mentioned in another thread that with firmware 1.3.13 this problem has been fixed! I hope so....
Thanks
Beat
They declared that this issue was resolved in previous major update, and initially I thought so. But after 2-3 months devices started to dissappear again, when I added more devices to the box. For me it's the #1 issue in Zipato, but I can imagine that people suffer from this issue when they have dozens of devices (like ~150 in my case).
So when you add 4-5 devices to zipato and no device is silently removed from the system is the time for celebration :)
They declared that this issue was resolved in previous major update, and initially I thought so. But after 2-3 months devices started to dissappear again, when I added more devices to the box. For me it's the #1 issue in Zipato, but I can imagine that people suffer from this issue when they have dozens of devices (like ~150 in my case).
So when you add 4-5 devices to zipato and no device is silently removed from the system is the time for celebration :)
Hi Tomasz
Yes I agree it would be #1 issue to me too! It did happen last night the first time to me and took me down from 107 to 103 devices. Then I did an upgrade to firmware 1.3.13 and added 4 devices. After that I check every single rule if another device is missing. But everything is there.
See the comment from Mislav in the update thread about version 1.3.13:
***************************************************************
Hi Beat,
This is an oversight from our team which happened since we were in a hurry to resolve the following issues with the 1.3.13 firmware:
Fibaro devices compatibility - some Fibaro devices had issues with inclusion and configuration settings
Z-Wave devices missing - in some special cases devices would get deleted by the controller (deemed malfunctioning and unavailable)
Virtual Thermostat - fixed issue with thermostat not turning on in some instances
BR,
Mislav
***************************************************************
Did it happen to you on firmware 1.3.13? If yes then you should report to support immediately (I know grrrr)...
Thanks
Beat
Hi Tomasz
Yes I agree it would be #1 issue to me too! It did happen last night the first time to me and took me down from 107 to 103 devices. Then I did an upgrade to firmware 1.3.13 and added 4 devices. After that I check every single rule if another device is missing. But everything is there.
See the comment from Mislav in the update thread about version 1.3.13:
***************************************************************
Hi Beat,
This is an oversight from our team which happened since we were in a hurry to resolve the following issues with the 1.3.13 firmware:
Fibaro devices compatibility - some Fibaro devices had issues with inclusion and configuration settings
Z-Wave devices missing - in some special cases devices would get deleted by the controller (deemed malfunctioning and unavailable)
Virtual Thermostat - fixed issue with thermostat not turning on in some instances
BR,
Mislav
***************************************************************
Did it happen to you on firmware 1.3.13? If yes then you should report to support immediately (I know grrrr)...
Thanks
Beat
2 years spent but the problem the same. Qubino dimmer 0-10 lost Node ID absolutly unpredictable. All data were sent to manufacturer- no ractiion more 2 months. My vision is following be careful with products from GOAP. Qubino must be in black list until recovery lost of Node ID problem.
2 years spent but the problem the same. Qubino dimmer 0-10 lost Node ID absolutly unpredictable. All data were sent to manufacturer- no ractiion more 2 months. My vision is following be careful with products from GOAP. Qubino must be in black list until recovery lost of Node ID problem.
Replies have been locked on this page!