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

Showing Disarm when is arm #84

Open
bigjuanpa opened this issue Sep 23, 2020 · 15 comments
Open

Showing Disarm when is arm #84

bigjuanpa opened this issue Sep 23, 2020 · 15 comments

Comments

@bigjuanpa
Copy link

Hi for some reason sometimes if the status is change and is not registered on mqtt after check when the alarm is arm and I check the panel status it show's disarm.
I test that on node red and report disarm when is arm.
The only fix is disarm and arm again from the panel and after that on the next arm it fix.

Any idea why the serial report disarm when is arm?
Thanks

@userMak
Copy link

userMak commented Sep 23, 2020

Same think happening to me some times

@bigjuanpa
Copy link
Author

at this moment im checking every 15 minutes the state.

@bigjuanpa
Copy link
Author

Same issue even asking a few times return disarm when is arm.
any help?

@maragelis
Copy link
Owner

You will have to send a status request message.

@userMak
Copy link

userMak commented May 27, 2022

Same issue even asking a few times return disarm when is arm.
any help?

Hi have you found a solution?
I am not sure how I could the status request message as @maragelis suggest

@croftsquirrel
Copy link

I also have the same problem. Can't figure out what is causing it. In my particular case it seems to more likely happen when the system is armed and we have a power outage. When the power is restored I can't send disarm message through. Or sometimes even when it says disarmed it still actually armed and then is triggered. Also then need to manually disarm on panel.
@maragelis is there any updates or fixes that can resolve this? I have the latest version available 2.2.3

@maragelis
Copy link
Owner

There is a way to get over this, just set the sendmqtt method to send an mqtt retain message, that will keep the last message sent on the mqtt topic. That way when HA reboots it will always read the last status sent.

@userMak
Copy link

userMak commented Jul 9, 2022

There is a way to get over this, just set the sendmqtt method to send an mqtt retain message, that will keep the last message sent on the mqtt topic. That way when HA reboots it will always read the last status sent.

Hi, can you give an example please?

@croftsquirrel
Copy link

croftsquirrel commented Jul 9, 2022

It's seems to be a problem with connecting to WiFi or MQTT even though WiFi is back and up and running. Also the zones opening also doesn't get sent through from the ESP8266.
Is there a way to program the "void handleMqttKeepAlive()" or similar section in the ParadoxAlarmSystemOTA.ino to restart the device if there is no connection. I need the ESP8266 to restart when it can't connect, not just to retry the connection.
Sorry I'm not a developer so not too sure what to do but could one put this in the code somewhere if it doesn't connect. "ESP.reset();" ?
When I manually reset the ESP8266 it starts working again.

@maragelis
Copy link
Owner

I am currently testing a version using micropython on the esp32. Seems to be very stable and doesn't suffer from random disconnects. It will also be able to run on a raspberry pico w. So far I have got the hassio code working, and working on the web interface. So be patient code will be uploaded to GitHub soon.

@maragelis
Copy link
Owner

@bigjuanpa
Copy link
Author

https://github.com/maragelis/micropython_paradox
Looks really good, I never use micropython on esp32.
Do you have any tutorial or something?
Do you think this is better tan your paradox for esp32 code?
Thanks

@maragelis
Copy link
Owner

yes much better and runs quite well.

@maragelis
Copy link
Owner

need testers so your help will be gratefully appreciated

@bigjuanpa
Copy link
Author

I will try to install and test it in a few days.
The connection are the same than before?
Regards.

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

4 participants