Domoticz

What platform and why are you migrating?

Clemen wrote: ↑Friday 26 January 2018 10:42 What platform and why are you migrating?

Hi @Clemen!

With respect for everyone working hard to make Domoticz a great software, I would prefer not to use this forum to market other HA software. I hope you understand. Thanks!

BakSeeDaa wrote: ↑Friday 26 January 2018 9:22 *************** IMPORTANT NOTE ***************                            `
                                                                                             
This script will be retired. I'm migrating away from Domoticz to another automation
solution. It requires some effort to maintain it and I won't have the time to do it in the future.

Too bad, you had made some great scripts for us. You will be missed

BakSeeDaa wrote: ↑Friday 26 January 2018 16:07

Clemen wrote: ↑Friday 26 January 2018 10:42 What platform and why are you migrating?

Hi @Clemen!

With respect for everyone working hard to make Domoticz a great software, I would prefer not to use this forum to market other HA software. I hope you understand. Thanks!

That makes me curious too. What are you migrating to? I don't see why mentioning the name would be a problem. It never hurts to know alternatives, plus perhaps domoticz developers might want to add features that might be missing too

Hello!
Someone have a copy of this?
the repository is deleted...

damn, I hope that somebody forked it. because it was a great guide!
I have the files of the script but not the his wiki and other...

I have cloned a old one (only files)

but find out that the author continued his work on another platform:
https://github.com/OH-Jython-Scripters/ideAlarm/wiki this is not for domoticz but I think a lot of comments and the way it work is still useable.
I asked the author for a copy of his old work..

https://github.com/xchwarze/ideAlarm

TODO:
rewrite texts/wiki to Markdown
recover README.md, Arming and disarming wiki and API Script Examples wiki

If the author doesn't have it anymore... i still have a copy with all the wiki info
Most info is also available in search engine caches.
I just don't have the time to fully take over the ideAlarm but i still want to join if someone take over.

Bit of a weird move to completely delete the repository like that. Why not just keep it up, at least for a white, but indicate it's no longer being maintained? Happens all the time.

Anyway: let's declare one as the primary and maybe fork from that one if you want a copy, to prevent all sorts of clones to pop up and confuse people. I have one little fix I'd like to propose which I needed to change to get everything working in my current set-up. Apart from that, happy with the scripting which works perfectly. So @xchwarze is yours going to be the primary then?

Please.

I've been working through getting this script set up, scoured github today and found a copy. Was a bit dated, had some errors. Just back in here tonight, I tried the github copy from xchwarze, works better (thank you!). Had downloaded Google's cached copy of the documentation and gone through it, good to see it's available in the git repo.

xchwarze: I've created a pull request for changing the wiki to markdown. I'm not great at markdown, but it's a decent start I suppose. I can nuke my fork after you merge my changes.

@jsiegmund yes, I will try to keep the script updated
@budm Thanks for the help!

@xchwarze: NP
@jsiegmund: What little change did you make?

I've had a chance to really dig through the script and I have a couple of ideas that I may try to implement:

1. A subset of sensors that have their own entryDelay. This allows you to specify sensors that you know will be tripped when attempting to disarm the system, such as a front door sensor or PIR located in the same room as the security panel. IOW, all other sensors trip immediately (for example), but these specific sensors trip after a delay.

2. Maybe 'alertDevices' should also be unique per sensor class. I may not want a 105db siren going off when I'm sleeping and someone has breached the perimeter zone. I realize I can define different zones and put zone-specific alerts there, but I'm trying to wrap my head around when to use a zone and when to use a sensor class.

Anyway, it's a nice little script, let's keep it.

great work guys! let's continue this great script and make it more modular, compact and still easy to configure. Maybe the most important thing: let's continue the documentation.

I'm happy the github is still available but wonders if somebody made some nice changes already ?

Hello,

I'm currently trying ideAlarm and get following error: I'm pretty sure of all my device name.

Any idea where I can have a look ?

Thanks !

Math43 wrote: ↑Monday 03 September 2018 12:51 Hello,

I'm currently trying ideAlarm and get following error:

Code: Select all

2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: There is no device with that name or id: 550
2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: An error occured when calling event handler ideAlarm
2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: /srv/domoticz/scripts/dzVents/scripts/ideAlarmModule.lua:70: attempt to index a nil value

I'm pretty sure of all my device name.

Any idea where I can have a look ?

Thanks !

I only use the ID's with 'armingModeTextDevID and statusTextDevID'
All other options are device names

Can you recheck?

lepe wrote: ↑Monday 03 September 2018 13:55

Math43 wrote: ↑Monday 03 September 2018 12:51 Hello,

I'm currently trying ideAlarm and get following error:

Code: Select all

2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: There is no device with that name or id: 550
2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: An error occured when calling event handler ideAlarm
2018-09-03 12:20:04.297 Status: dzVents: Error (2.4.6): ideAlarm V2.4.0: /srv/domoticz/scripts/dzVents/scripts/ideAlarmModule.lua:70: attempt to index a nil value

I'm pretty sure of all my device name.

Any idea where I can have a look ?

Thanks !

I only use the ID's with 'armingModeTextDevID and statusTextDevID'
All other options are device names

Can you recheck?

I've used only device names but I haven't configured anything regarding 'armingModeTextDevID and statusTextDevID', maybe it's the issue !

Hopefully you've got it figured out by now, but essentially you create two virtual text devices (Mode and Status), and then you create two virtual toggle switches (Arm Home and Arm Away). And you set the off delay on the toggle switches to 2 seconds.

Then you go into the Setup->Devices view in Domoticz and locate the two virtual text devices you created (Mode and Status). You'll notice that Domoticz has assigned them each a device identifier (Idx). Those are the two numbers you use for 'armingModeTextDevID' and 'statusTextDevID' in the ideAlarmConfig.lua file.

Basically these two text devices are just a way for the script to send some text so you can see what the status of the alarm zone is. I put these text devices on my dashboard so I can get a quick overview of the alarm status on my phone.