Giter Site home page Giter Site logo

dahua's People

Contributors

adutchak avatar andrew-d avatar brianegge avatar cchamilt avatar dmr1987 avatar dougiteixeira avatar featherking avatar gelokatil avatar goblinmaks avatar gtbuchanan avatar hawkeye217 avatar idekker avatar ikke-zelf avatar itkfilelor avatar jackdanger avatar joshdev avatar leandroissa avatar mdegat01 avatar neumeier-cloud avatar patriot1889 avatar pedro042 avatar razzo04 avatar redblockmasteur avatar redstone99 avatar rogodra avatar rroller avatar si458 avatar thecode avatar urbim avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

dahua's Issues

VTO door status is unreliable

Door status working fine only for 80% cases.
Sometimes door's are open but sensor status show its closed and the opposite.
Door status always changing with alarm_local, and this one seems to be 100% reliable, maybe there is problem with two messages concurrency or something ?

IPC-HDW4231EM-ASE working but with errors !

2021-07-22 19:58:23 ERROR (MainThread) [custom_components.dahua] TimeoutError fetching information from http://192.168.1.33:80/cgi-bin/configManager.cgi?action=getConfig&name=General -

2021-07-22 19:58:23 ERROR (MainThread) [custom_components.dahua] TimeoutError fetching information from http://192.168.1.33:80/cgi-bin/magicBox.cgi?action=getSoftwareVersion -

2021-07-22 19:58:23 ERROR (MainThread) [custom_components.dahua] TimeoutError fetching information from http://192.168.1.33:80/cgi-bin/magicBox.cgi?action=getSystemInfo -

2021-07-22 19:58:24 WARNING (MainThread) [homeassistant.config_entries] Config entry 'Kamera-Bagdoer' for dahua integration not ready yet; Retrying in background

2021-07-22 19:58:24 WARNING (MainThread) [custom_components.dahua] Failed to sync device state
Traceback (most recent call last):
File "/config/custom_components/dahua/init.py", line 174, in _async_update_data
data.update(response)
TypeError: 'NoneType' object is not iterable

This Camera works.

Hi,

Did not know where to put this info..
Just wanted to let you know that my Dahua IP cam also works.

Thnx for this Dahua integration in Hass.

Camera Type: IPC-HDW4233C-A

Not all functions yet tested, but overall it seems ok and no problems adding it to Hass.

Grtz Duke.

Working Dahua

I can confirm that the Dahua IPC-A26 camera is working.

Add dahua access control

This integration will add dahua access control but not all features are supported. Some events work like the motion detection but face detection won't work. Also, I am looking for DoorStatus event but i couldn't find it.

can you make this integration support all events of the access control my model is ASI7213X.

there is an addon called DahuaVTO2MQTT "https://github.com/elad-bar/DahuaVTO2MQTT" it has the door status event but it can only handle one device and I have multiple devices. if you can use the same method to obtain DoorStatus event that will be great.

Relationship with the internal `amcrest` integration

Home Assistant ships with an amcrest integration, which supports through pyamcrest a lot of Dahua products too. This raises several questions:

  • What advantages does the integration here have over that amcrest integration ?
  • Would it be possible to improve the amcrest integration and/or pyamcrest instead of writing a completely new one, or
  • Would it be possible to get inspiration from that amcrest integration and check for parts of the Dahua API that are better supported by pyamcrest ?
  • Maybe the path forward is to write an equivalent to pyamcrest with the code here if it is better, then modify the internal amcrest integration to use that new code ?
  • Or if you think that your integration should stay separate, explain why in the README so that users can decide whether the internal amcrest or yours is better. Then maybe try to merge your integration into Home Assistant itself.

All available streams created as default

Current setup:
When adding a camera you have to choose what stream you want (main, sub, both).
My camera has 2 sub streams, and the 2nd has other resolution options then the 1st, so I use them both for diffrent scenarios.

2 problems:
A. The 2nd Substream is not available at all (for other cams maybe even 4 streams?).
B. When changing/adding a scenario, I have to remove/re-add the camera to enable or disable (sub)streams.

Possible solution
Allways create all available streams as entity.
Correct me if i'm wrong, but as long you just make a stream available in the config this will not cost any extra overhead as long it is not used in streaming?
For streams that have no activity, those can be created as DISabled entities automaticly when cam is added.
Or...
Show all possible streams as option to user to enable/disable when cam added (as select list/tick boxes), and create entities as disabled when not tagged by user.

