search

akasma74 / Hass-Custom-Alarm

It is a fork of "Yet another take on a home assistant custom alarm" that will exist until its author is back to our Earth
79 stars 29 forks source link

error alarm_control_panel.bwalarm - Integration '' not found #77

Closed mnikser closed 4 years ago

mnikser commented 4 years ago

Platform & Browser: Hassio 0.104.3

Describe the bug 2020-01-31 20:25:57 ERROR (MainThread) [homeassistant.components.hassio] Platform error alarm_control_panel.bwalarm - Integration ' ' not found.

This error shows up even if I just do a "check config". I receive configuration not valid with this error.

To Reproduce For this started after updating HA to 0.104.4 from 0.102.3 and updating the alarm from the master branch.

Additional context I updated HA to v0.104.3 and the alarm stopped working. I applied the manifest change that is mentioned here, but it didn’t help. The error that I got was that it couldn’t load mqtt. I don’t use mqtt and don’t need it. Then I decided to completely update my alarm component from the master branch. Alarm_error

akasma74 commented 4 years ago

For this started after updating HA to 0.104.4 from 0.102.3 and updating the alarm from the master branch.

if it's from the master branch, its version should be v1.11.2pre1. Could you double check?

mnikser commented 4 years ago

I don't know where exactly to look for the version. The panel version is what I picked up from the panel version message. Anyways I think you can actually close this issue. I think the problem was the following line which I think I still had it in my configuration file and not commented out when I was testing:

panel_custom: !include panel_custom.yaml

Today I did some clean up of my configuration file and I removed these lines completely. Then I noticed the errors message doesn't show anymore, but I got the mqtt error again: 2020-02-02 14:58:32 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of bwalarm. Setup failed for dependencies: mqtt 2020-02-02 14:58:32 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform bwalarm.alarm_control_panel: Could not set up all dependencies. As I don't use mqtt, I changed the dependency in the manifest to null and then the alarm component started to load again. Alarm_info

The component is working now, but even in the information panel it doesn't show the component version properly.
Another question, have you disabled Perimeter mode? I can't enable whatever do.

akasma74 commented 4 years ago

panel_custom: !include panel_custom.yaml

oh yeah..

As I don't use mqtt, I changed the dependency in the manifest to null and then the alarm component started to load again.

the right way is to leave manifest.json alone with dependencies as they are and set enable_mqtt: false in your bwalarm.yaml

The component is working now, but even in the information panel it doesn't show the component version properly.

that's because you're not using the latest version. long time ago I changed it to only one version, there is no 'panel/component` version anymore. the version is here

have you disabled Perimeter mode?

I'm starting to think that you're using the original bwalarm.. This component supports Home, Away and Night(ex. perimeter) modes.

mnikser commented 4 years ago

Thank you very much for taking care of this component and responding to issues.

I changed the manifest to its original value and added the directive to disable mqtt in the configuration file. The mqtt error came back: 2020-02-04 19:23:36 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of bwalarm. Setup failed for dependencies: mqtt 2020-02-04 19:23:36 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform bwalarm.alarm_control_panel: Could not set up all dependencies.

Yes, I have this version: const _VERSION = 'v1.11.2pre1';

I am certain that now, I am using your version as I cloned this repository.

akasma74 commented 4 years ago

I cloned this repository

when you say cloned, does that mean you use the latest release or you cloned the master branch? and could you check out this just in case?

HerkDriver commented 4 years ago

I am also receiving this same error. I even wiped and did a clean install of HASS then downloaded most current master branch clone.

On reboot, I receive

Invalid config The following integrations and platforms could not be set up:

mqtt bwalarm.alarm_control_panel Please check your config.

My bwlarm.yaml only has this for now:

platform: bwalarm mqtt: enable_mqtt: false

Do we need the MQTT addon regardless if we use it in the alarm config?

akasma74 commented 4 years ago

I even wiped and did a clean install of HASS then downloaded most current master branch clone.

You mean you made a fress HA install and then manually installed this component from the master branch (not the latest release)?

From the error message I would say you have dependencies: [] in your custom_components/bwalarm/manifest.json.

Do we need the MQTT addon regardless if we use it in the alarm config?

I don't think we do. Just stopped my add-on and have different errors (cannot connect to MQTT/error talking to MQTT).

By the way, what's your HA version?

HerkDriver commented 4 years ago

Home Assistant: v0.104.3

Apologize for the terminology but this is what I did for the component version:

  1. Went to https://github.com/akasma74/Hass-Custom-Alarm
  2. Clicked green button CLONE or DOWNLOAD and saved to ZIP
  3. Installed ZIP contents into HA folders

I was able to launch the alarm panel after installing MQTT addon. Without the addon, the panel will not launch, regardless of the edits to bwlarm.yaml

akasma74 commented 4 years ago

Thanks for confirming! I never tried it without MQTT broker as my system hugely relies on MQTT so I always have it on. Will look into it.

mnikser commented 4 years ago

Yes, I have used your master branch.

akasma74 commented 4 years ago

Yes, I have used your master branch.

If you read our conversation above, the issue might be related to MQTT broker not running. Could you check that you have a functional one?

mnikser commented 4 years ago

I don't use mqtt component neither for alarm nor for anything else. It looks like HA first tries to confirm all components that are listed in the manifest are loaded before loading the alarm component. So if I don't have an mqtt component, even if I have a enable_mqtt: false in my configuration, it will fail because the alarm component doesn't get to load to read its configuration.

akasma74 commented 4 years ago

Well, for various reasons the alarm won't start unless you have a MQTT broker running. I'm looking into the issue, but at the moment running a MQTT broker is the easiest solution for you.

akasma74 commented 4 years ago

could you try this release as it contains some MQTT-related fixes?

akasma74 commented 4 years ago

I'm closing this issue because of no response. Feel free to open a new one if required.

mnikser commented 4 years ago

Sorry, I was away/busy for a while and then totally forgot this as my alarm works when I remove the mqtt from the manifest. I will test and let you know as soon as I can.

mnikser commented 4 years ago

Yes, the new release works fine. Thank you again.

akasma74 commented 4 years ago

cool! thanks for reporting it