New Topic

Zipato support center Topic Question Uncategorized

This object is in archive!

exchanging module(s)

Frank Weijnen shared this question ago

Need Answer

Hi,

I have a zipabox on firmware 1.0.19 and it's working great.

At the moment I have one module that needs to be exchanged for a new one because it triggers motions even when i am not at home (no, I have no pets).

When I delete the module than I have broken puzzle pieces in my rule and I need to find them and replace them with the new module.

Is there a way to "exchange" or "swirtch" that module for a new one?

Thanks,

Frank.

The same question

Replies (2)

Alberto Macias ●

Frank,

Not that I know of, you have to change the puzzles manually. Although I would try to name the endpoints exactly the same, don't know if that would work. Just for curiosity, the "broken module" you are talking about, is a Fibaro Motion sensor? I have had times where those detect motion but I got arround it with the sensitivity configuration and grouping them in the security alarm. You might be able to "tweak it".

Reply URL

Frank Weijnen ●

Hi Alberto,

Yes it is a Fibaro motions sensor. I have several of them and this is the second one that "malfunctions".

I also thought about the sensitivity but I am happy with the sensitivity and I still have warranty so I will exchange it.

I think it would be a great idea when Zipato added the option to exchange one module with another one. So like:

- Add the new module with whatever name.

- Select the module you need to exchange.

- Instead of pressing delete you press exchange or swapp button you then get a list of modules that are the same and select the one you want.

Sounds easy enough ;-)

Frank.

URL

Alberto Macias ●

Yes it is a very good idea. Hey, if I may ask, is this triggering your home security system? after having this issue a few times I read the manual completely and I read a note where it says that air flows sometimes can be detected as motion. I was happy with the sensitivity so what I did is to configure the zones within the security alarm as "Group 1" which is basically all my motion sensors so, if only one sensor detects motion it won't trigger the alarm. If more than one detect motion within a configurable window of time, then the alarm is triggered. If that is your case too you might want to give it a shot.

URL

Frank Weijnen ●

At the moment I am using the motion sensors mainly to automate my lighting ( auto off when I am leaving a room and stuff like that). I have setup a alarm system and played arround with it to see how it works. Initially it looked great until I got multiple messages saying "alarm triggered" so I gave up for the moment.

But what you say is interesting about grouping, so I could have one group "down stairs" and a second one "upstairs". Unfortunately I could not find a good manual explaining how everything works so I have no idea how to "group".

URL

Alberto Macias ●

I agree with you with the fact that we are lacking of manuals. Nevertheless I have been doing a lot of learning from "trying" which I don't mind sharing.

If you go to the configuration of the zones in your security alarm (little gear icon on the right of the name of the zone), inside the configuration menu you can see the "CROSS ZONE GROUP" and "CROSS ZONING TIME" if you click in the little "i" icon you will get a brief description of what are this basically;

CROSS ZONE GROUP - This is the group you want that particular zone (sensor), as you stated, group 1 can be your "upstairs" group 2 can be "downstairs" (no, you cannot change the name of the groups).

CROSS ZONING TIME - This is the time you want that passes between one sensor "Tripping" and the second sensor "tripping" creating a security alarm TRIP. I.E. lets say you set this time for sensor "A" and "B", sensor A detects motion and this timer starts counting, if at second 15 sensor B detects motion then the alarm gets tripped. In the other hand if sensor B gets tripped after second 31, then the alarm does not get tripped but another 30 second timer starts timing for another motion. I hope I'm being clear. Regards.

Files:

URL

Frank Weijnen ●

Thanks for the explanation. This is useful feature. My holiday starts next week so plenty of time to test this.

Do you use a squawker with the alarm and if so what type / module?

URL

Alberto Macias ●

Well, at the beginning I was using my Zipato Indoor Siren but it's a bit too loud for the baby sometimes so I removed the siren and created a couple rules. First I have a virtual sensor that is active during the day and inactive during the night, using schedulers with astro function. Then using this virtual sensor, if it's night time then I trigger my RGBW controllers to green for 8 seconds if the alarm has been disarmed or red if it has been armed, during day I make the siren beep once or twice accordingly. I you are interested on these rules let me know and will share.

URL

Adrian Van Der Heijden ●

a way to replace a device for the same device would be ideal. but it would have to be the exact same device. You can replace a node, but that only replaces the devices ID node number, not the actual endpoints. It does not swap uuid's over. So unfortunately all rules need to be fixed. And be sure to fix ALL rules, as invalid rules are triggering reboots and problems with controllers.

Reply URL

Frank Weijnen ●

Well that's true and if you exchange the device with a newer version, who knows what happens.

What I would settle with is the option to "ask" a module in what rules it is used. Maybe by adding a "lookup glass" next to the bin and setting icon in the module manager. Pressing that icon shows you a list of all rules it is used in and also how many times.

One should also be able to copy that list to the clipboard in case you delete the module and forgot in which rules it was used ;-)

So zipato, please add.

URL