Again, amazing job @AhmadK
Just updated to the latest and got the below error - role back to previous version
Invalid config
I am not using MQTT
The following integrations and platforms could not be set up:
- mqtt
- bwalarm.alarm_control_panel
Please check your config.
and
his component is not working!
Unable to prepare setup for platform bwalarm.alarm_control_panel: Could not set up all dependencies.
(setup.py)
Unable to set up dependencies of bwalarm. Setup failed for dependencies: mqtt
(setup.py)
Check the Home Assistant log for more details.
Home Assistant: v0.105.2
Iâm facing the exact same thing. I also tried removing the Integration, but that didnât solve it.
Didnât even know that I was using mqtt, but I guess that is a part of the bwalarm component?
Same issue here, I was on 103.6 and got the error, updated to latest 105.2 but same issue. I dont have mqtt installed in my setup (in HA).
HA 0.105.2
Donât use MQTT at all
Roled back to
v1.11.2pre1
Thanks for all your work keeping this going
@Yoinkz, @sweup, @Kelvin_Sudlow could you confirm that:
- You donât have any MQTT broker running with your HA setup
- You have
mqtt:
enable_mqtt: false
or donât have mqtt
section at all in your bwalarm.yaml
- you started getting errors when updated this component today to the v1.12?
HI
I donât have MQTT broker running with HA
Error only happens with v1.12 released today
Iâve updated my release post as it does not work if you are not using MQTT.
Need to investigate it further.
- no mqtt in HA
- i havent edit anything in bwalarm or stated âfalseâ
- errors came after 1.12
There is a fresh new release available that should work for everyone so feel free to check it out and thanks for your patience!
the custom panel doesnât work for me, the panel doesnât open, it goes blank, 105.2, Iâm
For me it seams to work. Im able to reach panel and setting, lovelace card is showing no errors, logs are fine. Thanks for hard work!
Same panel went blank, restarted, But still blank. Using HA app on android get error unable to open panel. No errors in log. In chrome it did appear to work but cleared cache and same issue -blank
Has error in log, did not notice the first time
Mon Feb 10 2020 10:57:30 GMT+1300 (New Zealand Daylight Time)
http://#####:8123/api/panel_custom/alarm:2038:32 Uncaught ReferenceError: $ is not defined
Unhandled exception
Traceback (most recent call last):
File â/usr/local/lib/python3.7/site-packages/aiohttp/web_protocol.pyâ, line 461, in start
await prepare_meth(request)
File â/usr/local/lib/python3.7/site-packages/aiohttp/web_fileresponse.pyâ, line 224, in prepare
st = await loop.run_in_executor(None, filepath.stat)
File â/usr/local/lib/python3.7/concurrent/futures/thread.pyâ, line 57, in run
result = self.fn(*self.args, **self.kwargs)
File â/usr/local/lib/python3.7/pathlib.pyâ, line 1178, in stat
return self._accessor.stat(self)
FileNotFoundError: [Errno 2] No such file or directory: â/config/custom_components/bwalarm/resources/panel.htmlâ
do you have panel.yaml
in /config/custom_components/bwalarm/resources/
?
Have a panel.html, as mentioned no changes have been made except updated
Sorted mine, had to re look at the folders structure/ file locations etc and some how they were quite different to the current build. All though always updated from HACS
Fixed that and all working
I use zwave scene events triggered by my wall switches right now. Doesnât run unless one of us is actually home. Itâs just supposed to be a temporary measure until I find a decent zwave keypad that I know will work with HA but Iâll say itâs bloody convenient for now. I suppose itâs not the most secure setup in the world but itâs better than the alarm I had before (none) and my wife will actually uses this so itâll do for now.
We have a Nest Hub right near enough to the door and I had planned on casting a lovelace view with the keypad on it when someone comes home but the cast feature doesnât seem to be ready for prime time yet.
Hereâs an example of the zwave scene automation. Easy peasy.
trigger:
- platform: event
event_type: zwave.scene_activated
event_data:
entity_id: zwave.side_entrance_light
scene_data: 7980
scene_id: 1
condition:
- condition: state
entity_id: binary_sensor.someone_home
state: 'on'
action:
- service: script.arm_alarm_home
what was the difference?
from the very beginning? because HACS can only care of custom_components/bwalarm
and doesnât know about user-specific resources/bwalarm/