Posts: 951
Threads: 111
Joined: Jan 2008
I am starting to play around with the room configuration. For the security section I have an ELK M1 with driver 2.21 (Network v2).
In the client side driver It shows the lights, motion sensors and counters. However it does not show the zones. We don't have to load all of them individually do we? I know that previously it imported all that info. Does it not do that now?
George M
Thanks
George M
Posts: 40,483
Threads: 491
Joined: Aug 2002
The official driver never has supported importing the configuration from the Elk itself. There is one based on the old V1 driver that someone else took and expanded on that did it, but it's not been ported to the official driver yet. So I would assume that the other stuff was already there from a previous installation of the driver and it picked that up? That's the only way I can think of that the V2 driver would have initially got it, assuming you used the same moniker for the V2 driver as you did for that other one. There may have been something different in the zone info in that modified driver that made the official one unable to pick up the old configuration for those or something, so it only got the stuff it could understand. It probably just failed when it hit the zones, but they are the last thing done, so it managed to load up the other stuff I guess.
Dean Roddey
Explorans limites defectum
Posts: 951
Threads: 111
Joined: Jan 2008
(12-28-2016, 05:53 PM)Dean Roddey Wrote: The official driver never has supported importing the configuration from the Elk itself. There is one based on the old V1 driver that someone else took and expanded on that did it, but it's not been ported to the official driver yet. So I would assume that the other stuff was already there from a previous installation of the driver and it picked that up? That's the only way I can think of that the V2 driver would have initially got it, assuming you used the same moniker for the V2 driver as you did for that other one. There may have been something different in the zone info in that modified driver that made the official one unable to pick up the old configuration for those or something, so it only got the stuff it could understand. It probably just failed when it hit the zones, but they are the last thing done, so it managed to load up the other stuff I guess.
So do we have to add each zone individually?
Thanks
George M
Posts: 40,483
Threads: 491
Joined: Aug 2002
12-28-2016, 06:53 PM
(This post was last modified: 12-28-2016, 06:54 PM by Dean Roddey.)
Yeh, you would need to do that. The difference in the format is probably that V2 drivers allow you to indicate for each type of zone whether it should send out standard notifications or not, so as to avoid lots of triggers being sent for zones you don't care to react to in any triggered events.
I had hoped to port that configuration import functionality over to the new V2 driver for 5.0. But 5.0 turned into such a massive life sucker that there wasn't time to do it.
Start out with a few zones and make sure you have things working the way you want them to before you commit to the whole thing.
Dean Roddey
Explorans limites defectum
Posts: 3
Threads: 0
Joined: Apr 2010
Is it possible to import zone info (etc.) from a text file or something along those lines?
Posts: 40,483
Threads: 491
Joined: Aug 2002
No, not currently. I will get the auto import thing done as soon as I can.
Dean Roddey
Explorans limites defectum
Posts: 951
Threads: 111
Joined: Jan 2008
Putting them in manually was not as painful as I thought it would be.
Thanks
George M
Posts: 40,483
Threads: 491
Joined: Aug 2002
You would also still want to go through them and indicate which of them you want to send out triggers, since it's not always the case that all of them should and it's a lot of potential overhead if you have, say, a good number of motion sensors, which are constantly being tripped and sending out triggers that aren't being used.
Dean Roddey
Explorans limites defectum