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

Sensor fail to detct after first detection #364

Open
5xPa opened this issue Apr 23, 2022 · 7 comments
Open

Sensor fail to detct after first detection #364

5xPa opened this issue Apr 23, 2022 · 7 comments

Comments

@5xPa
Copy link

5xPa commented Apr 23, 2022

Front door contact on first operation would show open until door closed. If I open the door again it would blip open then show closed even with door open.
Rebooted panel problem still existed
Rebooted HomeBridge problem still exists.

Loaded previous days backup returning to version 0.4 all working Ok

@garethflowers
Copy link
Owner

There's nothing between v0.0.4 and v0.0.5 that would cause this kind of issue.

If the issue persists can you try running Homebridge in Debug Mode - and then provide a sample of the Homebridge logs around the time the problem happened.

@5xPa
Copy link
Author

5xPa commented Apr 25, 2022

Gareth thanks for the prompt reply. I reinstalled ver 0.5 same problem. I view on homekit the FrontDoor, first time I open and close the door I can see the change in HomeKit. I Open and close the door again and no change. I have as you requested enabled debug. Have attached the log.
A couple of days ago I update Homebridge to version 1.4.0 which there was an option to update Node.js. Could that be relevant to the problem?
Attached is a file with the log from around this mornings update[](url
homebridge texecom connect problem.txt
)
Hopefully the log file has uploaded. If not please let me know and I shall try again

@5xPa 5xPa closed this as completed Apr 25, 2022
@5xPa 5xPa reopened this Apr 25, 2022
@5xPa
Copy link
Author

5xPa commented Apr 25, 2022

Sorry I selected "close with comment" now doubt you can discern I am not that computer literate.
thanks for the work you dedicate to this.

@amitpatel99
Copy link

Hi there,
Just trying to add our Texecom Alarm into HomeKit and get the following...
[homebridge-texecom-connect] Connected to SmartCom - 192.168.86.93:10001
[5/12/2022, 4:02:10 PM] [Google Smart Home] Sending Sync Request
[5/12/2022, 4:02:10 PM] [Google Smart Home] Please connect with the Google Home app: https://git.io/JfuHC
[5/12/2022, 4:02:26 PM] [homebridge-texecom-connect] Invalid data from SmartCOM
[5/12/2022, 4:02:26 PM] [homebridge-texecom-connect] Reconnecting to SmartCom - 192.168.86.93:10001
[5/12/2022, 4:02:36 PM] [homebridge-texecom-connect] Connected to SmartCom - 192.168.86.93:10001
[5/12/2022, 4:02:44 PM] [homebridge-texecom-connect] Invalid data from SmartCOM
[5/12/2022, 4:02:44 PM] [homebridge-texecom-connect] Reconnecting to SmartCom - 192.168.86.93:10001
[5/12/2022, 4:02:54 PM] [homebridge-texecom-connect] Connected to SmartCom - 192.168.86.93:10001
[5/12/2022, 4:02:58 PM] [homebridge-texecom-connect] Texecom Alarm : Security System Mode Changed : Night
[5/12/2022, 4:02:58 PM] [homebridge-texecom-connect] Invalid data from SmartCOM
[5/12/2022, 4:02:58 PM] [homebridge-texecom-connect] Reconnecting to SmartCom - 192.168.86.93:10001
2022-05-12T15:03:01.777Z hapNodeJSClient Events [{"host":"192.168.86.30","port":54792,"aid":2,"iid":10,"value":2,"status":2}]

Any help greatly appreciated. Thanks

@5xPa
Copy link
Author

5xPa commented May 15, 2022

Gareth updated to version 0.6 problem remains.
Open door Homebridge indicates open
Close door indicates closed
Open door Homebridge blips open then closed even with door open
Door Contact going closed when open.txt
.

@garethflowers
Copy link
Owner

I've extracted the logs specific for the TexecomConnect plugin and, assuming you have set the door up as "Garage Door", it all appears to be working fine. The is a 3-4 second gap between opening and closing the door.

[15/05/2022, 11:44:12] [TexecomConnect] Socket Data: "Z0181
[15/05/2022, 11:44:12] [TexecomConnect] Living Room : Motion Detected : Yes
[15/05/2022, 11:44:20] [TexecomConnect] Socket Data: "Z0271
[15/05/2022, 11:44:20] [TexecomConnect] Garage Door : Contact Sensor State : Open
[15/05/2022, 11:44:22] [TexecomConnect] Socket Data: "Z0180
[15/05/2022, 11:44:22] [TexecomConnect] Living Room : Motion Detected : No
[15/05/2022, 11:44:23] [TexecomConnect] Socket Data: "Z0270
[15/05/2022, 11:44:23] [TexecomConnect] Garage Door : Contact Sensor State : Closed
[15/05/2022, 11:44:34] [TexecomConnect] Socket Data: "Z0271
[15/05/2022, 11:44:34] [TexecomConnect] Garage Door : Contact Sensor State : Open
[15/05/2022, 11:44:38] [TexecomConnect] Socket Data: "Z0270
[15/05/2022, 11:44:38] [TexecomConnect] Garage Door : Contact Sensor State : Closed
[15/05/2022, 11:44:50] [TexecomConnect] Socket Data: "Z0181
[15/05/2022, 11:44:50] [TexecomConnect] Living Room : Motion Detected : Yes

@nigetech
Copy link

Afternoon,

I am also having this issue - I can't pinpoint when it started, but no more than a month ago, but exactly as above.

First try, door opens, sensor shows open, stays open till door is closed, sensor shows closed.
Second try, door opens, sensor shows open, goes to closed after a second or two without the door actually being closed.

This then repeats in sequence, which is even more odd.

At first I thought it was homekit, but the accessory shows in homebridge as the same. I checked in Wintex and it shows correct open/close status in there.

All very odd.

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