Whatever option is choosen, at least create all cam streams as entitie so they can be enabled/disabled with a click of the mouse.
I've seen other Integrations create some disabled entities by default. So should be possible.

And for trigger entities the same request (see issue #38 ), so this whole integration works the same for streams as entity triggers.

My Substream options config screenprint

Regards, The Duke.

Support request for XVR5104C-X device

I would love to see support for XVR5104C-X Dahua device.
I was trying to use on v0.9.13 generic driver but not working.

I will try to read more about Dahua API but it isnt my priority now so I would like to see some advices about it.

Thank you in advance for any type of help.

Support Dahua doorbells

I am using this integration with my doorbell and it seems to work but it's missing the doorbell button binary_sensor. It would be very cool to have that too.

"enable_recording and "disable_recording function

Hi
Very nice project !
I have been using for my Dahua cameras, amcrest intregration for a while but its very bad now, is it possible to implement
enable recording and disable recordning
Thank you in advance.

See link

https://github.com/home-assistant/core/blob/5c5e43afc127fe420f314c01ee2e78d347631adc/homeassistant/components/amcrest/camera.py#L39

i use it like this

  - alias: Camera Record on
    initial_state: 'on'
    trigger:
      - platform: state
        entity_id: alarm_control_panel.ha_alarm
        to: 'armed_away'
      - platform: state
        entity_id: alarm_control_panel.ha_alarm
        to: 'armed_home'
    action:
      - service: amcrest.enable_motion_recording
        data:
         entity_id:
          - camera.carport
          - camera.laundry
          - camera.kitchen
          - camera.living_room
          - camera.family_room
#
  - alias: Camera Record off
    initial_state: 'on'
    trigger:
      - platform: state
        entity_id: alarm_control_panel.ha_alarm
        to: 'disarmed'
    action:
      - service: amcrest.disable_motion_recording
        data:
         entity_id:
          - camera.carport
          - camera.laundry
          - camera.kitchen
          - camera.living_room
          - camera.family_room

NVR support

Is it possible to support NVR? It would be nice to add one device (NVR) and all info about cameras would be detected automatically.

It should also solve a problem when cameras cannot be added because they are connected via NVR and NVR use specific custom IP addresses for them - and the IP addresses are not usable directly.

https support

My VTO2211G have option to turn https on. When it is checked all traffic from https:/IP:80/ is redirected to https://IP:443/.
SSL Certs are created on VTO itself so they are self signed. Please add support for such connection

Request: Service for color/bw/auto

Dahua has issues with remembering the color profile (auto, bw, color) where it reset the settings. I see in the dahua API its an endpoint to change this - could it be implemented?

Cross Region Detection - IVS Intrusion not working

Not getting any responses to Cross Region Detection. I've reinstalled and cross line alarm works but not cross region.

I've added the log entry into configurations.yaml but when checking the side bar logs I don't see any entries, assume I'm looking in the wrong place for the logs.

Cross Region / Intrusion not working.

Version of the custom_component

V0.8.7

Option in Dahua integration for cross region (and more) detection is enabled.

Describe the bug

Intrusion region detection does not trigger in Hass (but it does trigger in camera app/browser when tested).
Event listener in Hass dev "dahua_event_received" does also NOT get triggered.
Is there another "event listener" I need to use?

ps. Cross line, and Motion do trigger OK.

Logs:
Debug ON, Nothing in the logfiles.

Camera intrusion config screenprint

Activated options in Dahua integration screenshot

Add support for IVS

Hi,
wanna u consider to add support for enabling/disabling IVS

def setIVS(ip=None, user=None, passw=None, enabled=True):
  enableRuleResponse = requests.get(
                        'http://'+ip+'/cgi-bin/configManager.cgi',
                        params={
                            'action': 'setConfig',
                            'VideoAnalyseRule[0][1].Enable': str(enabled).lower(),
                            'VideoAnalyseRule[0][2].Enable': str(enabled).lower(),
                            'VideoAnalyseRule[0][3].Enable': str(enabled).lower(),
                            'VideoAnalyseRule[0][4].Enable': str(enabled).lower(),
                            'VideoAnalyseRule[0][5].Enable': str(enabled).lower(),
                            },
                        auth=HTTPDigestAuth(user, passw),
                        )
  print('IPC response was:', enableRuleResponse.status_code)


def dahuaivs_enable(action=None, id=None, enable=True):
    """Enable/Disable IVS on Dahua Camera."""

    setIVS('192.168.12.42', username, password, enable)


Object is not subscriptable

An error appears in the log after the last update.

This error comes from the integration itself.

Logger: homeassistant.config_entries
Source: custom_components/dahua/binary_sensor.py:16
Integration: Dahua (documentation, issues)
First occurred: 20:04:41 (1 occurrences)
Last logged: 20:04:41

Error setting up entry Kamera-ALM for binary_sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 293, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/usr/src/homeassistant/homeassistant/components/binary_sensor/init.py", line 141, in async_setup_entry
return await hass.data[DOMAIN].async_setup_entry(entry)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 149, in async_setup_entry
platform = await async_prepare_setup_platform(
File "/usr/src/homeassistant/homeassistant/setup.py", line 328, in async_prepare_setup_platform
platform = integration.get_platform(domain)
File "/usr/src/homeassistant/homeassistant/loader.py", line 498, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 503, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.8/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1014, in _gcd_import
File "", line 991, in _find_and_load
File "", line 975, in _find_and_load_unlocked
File "", line 671, in _load_unlocked
File "", line 783, in exec_module
File "", line 219, in _call_with_frames_removed
File "/config/custom_components/dahua/binary_sensor.py", line 16, in
NAME_OVERRIDES: dict[str, str] = {
TypeError: 'type' object is not subscriptable

VTO2202F remote unlocking

I have a VTO2202F doorbell which have remote unlocking, can you add this as a binary sensor? The following is what I can find with the work "lock", I am not sure if this is the debug line you are looking for. If you need more debugging, let me know. Cheers

2021-06-22 03:11:07 DEBUG (Thread-43) [custom_components.dahua] Data received: {'id': 4, 'params': {'table': [{'AccessProtocol': 'Local', 'CloseAlwaysTime': 1, 'EntranceLockChannel': 0, 'OpenAlwaysTime': 0, 'State': 'Normal', 'TimeSchedule': [{'TimeSection': '00:00-23:59'}], 'UnlockHoldInterval': 2, 'UnlockReloadInterval': 15}, {'AccessProtocol': 'Dahua', 'CloseAlwaysTime': 1, 'EntranceLockChannel': 0, 'OpenAlwaysTime': 0, 'ProtocolType': 0, 'State': 'Normal', 'TimeSchedule': [{'TimeSection': '00:00-23:59'}], 'UnlockHoldInterval': 2, 'UnlockReloadInterval': 15}, {'AccessProtocol': 'Remote', 'Address': '0.0.0.0', 'CloseAlwaysTime': 1, 'EntranceLockChannel': 0, 'OpenAlwaysTime': 0, 'Port': 10001, 'State': 'Normal', 'TimeSchedule': [{'TimeSection': '00:00-23:59'}], 'UnlockHoldInterval': 2, 'UnlockReloadInterval': 15}]}, 'result': True, 'session': 1687891641}

Add support for PTZ

Hello and thank you for your work with this costume component !!

Just to share with you that I have tested successfully this models:

IPC-HFW1230S
https://s.click.aliexpress.com/e/_AaZ6Mt
IMOU IPC-K22A / Cube PoE-322A
https://s.click.aliexpress.com/e/_AotOJr
IMOU IPC-A26Z / Ranger Pro Z
https://s.click.aliexpress.com/e/_9xkY6V

And i also have a request to improve this, can you please add the PTZ commands to the models that support this feature please like this one Please if possible at right a saved position and a left the commands to move the cameras

image

Thank you and best regards

Issue with channel +1 in camera.py

Was reported a number of times in different threads.
camera.py has a "channel + 1" in a number of places, which causes issues when adding channel from NVR

Not loading with DVR because devicetype is empty.

Thanks for the efforts creating this component. I'm trying to use the component for a DVR (XVR5108C-X). The integration is not loading correctly as shown in the debug logs.

2021-07-21 19:01:02 INFO (MainThread) [custom_components.dahua] Authenticated with the RPC2 API
2021-07-21 19:01:05 WARNING (MainThread) [custom_components.dahua] Failed to sync device state
Traceback (most recent call last):
File "/config/custom_components/dahua/__init__.py", line 197, in _async_update_data
is_doorbell = self.is_doorbell()
File "/config/custom_components/dahua/__init__.py", line 411, in is_doorbell
m = self.model.upper()
AttributeError: 'NoneType' object has no attribute 'upper'
2021-07-21 19:01:05 DEBUG (MainThread) [custom_components.dahua] Finished fetching dahua data in 0.186 seconds

The problem is that the output of "/cgi-bin/magicBox.cgi?action=getSystemInfo" doesn't contain a deviceType as stated on line 73 in client.py.
This is the output.

processor=ST7108
serialNumber=...
updateSerial=XVR5108C-X

Maybe it's an idea to retrieve the device type from updateSerial if the output of the Dahua api doesn't contain a deviceType (like you did when the deviceType is IP Camera) or call "/cgi-bin/magicBox.cgi?action=getDeviceType" ?

output of /cgi-bin/magicBox.cgi?action=getDeviceType is
type=DH-XVR5108C-X

Thanks in advance!

CrossRegionDetection = Intrusion

Would be good to add the additional IVS feature: CrossRegionDetection = Intrusion

This allows more functionality for IVS in addition to the tripwire feture

Error "object has no attribute 'async_config_entry_first_refresh'"

Just installed the component using HACS, configured one camera and found no entities or devices were created.
The following error was in the HA log:

Logger: homeassistant.config_entries
Source: custom_components/dahua/init.py:69
First occurred: 10:42:21 AM (1 occurrences)
Last logged: 10:42:21 AM

Error setting up entry DahuaRearDeckCamera for dahua
Traceback (most recent call last):
File "/home/homeassistant/.local/lib/python3.7/site-packages/homeassistant/config_entries.py", line 236, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/home/homeassistant/.homeassistant/custom_components/dahua/init.py", line 69, in async_setup_entry
await coordinator.async_config_entry_first_refresh()
AttributeError: 'DahuaDataUpdateCoordinator' object has no attribute 'async_config_entry_first_refresh'

I am using Home Assistant version: 2021.1.4, frontend version: 20201229.1

Last update not working. Missing Camera device.

v0.8.1. was working perfect.

Updated to 0.8.3.
First Reboot>> Error in log: Camera not found.
2nd Reboot>> No error, but also NO camera device!

Removed Camera, and RE-added camera.
Camera device still missing.

Back to v0.8.1. >> All working prefectly.

Debug log

2021-06-26 09:26:33 DEBUG (Thread-3) [custom_components.dahua] Starting DahuaEventThread
2021-06-26 09:26:33 DEBUG (MainThread) [custom_components.dahua] Finished fetching dahua data in 2.410 seconds
2021-06-26 09:27:03 DEBUG (Thread-18) [custom_components.dahua] Starting DahuaEventThread
2021-06-26 09:27:04 DEBUG (MainThread) [custom_components.dahua] Finished fetching dahua data in 1.756 seconds
2021-06-26 09:27:15 DEBUG (Thread-20) [custom_components.dahua] Starting DahuaEventThread
2021-06-26 09:27:15 DEBUG (MainThread) [custom_components.dahua] Finished fetching dahua data in 1.775 seconds
2021-06-26 09:27:28 ERROR (MainThread) [homeassistant.components.camera] Error requesting stream: Camera not found
2021-06-26 09:27:36 DEBUG (Thread-23) [custom_components.dahua] Starting DahuaEventThread

Also text at integration: Retrying setup
Screenprint Integration Screen

Missing binary sensor - button pressed

I have VTO 2211G-P everything works good but I dont see binary sensor which reports when butt is pressed. In configuration I have checked option "binary sensor". Do you know what is the problem?

Create all entities by default, but disable those not in use.

problem:
Maybe I'm wrong, but the only way to enable a new entitie like Crosswire detection now is to remove and re-add the camera?

suggestion:
Why not create all available entities by default but Disable those the user does not want when cam is installed.
Then later we can just Enable or Disable the entities if we want to use them.

same for streams. see request #36

If #36 is also a good option to create, then this integration might even be easier to maintain or debug (no more different entities created depending the cam type, but allways the same entity list is created, just disabled what not needed).

Failed to sync device state

Version of the custom_component

Configuration

Add your logs here.

Describe the bug

After installing the integration I get the following error logs
I've get 3 different ones which I've labelled them as Log 1, Log 2 and Log 3

Anyone able to help out as to why I'm getting this message.

Home assistant version :2021.6.3
Dahua integration version : 0.9.1

Debug log


Add your logs here.

Log 1
This error originated from a custom integration.

Logger: custom_components.dahua
Source: custom_components/dahua/client.py:551
Integration: Dahua (documentation, issues)
First occurred: 7:10:03 AM (96 occurrences)
Last logged: 9:16:14 AM

Failed to sync device state
Traceback (most recent call last):
  File "/config/custom_components/dahua/__init__.py", line 239, in _async_update_data
    results = await asyncio.gather(*coros)
  File "/config/custom_components/dahua/client.py", line 168, in async_common_config
    return await self.get(url)
  File "/config/custom_components/dahua/client.py", line 565, in get
    raise exception
  File "/config/custom_components/dahua/client.py", line 551, in get
    response.raise_for_status()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 1000, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request', url=URL('http://10.0.0.100:80/cgi-bin/configManager.cgi?action=getConfig&name=MotionDetect&action=getConfig&name=Lighting%5B1%5D%5B0%5D')


Log 2 
This error originated from a custom integration.

Logger: custom_components.dahua
Source: custom_components/dahua/__init__.py:210
Integration: Dahua (documentation, issues)
First occurred: 7:10:03 AM (96 occurrences)
Last logged: 9:16:14 AM

Cam does not support profile mode. Will use mode 0

Log 3
Logger: homeassistant.config_entries
Source: config_entries.py:324
First occurred: 7:10:03 AM (2 occurrences)
Last logged: 7:12:45 AM

Config entry 'NVR' for dahua integration not ready yet; Retrying in background

Readme needs change for the Stream component

Just a small update:

In the readme you state stream is needed in the config.yaml
But according to this url (I checked and can confirm this): Hass Stream Component

The stream integration is automatically loaded by default_config and enabled by the camera platforms that support it. If default_config is used, no separate configuration.yaml entry is necessary.

ps. Readme FFMpeg part is correct. FFmpeg is NOT included (yet?), and needs to be added to the config.yaml

Regards, The Duke.

Add support for reconfiguration

After a cam is added, there's no support to update the device details: username, password, IP, events, etc. Add in an update flow.

IVS event not triggering Home Assistant event.

I have a fresh install of HA (2021.6.4) with the latest Dahua integration installed.
IVS is set up on two cameras (different models) and the CrosslineEvent is ticked for both.
I can see the events occurring using a cut down version of the original Johnny le Trois python script that subscribes to the camera's events.
However, the events do not appear in HA.
I can listen to "dahua" events in HA using the Developer Tools, and no triggers are reported.
There are no errors or warnings reported by HA in the home-assistant.log..

Event Binary Sensor

I have a IPC-T5442T-ZE setup with 2 IVS rules, the first is a general motion detector and the second one is a tripwire which I am hoping to use this for automation. Under my integration, my device only shows 5 entities (Cam Disarming, Cam Infrared, Cam Main, Cam Motion Alarm and Cam Motion Detection) and I do not have separate event binary for CrossLineDetection or FaceDetection, even though I have this enabled on the camera and integration. I am using the latest version installed via HACS.

Following error in my logs

Hello, i have the following error in my logs? What is it? And what can i do about it?
I'm using version 0.9.10 of the Dahua intergration true hacs.
And my version from Home Assistant is 2021.7.4

`Logger: custom_components.dahua
Source: custom_components/dahua/digest.py:46
Integration: Dahua (documentation, issues)
First occurred: 27 juli 2021 23:14:22 (1273 occurrences)
Last logged: 11:57:23

Failed to sync device state
Traceback (most recent call last):
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 969, in _wrap_create_connection
return await self._loop.create_connection(*args, **kwargs) # type: ignore # noqa
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1056, in create_connection
raise exceptions[0]
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 1041, in create_connection
sock = await self._connect_sock(
File "/usr/local/lib/python3.9/asyncio/base_events.py", line 955, in _connect_sock
await self.sock_connect(sock, address)
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 502, in sock_connect
return await fut
File "/usr/local/lib/python3.9/asyncio/selector_events.py", line 537, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.1.114', 80)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/config/custom_components/dahua/init.py", line 246, in _async_update_data
results = await asyncio.gather(*coros)
File "/config/custom_components/dahua/client.py", line 181, in async_common_config
return await self.get(url)
File "/config/custom_components/dahua/client.py", line 585, in get
raise exception
File "/config/custom_components/dahua/client.py", line 570, in get
response = await auth.request("GET", url)
File "/config/custom_components/dahua/digest.py", line 46, in request
response = await self.session.request(method, url, headers=headers, **kwargs)
File "/usr/local/lib/python3.9/site-packages/aiohttp/client.py", line 520, in _request
conn = await self._connector.connect(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 535, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 892, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1051, in _create_direct_connection
raise last_exc
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 1020, in _create_direct_connection
transp, proto = await self._wrap_create_connection(
File "/usr/local/lib/python3.9/site-packages/aiohttp/connector.py", line 975, in _wrap_create_connection
raise client_error(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host 192.168.1.114:80 ssl:default [Connect call failed ('192.168.1.114', 80)]
`

Support for IPC-K42 (Imou Cube 4MP)

Hi,

Is there support for the Dahua IPC-K42 (Imou Cube 4MP)?

I installed the custom component manually, but I don't get any devices or entities visible within Home Assistant (and yes rebooted multiple times).

Do I need the RPC wrapper? Or does this component not support this camera?

Kind regards,
Barry

Light Illuminator not working when profile is set as "night"

Switching on the LED light via HA works fine when the profile is the day but not when the profile is at night.

Log here: 2021-06-23 15:23:50 DEBUG (MainThread) [custom_components.dahua] Turning light on: http://192.168.10.20:80/cgi-bin/configManager.cgi?action=setConfig&Lighting_V2[0][0][0].Mode=Manual&Lighting_V2[0][0][0].MiddleLight[0].Light=20

It does work with the following URL:

http://192.168.10.20/cgi-bin/configManager.cgi?action=setConfig&Lighting[0][2].Mode=Manual

So night profile needs to be stated in the URL as [2] Any idea if this can be amended as it's great to control the brightness via HA.

thanks

DH-SD1A203T-GN audio event

The DH-SD1A203T-GN camera has an onboard mic and can generate "audio detection" event.

It would be nice to have a binary sensor representing this event. As an additional note, the event already get fired in Onvif stream.

If you need any further info, I'll be glad to help. Thanks.

Error in log

This error occurs about 3 times a day, but I do not know if it is important or does not mean anything.
The IPC-A26 camera operates normally
I modified the IP address in the protocol so that it is not readable.

This error comes from the integration itself

Logger: custom_components.dahua
Source: custom_components/dahua/client.py:461
Integration: Dahua (documentation, issues)
First occurred: 17:04:15 (1 occurrences)
Last logged: 17:04:15

TimeoutError fetching information from http://1xx.xxx.xx.62:80/cgi-bin/configManager.cgi?action=getConfig&name=MotionDetect&action=getConfig&name=Lighting[0][0] -

Support for Imou IPC-F22 Bullet 2C

Hi. Any chance of support for this camera? I don't think it has http support on port 80.

It can be configured by the Dahau Windows Config tool. This also shows some cgi commands

Amcrest AD410 is supported

Version of the custom_component

0.9.2

Configuration

n/a

Describe the bug

I wanted to report that the Amcrest AD410 video doorbell appears to be supported with this integration. Some brief notes in case anyone else has this:

  • Pressing the doorbell appears to fire the alarm_local binary sensor - e.g. binary_sensor.front_doorbell_alarm_local here.
  • The camera shows up in Home Assistant and works fine, including both SD/HD streams and sound.
  • I haven't figured out how to get the "human detection" working yet; binary_sensor.front_doorbell_smart_motion_human doesn't appear to fire, but I'll play with it a bit more.

I'm happy to do any debugging/etc. if any of the maintainers want - but I figured I'd start with the fact that it works ๐ŸŽ‰ Thanks to everyone that's contributed!

Debug log

n/a

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.