Great update!, thanks, let’s see if changing the night mode can turn on the light from Home Assistant but it seems that it needs a lot of darkness.
I have already written several times suggestions for them to do a firmware update to be able to turn on the light whenever we want.
I’ve made a switch with a input booolean helper to turn the light on when it’s in FullColor mode and off when it’s in Intelligent. It works for me with a 2/3 second delay but as I said it needs a lot of darkness. Thanks for the latest update again.
I can’t get the "Associated Device Alarm" switch to work, I have tried all the options to activate or deactivate from the app and it doesn’t work for me from HA. I can only turn on the siren in the app from the main menu icons with a warning that the neighbors can hear it. Can you hear the siren when this switch is activated? Or maybe have to wait several times?
Thanks @user2684, very well done.
Now i have also a Versa and a Ranger 2c.
I will keep the Versa, but I will probably give back the other because I don’t like it very much.
The new switches seems to work very well.
In the new cams I don’t have an SD card installed, and the left storage sensor tell me 100%. In the one where I have the SD card, the % is ok.
It would be nice also to have a switch to reboot the cam, if it’s available in the capabilities.
I don’t think I will try the notifications because I don’t have any port exposed to internet and I’m not going to open them. So sorry for that!
@janinho if I understand correctly the switches from the latest version worked for you but changing the night vision mode per-se, even if with the light on, has an impact on the result since too dark, correct? I was afraid this could have happened…but I guess nothing we can do on the integration side. Associated Device Alarm in my understanding should “arm” the siren so that if there is a motion, the siren sounds. At least this it what I could see in the Versa. It is the same as turning the switch on in the app. Are you experiencing a different behaviour? Or are you looking also for a way to activate the siren, regardless of the motion?
@woody4165 thanks for the feedback. I’ll fix the storage used sensor reporting wrong values when a D card is not present. Regarding the rebook switch, this could be an easy addition, will be next in my list.
Yes, the light works correctly for me when it is completely dark. I have simply created a switch with a helper, when it is off its selected the intelligent mode and when it is on its selected the FullColor mode.
I thought that there would be the possibility of turning on the siren without movement sensor, that was it. Thanks for the reply
@janinho got it for the siren, will have a look at it, if can be done through the app, should be possible also through the API
Anybody had any luck with push notifications? With @snatch7 we found HA is not receiving the messages somehow. Troubleshooting is still in progress but if somebody else had it working, please let us know. Thanks
Hello @snatch7@user2684 I’m a newbie and I’m just starting to learn all the things about HASS. I have imou life camera IPC-S42F model and I’m wondering if is possible to receive a mobile notification with snapshot when motion detected? Also I’m having problems with onvif setup - which username & password should I enter - the one I have for Imou life app? Thank you in advance. Regards…
Just throwing my 2c in here.
I’m actually unable to add the vacuum to the open.imoulife platform (so, those cli commands don’t work at all).
Adding the vacuum to the app only requires the vacuum S/N, and the vacuum be in pairing mode (safety code is left blank).
The open.imoulife platform requires the safety code when adding a new device, so fails with the following error:
服务异常 (translates to Service exception)
I think the imoulife platform hasn’t been updated to suit the vacuum yet. This is understandable with the way the app itself is built.
The app talks to, and authenticates with, a different server when communicating with the vacuum robot (app-v2.easy4ipcloud.com & app-or-v2.easy4ipcloud.com vs openapi.easy4ip.com/openapi).
Anyway, I’m happy to help in any way I can… I’m just hacking away with the apk and the IMOU private API until I hit gold. Stuck on a HmacSHA256 sig that’s not matching during auth…
#UPDATE
Just tried the openapi to try and manually bind the device to my appid - no luck. I just get the following error: {"result":{"msg":"Device does not exist","code":"DV1002"},"id":"48"}
@janez33 push notifications generally speaking is what we are currently working on. It is available within the integration right now but we are experiencing some issues due to the way the Imou APIs handle the communication. So stay tuned. Personally I’m still using Imou Life app for this since Home Assistant would not add much value there in replicating the same functionality.
For Onvif, you must use admin as username and the password which is printed on the device to make it working. Thanks
@tubes41 thanks a lot for the reverse engineering exercise I was afraid of a similar situation, that is Imou Life app using a completely different set of APIs for interacting with the vacuum cleaner as it looks like from your analysis. I don’t see unfortunately any documentation regarding this additional endpoint…
Have you tried by chance other integrations in HA supporting Dahua’s devices? As far as I’ve understood there is something in common between Imou and Dahua and maybe vacuum cleaners can be connected through them. Just guessing of course.
Hi @user2684, nice work with the integration I’ve always wanted to integrate my Dahua/Imou DB11 doorbell into HA and now I finally can, almost. I am successfully pulling the switches and sensors but I am having trouble getting webhook events to trigger. I receive the push notification on my phone but the webhook is never triggered in HA. I can test the webhook using Postman and that works fine. I enabled logging but webhook events do not appear.
My HA instance sits behind a reverse proxy and therefore I am using the Callback Full URL but it’s not working for me. I wonder whether it’s a formatting issue. An example would be helpful in the Wiki. Here is the format that I am using. It works in Postman.
https://<domainname>/api/webhook/<webhookID>
How are the webhooks sent from openapi.easy4ip.com. I gather you are passing the Callback Full URL? I appreciate some help to troubleshoot.
@tubes41 The Dahau/Imou safety code is the admin password for the device. It is either printed in plain text on the physical device or a QR code is used. I’ve had some success adding old Dahua cameras that use the legacy P2P protocol which were migrated to this new platform by using the Imou Life Windows application to add the devices. Try adding your vacuum using this method.
I must be doing something wrong but I can’t seem to understand how I could trigger on motion detection on my IMOU camera. I’ve been reading on ONVIF camera component being able to trigger on motion detection but my IMOU REX doesn’t present a motion entity binary sensor.
I’ve been reading on the topic start motion detection would be a part of this integration. How do I use this? Obviously the motion detection switch in this integration is turned on.
@galaxy_explorer you are likely not doing anything wrong, there is something which is preventing HA to accept the webhook (provided it gets to the HA which is something still under investigation).
I’ll try to summarize all the tests done by various members here in a github issue so to have all of us a clear picture of what is happening and do more investigations over the weekend. I’ll keep you posted.
@mhoogenbosch this integration is aimed mostly (at least at this time) to control the switches of the camera, like you do in the Imou Life app, manually or through automations. Receiving motion detections events is something which is also supposed to work but not fully working right now. Keep on eye on this thread for updates.
Regarding Onvif motion detection events, I’ve noticed they are different than those coming from the Imou Life app. Especially if you use Human Detection or other things, those filters are ignored, Onvif reports a motion at EVERY movement. The alarms we are instead trying to get from Imou through this integration, should instead take into account the way you have configured motion detection parameters, which should make more sense. Again, keep on eye here, capturing alarms through the integration is number 1 priority right now.
Apart from this, I’ve just released 1.0.4. No big news apart from the following:
The integration has been added to the default repository of HACS, so no more the need to add it through a custom repository, you should now find right in the main HACS directory
A good amount of updates in this 1.0.5 version just released:
Added a switch for turning the Siren on/off for those devices supporting it. This requires your automation to turn the switch off after a while since apparently there is no way to turn it off automatically, even through Imou Life app (can anybody confirm?)
Added buttons for restarting the device and manually refreshing device data in Home Assistant, as requested by a few of you here
Added a sensor with the callback url set for push notifications so to see which url has been set
Deprecated “Callback Webhook ID” option for push notifications, use “Callback URL” instead. Having two options was creating confusion, as some of you correctly reported here. This is not a breaking change per-se since once set the URL is not changing, however, if you were previously using webhook id and you need to update the URL, you have to set the full callback url now
Reviewed the labels of some of the switches to make them more self-explanatory
Fixed “storage left” sensor which is now reporting “unknown” when a SD card is not present
The siren works perfectly! Do you know that in HA there is an option that instead of switch.siren there is siren.imou_versa?
In the versa camera they have updated another firmware version but it is still not possible to turn on the light at our whim. I have written a complaint or suggestion again
@galaxy_explorer, unfortunately, it’s not that easy. The IMOU app uses a blank safety code when adding a vacuum cleaner via the new endpoint.
Digging a bit deeper, the vacuum may be a OEM Tuya vacuum, but with customised firmware and app (which is then merged into the imou app).
This would explain the blank safety code, as the Tuya devices don’t have one, only a S/N, an internet connection, and a direct wifi/bluetooth connection.
I’ve always wanted to integrate my Dahua/Imou DB11 doorbell into HA and now I finally can, almost. I am successfully pulling the switches and sensors but I am having trouble getting webhook events to trigger. I receive the push notification on my phone but the webhook is never triggered in HA. I can test the webhook using Postman and that works fine. I enabled logging but webhook events do not appear.