Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alarm state messages not processed #22

Open
gaborkissjr opened this issue Dec 10, 2018 · 2 comments
Open

Alarm state messages not processed #22

gaborkissjr opened this issue Dec 10, 2018 · 2 comments

Comments

@gaborkissjr
Copy link

Hi!

First, big thanks for your application, this is exactly what I looking for.

However, let me share one of my observation, and at this moment I can't decide if it's an issue or just a misconfiguration.

I've set the mqtt broker address, and alarm command and state topic as follow:

Alarm Command: ha/alarm/set
Alarm Topic: ha/alarm

It looks like the application succesfully sends out alarm commands to the broker (confirmed in home assistant, and in a mqtt client as well), however the state messages just simply not processed in the application.

E.g. I'm able to arm the alarm panel with the application, and it's visible in the screen also, and I can see the same in home assistant, however, if I try to disarm it in the application, then a DISARM message sent out, but nothing happens in the app.
System state remains in 'ARMED AWAY', with red lock in the middle. Later it changes to a grey lock, with only 'SYSTEM' caption.
I can confirm that the 'disarmed' message published by the home assistant to the Alarm Topic queue, confirmed in the 3rdparty mqtt client.

Am I miss something?
Are there any requirements related to the mqtt broker maybe? It's installed on an orangepi/armbian, but I think it's quite new.

Thanks for your assistance,
Gabor

@gaborkissjr
Copy link
Author

Hi,

So after a few tests, it looks like it works perfectly if I use the default value for 'Alarm Topic' variable.
If I leave it as 'home/alarm' it works like a charm.

Now as a workaround I've modified this parameter on home assistant side, but it would be very nice if I can change this parameter as well.

Thanks!
Gabor

@thanksmister
Copy link
Owner

I will check when I have time, but it should be accepting any value you like. It may not be propagating through the application properly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants