-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cell Go support? #55
Comments
Hi, can you please both diagnostic and debug logs so to have a better look at it? Might be this model does not expose certain capabilities. Thanks! |
Thanks for your answer, sorry to ask but do you have a link about which exact information you need? I am pretty new to HA, not sure how/where to get the requested diag/debug logs. |
Sure no problem, have a look at this: https://github.com/user2684/imou_life#troubleshooting |
Thanks for the info. Device Diagnostic data: { HA Logs Cette erreur provient d'une intégration personnalisée Logger: aiohttp.server Error handling request Logger: homeassistant.components.websocket_api.http.connection [547178262352] Error handling message: Unknown error (unknown_error) eric from fe80::2bb4:70f7:2921:9905 (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36) Thanks for your support & feedback! |
Hello And thank you I also have the same issue with the new Imou Cell Go it´s added in to Home Assistant, but is not showing the image stream and also some of sensors and features are unavailable Is there any chance to get this work? Thank you for your support |
Please let me know if you need any further information or logs in order to try support this device Thank you |
Thanks for the logs. From what I can see, the device is recognized as a "dormant" device correctly but the method we found in #36 by calling the closeDormant function to wake it up, it doesn't work here since not supported (invalid parameter). Unfortunately Imou is not keeping up to date the API specs at https://open.imoulife.com/book/en/start.html and there are no evidence on how to interact with those devices, how to wake them up etc. There is for sure a way because this is what the Imou Life app does but it is not easy to guess like we did in #36 since it is not publicly documented. I'll keep this open and in case I can get such a device for more detailed tests I'll dig into. Meanwhile if anybody identifies the right api to interact with those devices, please let me know. |
Ok no problem, thanks a lot for your help and for your great work with this imou integration |
Probably if anyone have access to the new model Imou Cell 2 is a good test also in order to check this parameter |
agree, it is really try and error and the complexity is also that since looks like Imou is updating their API but not their documentation, sometimes is really difficult to guess what to call. maybe one way could be to intercept in the network the calls issued by the camera but the SSL certificate could prevent this. Another could be to ask the Imou support but I never got decent answers from them. |
I just got a Cell Go camera, which I thought I could manage with Home Assistant through this integration. Instead, this particular model seems to have a lot of problems which, from what I read, don't seem to have the possibility to be solved easily or quickly. Please let me know if I can be of any help, otherwise I believe I might be forced to return the camera. Thank you. |
I also have one of these cameras and would gladly do whatever I can to assist in finding a way through its limitations. Ask away :) |
I've set up Postman and followed some directions as outlined in request #36, so far with some success. |
Great, thank you. Unfortunately without having the model to test it is very difficult for me to implement something when blind :-) |
Here's what I am doing with Postman, tried some different functions: get camera status through the "deviceOnline" call with these parameters I get the onLine=4, if I got it correctly, means sleeping, right? Then I call the wakeUpDevice function with the following parameters { and I get in response {"result":{"msg":"Operation is successful.","code":"0"},"id":"39"} Right after calling the wakeup function, if I send a deviceOnline call I get {"result":{"msg":"Operation is successful.","code":"0","data":{"productId":"XXXXXXX","channels":[{"channelId":"0","onLine":"1"}],"deviceId":"XXXXXXXXXXXXX","onLine":"1"}},"id":"21"} the online=1 means online, correct? Please let me know if you need me to do further testing. Thank you. |
Yes, online should mean the device is actually online. Just check maybe that after this message you can get a snapshot, move the switches etc. so to be sure the device is really back online. Thanks! |
Some further progress, even though I confess I haven't read the documentation thoroughly and I may be doing things not the proper way. |
This is the log HA produces about the imou_life custom component: 2023-12-04 16:36:55.187 ERROR (MainThread) [custom_components.imou_life] APIError: OP1003: Invalid parameter (incorrect or null), please modify parameter |
Good news! |
Great News! Can you please let us know if you are able to see the live stream of this camera model over the HA? If Yes can you please give us more details how to perform this? Thank you |
Yes, I can see the live stream in HA but it's kind of hit or miss, sometimes it works, sometimes not. I am also verifying the battery drain: it seems that after connecting the camera in HA the battery has a much higher discharge rate. |
This is great even if for some times works or not ... Yes its expected that the battery drain more faster once the stream is always active Can you please give more information about how to achieve this integration in HA? Thank you |
Excellent job @tango13 !! Just to fully understand the process here: the device is correctly identified as a "dormant" but was not correctly woke up by the integration. If you instead manually call async_api_setDeviceCameraStatus with the channel id, then the device wakes up and you can interact with it, correct? Battery drain is normal and the fact that the imou service with these devices is not always perfect is unfortunately also kind of expected. Now if what we need is just to make the channel explicit, can be an easy change in the code so if so let me know. |
Linking this also with #36 |
Yes, correct.
What I did was simply adding a "channelId" line to the payload in async_api_setDeviceCameraStatus function (in file api.py), like this:
After this modification, the integration started interacting correctly with the device, apart from some hiccups in the live stream (sometimes it works, sometimes not).
Unfortunately, I don't have any other Imou camera to check, so I agree with you that possible impacts on other models is something that should be verified. |
Perfect thanks, I will do some tests on other models and report back! |
Hi, I run a test against two other models that I have here (IPC-C22C-D and IPC-C22F-C) and as expected the channelId addition had no impact and everything works correctly. I will add the fix in the next release, I'll keep you posted. Thanks! |
Great, thank you! |
Do you mean the motion detection switch or the motion alarm sensor? The first one should be there regardless of the camera's capabilities, the latter only if the device supports the AlarmMD capability. Thanks |
I mean the motion alarm sensor. Actually the motion detection switch is there correctly, but the motion alarm sensor is not. As far as I understand though, the device doesn't support it, because if I call a device capability list function I don't see the AlarmMD one in the response. |
Correct! it shows up only if the device is AlarmMD capable. However, this was more an educated guess from my side. If you are familiar with python you could try installing |
Thank you for the info. Capabilities: Switches: Almost everything seems to be set to off, though... |
Closing this since in v1.0.14 just released the additional parameter with channelId has been added. Thanks! |
Sorry @tango13 I missed your message. Yeah, not very informative the output of the command as I was afraid of :-( |
Reopening the issue. @tango13 is this new release working for you? I've added the channelId information in the API call. Thanks |
Yes, the new release works well for me, even though sometimes the video stream doesn't start from within HA. |
I still not able to load the stream from the cell go model camera with this new integration update ... Can you please let me know if I need performing something more in order to get this working? Thank you |
Thanks guys, So looks like the new version is working indeed but there is a problem with the streaming. Couple of questions:
Thanks |
For me, it was the same as now, that is sometimes it works, sometimes (well, I should say most of the times) it does not. When it doesn't work, I get a "Error with media stream contents".
Not in my case. Thank you! |
By the way, is there any chance in your opinion to have the motion alarm sensor supported for this camera? |
Hello I try several times during the last days with the new integration update and I never get the stream working SD or HD, even if I have Preload camera stream option available or even IF I start the stream with IMOU application in order to try "preload" the stream... |
Hello to all I opened a Ticket on the IMOU Cloud related to the stream not available from the cell Imou cameras and now I have to respond about, If some one can please help me in order to get this info to reply I will appreciate Imou Technical Support Question Thank you |
Hi, |
Is your feature request related to a problem? Please describe.
I have integrated an Imou Cell go camera into HA but I can't get any live feed and some sensors are not reported (like Battery reports unavailable)
Describe the solution you'd like
I might be totally wrong but I read request #36 and it seems the Cell go is not that much different (battery operated, no permanent live feed)...reason why I am opening it as a request as there's no official support yet I guess
Thanks
Eric
The text was updated successfully, but these errors were encountered: