roleoroleo / yi-hack_ha_integration

Home Assistant custom integration for Yi cameras: yi-hack-MStar, yi-hack-Allwinner, yi-hack-Allwinner-v2, yi-hack-v5 and sonoff-hack
GNU General Public License v3.0
205 stars 32 forks source link

Cam device and entities disabled in Home Assistant #127

Closed Davidd012 closed 2 months ago

Davidd012 commented 1 year ago

Hi there!

First of all thanks for your work.

I hacked my Yi camera with MStar (Last release), and I copied the custom components (0.4.5) folder in the Home Assistant config folder. I enabled on the camera the MQTT service and discovery, RTSP etc. All good with that.

In the Yi-hack addon in Home Assistant I have mostly of the things disabled, I only have access to the camera's media. The camera device is disabled, and all the other entities too.

I'm new with Home Assistant and not sure if I'm forgetting something else (additional code in config.yaml/go2rtc.yaml, an extra add-on like webrtc, or any other step process).

I saw a video of other guy, and he did the same than me, without any extra step and he has access to the camera media stream.

Any suggestion is welcome!

Untitled

roleoroleo commented 1 year ago

If you are using this integration, MQTT service discovery can be disabled. Did you enable MQTT integration in HA?

maobuz commented 11 months ago

i have the same problem, after last update the camera on yi-hack do not work Camera firmware 0.5.2 Home Assistant 2023.7.2 Supervisor 2023.07.1 Operating System 10.3

I tried to configure again but nothing image

on mttq do not find the camera

Help Me !

roleoroleo commented 11 months ago

Please, check the log and report errors, if present.

maobuz commented 11 months ago

Please, check the log and report errors, if present.

Questo errore ha avuto origine da un'integrazione personalizzata.

Logger: homeassistant.config_entries Source: custom_components/yi_hack/init.py:164 Integration: Yi Cam con yi-hack (documentation, issues) First occurred: 00:15:23 (1 occurrences) Last logged: 00:15:23

Error unloading entry yi_hack_m_68e502 for yi_hack Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/config_entries.py", line 546, in async_unload result = await component.async_unload_entry(hass, self) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/config/custom_components/yi_hack/init.py", line 164, in async_unload_entry hass.data[DOMAIN].pop(entry.entry_id) KeyError: '4b659c83240d2faa69a5693556782ee5'

Logger: homeassistant.components.stream.stream.camera.yi_hack_m_68e502_cam Source: components/stream/init.py:434 Integration: Stream (documentation, issues) First occurred: 22:24:45 (3 occurrences) Last logged: 22:26:47

Error from stream worker: Error demuxing stream: [Errno 110] Operation timed out: 'rtsp://yicamera:123ewq123@192.168.178.26/ch0_0.h264' Error from stream worker: Error demuxing stream: [Errno 110] Operation timed out: 'rtsp://yicamera:123ewq123@192.168.178.26/ch0_0.h264'; last error log: [NULL] missing picture in access unit with size 52

roleoroleo commented 11 months ago

There are no "big" problems in your log. The 1st error (KeyError) happens when you remove the cam, so it's not related to the installation/running phase. Other errors are related to the rtsp stream.

Is mqtt broker properly configured? Check if you disable MQTT Advertise; if you use this integration, mqtt advertise is not required. http://IP_OF_YOUR_CAM/?page=mqtt_adv

maobuz commented 11 months ago

There are no "big" problems in your log. The 1st error (KeyError) happens when you remove the cam, so it's not related to the installation/running phase. Other errors are related to the rtsp stream.

Is mqtt broker properly configured? Check if you disable MQTT Advertise; if you use this integration, mqtt advertise is not required. http://IP_OF_YOUR_CAM/?page=mqtt_adv

ok , i deleted all and reset a camera setting to default and reboot a home assistant, after reboot i reinstalled all and now

image

it's working !

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.