search

GelidusResearch / device.docs

3 stars 2 forks source link

Motion sensor on Control #1

Closed rlust closed 3 weeks ago

rlust commented 3 months ago

How do I use the motion sensor in HA? I see the sensor on the device web server, but its state does not change.

descipher commented 3 months ago

@rlust The component needs to pass it's published sensor changes to HA through the API definition.

#Enable Home Assistant API
api:
  encryption:
    key: "rRYCZwRhzruNwm5cNQ/eKX1nhRtErP8NmWbClRQTGZY="

When you create a device in the ESPHome Dashboard following the guide it creates an HA device instance and the esp device needs to use the generated key for access, this matches the HA device object. If the key is changed in the YAML it will not work against the originally created HA device. It will also be associated to an entity and if it's not working it will look like this.

image

You can delete a device and it should discover the active one that's not registered, then you can clean up any entity that's orphaned as well. When it's discovered you can submit the key again to re-register it as a device using the key from the ESPHome YAML def.

HA->settings->devices

image

rlust commented 3 months ago

I was asking about the GDO garage door opener. My wall switch has a motion detector which turn on opener light. The web page of the GDO shows the motion detector but I am not getting the events.

descipher commented 3 months ago

I see, what GDO and wall model are we working with? Also what firmware RATGDO or Secplus GDO?

rlust commented 2 months ago

I am using a Chamberlain Serial # GW0E00025AE, PLUS Belt Drive. Remote is Chamberlain with motion detector. Garage Door Mail Config

rlust commented 2 months ago

IMG_9332

rlust commented 2 months ago

I am having issues with Home Assistant GD not staying online. Getting API Errors. I have an API Encryption Key set.

api: encryption: key: "sGhSST9UUwUXq2UK6gvD3ZudL51J7jFlZLD25xdT/H0="

Main Garage Door Big Door

external_components:

substitutions: id_prefix: grgdo1 friendly_name: "GDO1_Main" uart_tx_pin: GPIO22 # J4 Pin 1 or 3 Red CTRL uart_rx_pin: GPIO21 # J4 Pin 1 or 3 Red CTRL

input_obst_pin: GPIO23 # J4 Pin 4 Grey OBST - not required with secplus_gdo

dry_contact_open_pin: GPIO17 # J4 Pin 6 Green dry_contact_close_pin: GPIO19 # J4 Pin 7 Blue dry_contact_light_pin: GPIO18 # J4 Pin 8 Orange

esp32: board: esp32dev framework: type: esp-idf version: recommended

esphome:

name: grgdo1

name: gdo1 platformio_options: lib_deps:

descipher commented 2 months ago

I have the same motion sensor issue on my old LM889 test rig. I switched to an old RATGDO firmware (pre V1 version) and it works. Put it the scope and I see a different baud rate coming from the wall control. The secplus version does not have auto-baud so this is an expected issue on that version however it does not work on the current RATGDO firmware which has auto-baud. Not sure why it broke yet. I have logged an issue for auto-baud on the secplus site. Will look at that code in the coming weeks, may be a timing change. The API errors are not related, for those you need to look at the logs on HA. I have cleared that type of issue by removing any esphome devices with that error from the HA integration and the cleaning of any entity remnants. Then restarting the esphome device will trigger a rediscover it and you can re-add it on the integration. Just don’t remove it from the ESPHome dashboard. Also what esphome version are you running?

rlust commented 2 months ago

I am running ESPHome 2024.6.6.

descipher commented 2 months ago

@rlust 2024.6.6 may have some resource issues with the web_server, I have observed async web server issues with libretiny modules and they also use rtos like the secplus implementation. If the HA api issues persist try commenting the web_server out. 2024.4.2 is the version I currently run atm