Motor not working on RJO101 when opening/closing the door

[sirmeili]

I don't know if this is expected. I'm using the SecPlus-GDO firmware for ESPHome.

I noticed that when opening closing the door the motor entity does not change. this might be expected for my GDO, but it seems like it would be simple to at least "fake" as the device knows when the door is opening/closing.

This is not a huge issue, and I don't really have a use case for the motor entity.

[GelidusResearch]

I just checked it on a secplusv2 test rig without issue.

external_components:
  - source: github://gelidusresearch/esphome-secplus-gdo
    components: [ secplus_gdo ]
    refresh: 1d

Are you running the current release?

[GelidusResearch]

[GelidusResearch]

[sirmeili]

I just got it Thursday. I did add the yaml into ESPHome Builder and "installed" it which I believe also grabs the code from the repo, compiles and updates it. I noticed the ESPHome version entity on the device went up from 2026.3 to 2026.4.5.

I don't know if this updates to the newest version or not and I don't see an entity with the version outside the one for the ESPHome version. At the top I have:

external_components:
  - source: github://GelidusResearch/esphome-secplus-gdo
    components: [ secplus_gdo ]
    refresh: 0s

You can see from the logs it shows it's closing and then closed but never changes the "motor" entiy:

[GelidusResearch]

That would be the current code, it is possible that it's not using the same state messages as other models. 39 openings! that door is very new, could be a change in the design too.

[sirmeili]

Ha! Yes, I just installed the opener. It's actually on my work shop. I'm doing this because I have a tendency to forget to close it when it rains... Lol.

Like I said it's not a huge issue. I don't have a specific use case but was wondering. I could easily derive the motor is running based on the actual open/closing/opening/open state (I think)

[sirmeili]

I think you can close this. Maybe my model (RJO101) doesn't support that signaling.

On another note, also added BT Proxy to it, which was nice because I picked up a Yale BT lock and I can just use the garage door opener as a BT Proxy to the lock.

[GelidusResearch]

I suspect they removed/changed it in the current firmware. If you have an 889LMW or any LCD wall control we can collect the firmware rev. Its done by holding the light and the first menu buttons.

You should watch the resource consumption with a BT Proxy and a Web Server locally, its likely OK j but ESPHome does caution about the heavy use of resources on either of them.

If you see lags etc. load a debug component:

debug:
  update_interval: 5s

text_sensor:
  - platform: debug
    device:
      name: "Device Info"
    reset_reason:
      name: "Reset Reason"

sensor:
  - platform: debug
    free:
      name: "Heap Free"
    block:
      name: "Heap Max Block"
    min_free:
      name: "Heap Min Free"
    fragmentation:
      name: "Heap Fragmentation"

[sirmeili]

Thanks, I may remove the web server as I really don't need it as I have HA now. I added your configs above and got the following:

[GelidusResearch]

Looks good, you can leave them loaded, I have only hit issues by inadvertently loading multiple web instances.

[GelidusResearch]

Just make sure you secure the web server with a UID and password.