go2RTC error With Feeder Video

[BenJewell]

System Health details

System Information

version	core-2026.4.3
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.77-haos
arch	x86_64
timezone	America/New_York
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	4995
Installed Version	2.0.5
Stage	running
Available Repositories	2941
Downloaded Repositories	27

Home Assistant Supervisor

host_os	Home Assistant OS 17.2
update_channel	stable
supervisor_version	supervisor-2026.04.0
agent_version	1.8.1
docker_version	29.3.1
disk_total	30.8 GB
disk_used	14.9 GB
nameservers	10.0.2.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	vmware
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Terminal & SSH (10.0.2), Let's Encrypt (6.3.1), NGINX Home Assistant SSL proxy (4.1.0), File editor (6.0.0), Samba share (12.6.1), Advanced SSH & Web Terminal (23.0.3), Node-RED (21.0.5), OneDrive Backup (2.3.10), Mosquitto broker (7.0.1), Speedtest (1.6.2), Matter Server (8.4.0), Zigbee2MQTT (2.9.2-1), Home Assistant Version Control (1.2.0), Home Assistant Editor (1.1.0)

Dashboards

dashboards	5
resources	12
views	39
mode	storage

Network Configuration

adapters	lo (disabled), enp2s1 (enabled, default, auto), docker0 (disabled), hassio (disabled), vetha7f13c9 (disabled), veth6f8e35b (disabled), veth3297113 (disabled), veth3cfe5b0 (disabled), veth1deddd8 (disabled), veth880013b (disabled), veth36f56d6 (disabled), vethec50cd8 (disabled), veth8562bda (disabled), veth15fcf57 (disabled), vethe92dd20 (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp2s1 (10.0.1.23/8), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), vetha7f13c9 (), veth6f8e35b (), veth3297113 (), veth3cfe5b0 (), veth1deddd8 (), veth880013b (), veth36f56d6 (), vethec50cd8 (), veth8562bda (), veth15fcf57 (), vethe92dd20 ()
ipv6_addresses	lo (::1/128), enp2s1 (fe80::f7be:af2:47d7:a0e9/64), docker0 (fe80::4493:f8ff:fe82:c90e/64), hassio (fd0c:ac1e:2100::1/48, fe80::d0ce:32ff:fe60:22cb/64), vetha7f13c9 (fe80::7c58:e4ff:fef8:6614/64), veth6f8e35b (fe80::8cf9:dcff:fe7b:930e/64), veth3297113 (fe80::7401:3cff:fec6:10c5/64), veth3cfe5b0 (fe80::e8ef:7eff:fe8b:aad2/64), veth1deddd8 (fe80::881:b8ff:fe23:626a/64), veth880013b (fe80::e4b5:f4ff:fec5:fc82/64), veth36f56d6 (fe80::9c18:49ff:fed3:da99/64), vethec50cd8 (fe80::1869:59ff:fec0:cf/64), veth8562bda (fe80::60a6:15ff:fed9:580c/64), veth15fcf57 (fe80::c51:b8ff:fedf:e455/64), vethe92dd20 (fe80::187c:caff:fe48:282a/64)
announce_addresses	10.0.1.23, fe80::f7be:af2:47d7:a0e9

Recorder

oldest_recorder_run	April 4, 2026 at 6:03 AM
current_recorder_run	April 19, 2026 at 6:04 PM
estimated_db_size	483.94 MiB
database_engine	sqlite
database_version	3.49.2

Integration version ?

1.25.0

In which region is your Petkit application registered?

United States

Device type

Feeder

Checklist

• I have enabled debug logging for my installation.
• This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
• This issue is not a duplicate issue of any previous issues..

Describe the issue

I am having a really hard time getting the new live video feature working. I have Home Assistant OS with the default config loaded. This seems like it should load something called go2rtc that this integration requires. But I get this error when I click on the camera entity provided by the integration.

"Failed to start WebRTC stream: No shared go2rtc instance is configured for this camera"

After much debugging, I added this to configuration.yaml:

go2rtc:
  debug_ui: true
  username: username
  password: password

Now I get a static picture that never updates when I try to view the camera from the dashboard. I can open the debug UI, but that never loads the stream.

If I open the PetKit app, it works there, but it does not "wake up" the stream in Home Assistant. I even updated the firmware on the feeder.

Reproduction steps

1. Setup Petkit device (Yumshare Solo With Camera (D4H)) with integration.
2. Verify that most entities work.
3. Attempt to open the camera entity.

Debug logs

Taken with NO rtc configuration in configuration.yaml.

https://drive.google.com/file/d/1m1OTkurgTMdlgDtV98UKZyLj5aAlvR_Y/view?usp=sharing

Diagnostics dump

petkit-01K0MHQWST2VPG5DQBP8EDJS66-Feedy-19caab664e5dc6e858bebdda3e388517(1).json

[Jezza34000]

Hi @rankjie
Do you have an idea what's wrong ?

[rankjie]

Apologize if I’m off base, as the debug log is massive(almost 30MB!) so I didn’t review it thoroughly.

I noticed that the diagnostics indicate you have default_config_disabler installed, and I’m guessing that it might be preventing HA’s managed go2rtc from starting.

Potential solutions assuming that's the issue:

1. Disable or uninstall default_config_disabler.
2. Or, install the official go2rtc add-on and specify go2rtc: { url: … } to it, then try again.

[BenJewell]

Apologize if I’m off base, as the debug log is massive(almost 30MB!) so I didn’t review it thoroughly.

I noticed that the diagnostics indicate you have default_config_disabler installed, and I’m guessing that it might be preventing HA’s managed go2rtc from starting.

Potential solutions assuming that's the issue:

1. Disable or uninstall `default_config_disabler`.

2. Or, install the official go2rtc add-on and specify `go2rtc: { url: … }` to it, then try again.

Thanks for looking into this. Sorry I'm not sure how to limit the debug log to just the relevant information. Let me know if you want me to redo it with certain parameters.

I do use default config disabler but go2rtc is not one of the things that's disabled. So I don't think that's the issue but I will disable it and test again this weekend just to make sure.

[BenJewell]

Any updates?