search

dchesterton / texecom2mqtt-hassio

Home Assistant add-on. Connect to Texecom Premier Elite alarm panels and publish updates to MQTT. Supports arming/disarming as well as zone updates and alarm events.
https://hub.docker.com/r/dchesterton/texecom2mqtt
MIT License
52 stars 9 forks source link

Most sensors not showing status updates #89

Closed badnbusy closed 1 year ago

badnbusy commented 1 year ago

Just integrated with the texecom2mqtt using the HA add-on and although it detects the alarm, sensors and zones, only the Front Door contact sensor is changing change when I open/close... all the PIR's are just showing "clear" no matter if movement.

Is there a correct way to diagnose this, either on the Texecom Elite panel itself or via the addon?

2023-10-06 22:23:04 - INFO: Starting texecom2mqtt v1.2.3 (Node v16.13.0)...
2023-10-06 22:23:04 - INFO: Connected to alarm, sleeping for 2 seconds...
2023-10-06 22:23:06 - INFO: Connection ready
2023-10-06 22:23:06 - INFO: Logging in to panel
2023-10-06 22:23:07 - INFO: Successfully logged in to panel
2023-10-06 22:23:07 - INFO: Connected to MQTT broker: core-mosquitto:1883 (retain: true, clean: true, client_id: texecom2mqtt, qos: 0)
2023-10-06 22:23:07 - INFO: Serial number: *******
2023-10-06 22:23:07 - INFO: Panel: Premier Elite 64 (V5.01.03LS1)
2023-10-06 22:23:07 - INFO: Fetched Area A: HOME
2023-10-06 22:23:07 - INFO: Fetched Area B: Area B
2023-10-06 22:23:07 - INFO: Fetched Area C: Area C
2023-10-06 22:23:07 - INFO: Fetched Area D: Area D
2023-10-06 22:23:10 - INFO: Fetched Zone 9: FRONT DOOR PIR (Type: Guard Access; Areas: A)
2023-10-06 22:23:10 - INFO: Fetched Zone 10: DINNING ROOM PIR (Type: Guard; Areas: A)
2023-10-06 22:23:11 - INFO: Fetched Zone 11: DINNING ROOM PIR (Type: Guard; Areas: A)
2023-10-06 22:23:11 - INFO: Fetched Zone 12: LIVING PIR (Type: Guard; Areas: A)
2023-10-06 22:23:11 - INFO: Fetched Zone 13: LIVING ROOM PIR (Type: Guard; Areas: A)
2023-10-06 22:23:12 - INFO: Fetched Zone 14: KIT SNUG PIR (Type: Guard; Areas: A)
2023-10-06 22:23:12 - INFO: Fetched Zone 15: KIT SNUG PIR (Type: Guard; Areas: A)
2023-10-06 22:23:12 - INFO: Fetched Zone 16: LANDING PIR (Type: Guard; Areas: A)
2023-10-06 22:23:12 - INFO: Fetched Zone 17: FRONT DOOR (Type: Entry/Exit 1; Areas: A)
2023-10-06 22:23:13 - INFO: Fetched Zone 18: BEDROOM SHOCK (Type: Guard; Areas: A)
2023-10-06 22:23:13 - INFO: Fetched Zone 19: LANDING SHOCK (Type: Guard; Areas: A)
2023-10-06 22:23:14 - INFO: Fetched Zone 20: LANDING SHOCK 2 (Type: Guard; Areas: A)
2023-10-06 22:23:28 - INFO: Updating all zone states...
2023-10-06 22:23:28 - INFO: Updating all area states...
2023-10-06 22:23:29 - INFO: Application ready
2023-10-06 22:36:14 - INFO: FRONT DOOR status changed to Active
2023-10-06 22:36:41 - INFO: FRONT DOOR status changed to Secure
2023-10-06 05:34:33 - INFO: FRONT DOOR status changed to Active
2023-10-06 05:34:38 - INFO: FRONT DOOR status changed to Secure
2023-10-06 05:55:48 - INFO: FRONT DOOR status changed to Active
2023-10-06 05:55:54 - INFO: FRONT DOOR status changed to Secure
image

Looking at zigbee2mqtt, the messages are being received fine:

image

Thanks

ptruman commented 1 year ago

For some reason my previously working integration is now only showing the alarm panel and no sensors at all. I can manually (via configuration.yaml) map a PIR back in as a sensor, but that's not how it worked previously.

Could you post your texecom2mqtt config yaml and your mqtt config pls?

badnbusy commented 1 year ago

config is as basic as you can get:

host: 192.168.1.74
udl_password: "****"

and

host: mqtt://core-mosquitto
username: ****
password: ****
ptruman commented 1 year ago

What about your MQTT config? Something has gone v wonky in mine :\

ptruman commented 1 year ago

So, I totally wiped MQTT (Eclipse version) and reset to use 2.0.17 (as I did an update and it broke around the same time). I've forced HASS MQTT plugin to use V3 (not 3.1 or 5) and it worked. I've then put Eclipse back to latest and it's seemingly working again.

badnbusy commented 1 year ago

Great news for you, still not sure about my issue though 🙂

ptruman commented 1 year ago

All I can say is that when looking at texecom2mqtt logs, I could see DEBUG messages it was publishing binary sensor info, but that there were no similar mapped items in MQTT :\

I was using MQTT Explorer and pointing it at my MQTT - to validate what was being received - and MQTT wasn't getting anything from texecom2mqtt

Given I'd recently updated mosquitto I thought it was worth a punt, and totally trashed my MQTT docker, and set it back up again via older version. Lo, it worked. I also wonder if the HASS DB got upset and blocked things....

If you've not updated your MQTT version recently, probably not that for you, but it's worth a check with MQTT explorer. If you can't see see /homeassistant/binary_sensor/texecom2mqtt then that's your start point!

badnbusy commented 1 year ago

I can see the texecom2mqttt items in MQTTT explorer so I think they are being published/received fine.

@dchesterton Any ideas? Happy to provide more detail.

Thanks

ptruman commented 1 year ago

Are you getting both /texecom2mqtt and /homeassistant/binary-sensor ? The latter were the ones I was missing.

On Mon, 9 Oct 2023 at 08:28, badnbusy @.***> wrote:

I can see the texecom2mqttt items in MQTTT explorer so I think they are being published/received fine.

@dchesterton https://github.com/dchesterton Any ideas? Happy to provide more detail.

Thanks

— Reply to this email directly, view it on GitHub https://github.com/dchesterton/texecom2mqtt-hassio/issues/89#issuecomment-1752473483, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAPGIY3TWQ6OQ5VEOZ54DKDX6ORRLAVCNFSM6AAAAAA5XRS2KSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJSGQ3TGNBYGM . You are receiving this because you commented.Message ID: @.***>

badnbusy commented 1 year ago

Yes, seeing both in MQTTT explorer.

badnbusy commented 1 year ago

I re-learnt all ricochet sensors and they now appear and work fine. Closed!