search

maeneak / utecio-ha

Ultraloq BLE Integration for HACS
MIT License
8 stars 0 forks source link

Lock only beeps #24

Open mrmichael1389 opened 5 months ago

mrmichael1389 commented 5 months ago

System Health details

System Information

version core-2024.3.3
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.12.2
os_name Linux
os_version 6.6.20-haos
arch x86_64
timezone America/Chicago
config_dir /config
Home Assistant Community Store GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok GitHub API Calls Remaining | 4994 Installed Version | 1.34.0 Stage | running Available Repositories | 1406 Downloaded Repositories | 14
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 12.1 -- | -- update_channel | stable supervisor_version | supervisor-2024.03.1 agent_version | 1.6.0 docker_version | 24.0.7 disk_total | 125.3 GB disk_used | 34.3 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Z-Wave JS (0.4.5), File editor (5.8.0), Samba share (12.3.1), Check Home Assistant configuration (3.11.0), Duck DNS (1.16.0), Terminal & SSH (9.10.0), Studio Code Server (5.15.0), Mosquitto broker (6.4.0), WireGuard (0.10.2), Advanced SSH & Web Terminal (17.2.0), ESPHome (2024.3.1), go2rtc (1.8.5), Piper (1.5.0), openWakeWord (1.10.0), Whisper (2.0.0)
Dashboards dashboards | 2 -- | -- resources | 1 views | 11 mode | storage
Recorder oldest_recorder_run | March 23, 2024 at 12:43 PM -- | -- current_recorder_run | March 31, 2024 at 6:24 AM estimated_db_size | 6811.00 MiB database_engine | sqlite database_version | 3.44.2

Checklist

Describe the issue

I can add the integration and my 3 locks show up as entities under the integration. When trying to lock or unlock, it makes the lock beep, but does not change the bolt position. I have a Bluetooth proxy for communication. My locks are also connected via Zwave.

Thanks for your work on this integration. I’m happy to help test. I have 3 U-Bolt-Zwave locks. I hoped that updating to the latest version of the integration would help, but no change.

Reproduction steps

  1. Configure integration
  2. Go to lock entity
  3. Push lock
  4. Alternatively, go to developer tools
  5. Run the lock service on the lock entity (with or without a code)

...

Debug logs

This error originated from a custom integration.

Logger: custom_components.ultraloq_ble
Source: custom_components/ultraloq_ble/lock.py:203
integration: Ultraloq Bluetooth (documentation, issues)
First occurred: 7:04:47 AM (3 occurrences)
Last logged: 7:11:46 AM

('Error communicating with device Front Door Lock(FC:A8:9B:XX:XX:XX).', 'Command LOCK_STATUS failed.')
('Error communicating with device Front Door Lock(FC:A8:9B:XX:XX:XX).', 'Command ADMIN_LOGIN failed.')
('Error communicating with device Front Door Lock(FC:A8:9B:XX:XX:XX).', 'Command BOLT_LOCK failed.')

Diagnostics dump

No response

Daniel-dev22 commented 5 months ago

Do you see any other ultraloq errors in your logs?

Do you have the U-Bolt Zwave lock?

maeneak commented 5 months ago

Honestly, if you have zwave locks I would recommend using HAs built-in zwave support. Utec's Bluetooth implementation is piss poor and the zwave interface should provide most of the lock functionality and provide real-time state updates. With the Bluetooth interface we are forced to conduct regular polling for state updates which is not efficient and time consuming. If you still want to use Bluetooth I'll be releasing an update with debug functionality soon, this will help translate some of the errors you are seeing.

Daniel-dev22 commented 5 months ago

I opened a few issues upstream 2 of which are related to the the way the zwave lock is being read by the library.

https://github.com/maeneak/utecio/issues/17 https://github.com/maeneak/utecio/issues/15

mrmichael1389 commented 5 months ago

Ok I understand. The reason I’m hoping to use Bluetooth instead of Zwave is because I’m hoping it will be more flexible. Zwave requires the controller/dongle which is USB. I am using Zwave JS UI to make that accessible over my network, but I’m not thrilled with the way I have to do this. Also, my Zwave network isn’t super reliable because my house is fairly large and I don’t have a lot of Zwave devices. I’m using an ESP32 Bluetooth proxy which I can easily place centrally in my home and extend HA Bluetooth connectivity to my locks.

Get Outlook for iOShttps://aka.ms/o0ukef

From: maeneak @.> Sent: Sunday, March 31, 2024 9:41:12 AM To: maeneak/utecio-ha @.> Cc: mrmichael1389 @.>; Author @.> Subject: Re: [maeneak/utecio-ha] Lock only beeps (Issue #24)

Honestly, if you have zwave locks I would recommend using HAs built-in zwave support. Utec's Bluetooth implementation is piss poor and the zwave interface should provide most of the lock functionality and provide real-time state updates. With the Bluetooth interface we are forced to conduct regular polling for state updates which is not efficient and time consuming. If you still want to use Bluetooth I'll be releasing an update with debug functionality soon, this will help translate some of the errors you are seeing.

— Reply to this email directly, view it on GitHubhttps://github.com/maeneak/utecio-ha/issues/24#issuecomment-2028776895, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQCTHOZJRVFCLZWFCG53XJLY3AOARAVCNFSM6AAAAABFQMWA22VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRYG43TMOBZGU. You are receiving this because you authored the thread.Message ID: @.***>

Daniel-dev22 commented 5 months ago

The reason I would use this even though I have Zwave as well on the lock is to control auto lock time and lock mode both can't be done via zwave. Also for redundancy.

Daniel-dev22 commented 4 months ago

@maeneak just checking in to see if you can share all of your research and anything else you think might be helpful for developing for utec