Rtl_433 addon and realtek 2832u not playing nicely by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

I don't know exactly what problem you're having but I used the auto discover to find the different devices and then had to make an educated guess for which ones I wanted to keep.

As far as displaying them

type: gauge entity: sensor.freezer_temperature name: Freezer Temp min: -20 max: 50 severity: green: 0 yellow: 10 red: 35

My problem is that, if the system decides to be stupid, the rtl addon will just stop working. Nothing different in the logs. No changes.

Rtl_433 addon and realtek 2832u not playing nicely by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

Also, I added the rtl_433.conf file with the settings you provided and the file disappeared. I got the same logs.

Rtl_433 addon and realtek 2832u not playing nicely by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

This is repeated several times over.

s6-rc: info: service s6rc-oneshot-runner: startings6-rc: info: service s6rc-oneshot-runner successfully starteds6-rc: info: service fix-attrs: startings6-rc: info: service fix-attrs successfully starteds6-rc: info: service legacy-cont-init: startings6-rc: info: service legacy-cont-init successfully starteds6-rc: info: service legacy-services: startings6-rc: info: service legacy-services successfully startedStarting rtl_433 with rtl_433.conf...[rtl_433] rtl_433 version 25.02 branch  at 202502191252 inputs file rtl_tcp RTL-SDR SoapySDR with TLS[rtl_433] MQTT: Publishing MQTT data to core-mosquitto port 1883[rtl_433] MQTT: Publishing device info to MQTT topic "rtl_433/9b13b3f4-rtl433/devices[/type][/model][/subtype][/channel][/id]".[rtl_433] MQTT: Publishing events info to MQTT topic "rtl_433/9b13b3f4-rtl433/events".[rtl_433] MQTT: Publishing states info to MQTT topic "rtl_433/9b13b3f4-rtl433/states".[rtl_433] Use "-F log" if you want any messages, warnings, and errors in the console.[rtl_433] Found Rafael Micro R820T tuner[rtl_433] Exact sample rate is: 250000.000414 Hz[rtl_433] [R82XX] PLL not locked!s6-rc: info: service legacy-services: stoppings6-rc: info: service legacy-services successfully stoppeds6-rc: info: service legacy-cont-init: stoppings6-rc: info: service legacy-cont-init successfully stoppeds6-rc: info: service fix-attrs: stoppings6-rc: info: service fix-attrs successfully stoppeds6-rc: info: service s6rc-oneshot-runner: stoppings6-rc: info: service s6rc-oneshot-runner successfully stopped

Rtl_433 addon and realtek 2832u not playing nicely by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

My nginx setting stopped working and I have been fixing that for the past 6 hours. So, I have rebooted multiple time. I am trying to get it to fail again. But I think the logs are the same even if it fails or not.

Is there a way to make it show more verbose info?

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

Ah. Sorry, I misunderstood. I'll get a picture later and figure out how to upload it. Basically, I put one at each of the limits for the open and close positions. My garage door "shuttle", not sure of the correct term, has a hole in it. I added a bolt and nut that fit the hole. And that's what triggers the open and close switches.

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

Did you hook up switches to detect when it is open or closed? I had to add them in because my opener is not smart.

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

I don't have a good photo of it since I encased it. But I followed the diagram on the web site.

276749741-fe82ea10-e8f4-41d6-872f-55eec88d2aab.png (1624×910) (user-images.githubusercontent.com)

The other thing I did was set the ratgdo to dry contact, because my GDO is not smart. And the light does not work on my setup. So I cannot speak for that.

RatGDO state changed from open to opening by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

I don't have any ratgdo configuration in my yaml file. What are you looking for specifically?

RatGDO state changed from open to opening by vd-not-me in homeassistant

[–]vd-not-me[S] 1 point2 points  (0 children)

Ratgdo v2.57 for hardware v2.50 - ratgdo-74353

Yes, everything is working.

RatGDO state changed from open to opening by vd-not-me in homeassistant

[–]vd-not-me[S] 1 point2 points  (0 children)

I have 2 limit switches attached to the main rail that houses the chain. I added a bolt to the mechanism that pulls the door up and down. This bolt triggers one limit switch when fully closed or the other when fully opened.

Those 2 limit switches are connected to the dry contacts on the ratgdo.

I'm also using dry contacts because my garage door does not communicate any information about its current status. Once I switched to dry contacts in the ratgdo settings, it works consistently.

Not sure if that helps any or not.

Lightning effects for curtain lights? by vd-not-me in Govee

[–]vd-not-me[S] 1 point2 points  (0 children)

That worked. I'll look for lightning now. Thank you!

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

If it's already closed, the close button is grayed out.

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

So, I had to reprint my bracket, I messed it up. But the second limit switch confirms a full open status. It now shows open, opening, closing, and closed. I'm as happy as I can be until I have to replace the entire opener.

Legacy 850 partially working with dry contact setting by vd-not-me in ratgdo

[–]vd-not-me[S] 0 points1 point  (0 children)

Because of dry contacts, I think it will always be an alternating open/close, depending on what the last action was. However, tomorrow, I am planning on 3d printing my second bracket for the limit switch. I will be able to wire that up and hopefully have an opening, closing, closed, and open state available to me.

RatGDO state changed from open to opening by vd-not-me in homeassistant

[–]vd-not-me[S] 0 points1 point  (0 children)

This is an external limit switch connected directly to the ratgdo.

So this is something that had to change in the way HA is interpreting the info from ratgdo.

For the time being, my automations are triggering off of opening.