Another questions or bug rather…
I have an automation watching for when the ELK system alarm goes off, the automation turns on a siren.
alarm_control_panel.elk_area_1 = { “Alarm”: “Burglar Alarm”}
The issue is that when the system is counting down, durning the time you come in through a door and can enter your code my siren now goes off.
Shouldn’t the alarm_control_panel.elk_area_1 be something like ‘Tripped entry timer’?
Implementing entry/exit timer reporting / awareness is on the list of things to do, and would likely solve the problem. If nothing else, you could add a condition to prevent the alarm sounding as long as EE timer is active. (once it’s implemented)
Hopefully I can knock it out this next few days / weekend. Actually implementing it won’t take long.
I installed the package, but am getting an error on startup…
> 2018-06-23 22:38:33 DEBUG (SyncWorker_4) [PyElk.Elk] Performing fastload
2018-06-23 22:38:33 DEBUG (SyncWorker_4) [PyElk.Elk] Failed to load fast load file - file not found
2018-06-23 22:38:33 ERROR (SyncWorker_4) [custom_components.elkm1] invalid URL, protocol ‘elk’ not known
2018-06-23 22:38:33 INFO (MainThread) [homeassistant.setup] Setup of domain elkm1 took 4.9 seconds.
2018-06-23 22:38:33 ERROR (MainThread) [homeassistant.setup] Setup failed for elkm1: Component failed to initialize.
2018-06-23 22:38:33 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: domain=persistent_notification, service=create, service_data=title=Invalid config, message=The following components and platforms could not be set up:Please check your config., notification_id=invalid_config, service_call_id=1971345872-2>
2018-06-23 22:38:33 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=persistent_notification.invalid_config, old_state=None, new_state=<state persistent_notification.invalid_config=notifying; title=Invalid config, message=The following components and platforms could not be set up:
I’ve restart the HASS.IO several times, all with the same errors.
Can someone point me in the right direction?
@project_x, I think that you have the wrong branch of the elkm1 component installed. The one that most of us are using these days has the “fastload” stuff disabled. You should checkout/download the gwww-elkm1-lib branch of the ha-elkm1 repository.
mentions this earlier in the thread.
Thank you.
I read thru the thread all day, but must have gotten lost
I read thru the thread all day, but must have gotten lost
Yes, this topic is quite the epic thread! It’s certainly easy to imagine missing that little bit of information…
The elkm1 integration is really working quite well lately. I think the rough edges are more about documentation than anything else. Thanks again to @BioSehnsucht for all his hard work here. This is really a wonderful addition to Home Assistant.
Just pushed a small update so that it will report that the entry or exit timer is running instead of burglar alarm, if the timer is still running.
Woohoo! Thanks I’ll give it a try now!
Not sure what I messed up. I’m getting this:
2018-06-25 21:56:41 ERROR (MainThread) [homeassistant.setup] Error during setup of component elkm1
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/setup.py", line 143, in _async_setup_component
hass, processed_config)
File "/usr/lib/python3.6/asyncio/coroutines.py", line 210, in coro
res = func(*args, **kw)
File "/config/custom_components/elkm1.py", line 175, in async_setup
from elkm1.const import Max
ModuleNotFoundError: No module named 'elkm1.const'; 'elkm1' is not a package
Weird, if it was working before it should still work with the same elkm1 lib version… Did you try restarting HASS a second time?
I did yes. I’ve tried a few things…
That file that it’s erroring on shouldn’t have changed any for that update - do you know what commit you were on previously (or the day you installed my ha-elkm1 code) ?
So let me make sure I did this right. I downloaded the entire folder from https://github.com/BioSehnsucht/ha-elkm1/tree/gwww-elkm1-lib
and replaced my files in the Custom_Components folder. It that correct?
That should work. The only file that should have changed (assuming you were already on the most recent version before today) was the alarm_control_panel/elkm1.py file - but replacing the existing files that didn’t change shouldn’t matter, having net zero effect (since the replacements should be the same as what you already had).
If you look in your HASS config/deps/lib/python3.6/site-packages/ folder (that’s where it is under Docker, not 100% sure for non-Docker - the folder where HASS auto installs dependencies) there should be another elkm1 folder that contains gwww’s Python library that my HASS code uses (this is auto-installed by HASS, you shouldn’t ever have to mess with it). If it’s missing that would cause the error you’re seeing. there may also be an elkm1-0.4.5.dist-info folder (or similar) there - whatever version is listed, if there is one, is the version of elkm1 that HASS has installed.
edit: Also, what version of HASS are you running? It’s possible you’ve also updated that at some point and my code no longer works on latest HASS (I haven’t updated my HASS in a few weeks)
Well this is strange. I completely deleted all the files. Restored them from a new download and it seems to be working. I am running 0.72.0.
So I was able to test. While the alarm was counting down it said triggered. When the Alarm went off… It still said triggered. It did not update to any other state.
Looking at the code it appears to be commented out still. Should I uncomment? Is that intentional?
Ah, I only changed the code that sets the ‘Alarm’ attribute so that it would reflect entry/exit status when timers are running, since you had mentioned checking it for your automation, but I guess you can’t see that in the UI in any case, and the UI should also provide useful information.
I suppose I can have the alarm state itself be ‘arming’ for exit timer and ‘pending’ for entry timer, instead of ‘triggered’ while the entry/exit timers run. (these are some of the predefined options in HASS)
I will try to get that done later today / tonight.
Sounds good. No rush - on vaca for a week.
Implemented the new code - just replaced the file mentioned; looks good so far; ready to test the next drop when published
cheers
Damian
I doubt this will be reproducible, and therefore may be hard to troubleshoot, but here goes. Everything working great and I can control a lot of my stuff through the integration with Google Home. BUT, google home sees EVERYTHING from Elk, regardless if it shows up in the Homeassistant UI. Per BioSehnsucht in a previous response to me I finally modified my configuration file to exclude all the things in ELK that I didn’t want Google Home to see.
Now here is my problem. I have a Filtrete 3M-50 wifi thermostat (a re-branded Radio Thermostat of America CT-50 I believe) and no thermostats on my Elk. My thermostat is added with
climate:
platform: radiotherm
host:
- 192.168.1.51
and I added
thermostat:
exclude:
- 1-16
and it causes my wifi thermostat to cease functioning. As soon as I comment out the thermostat section in the Elk my thermostat works again.
Anyway to fix this? otherwise Google thinks I have 17 thermostats.