Closed Esp32-zapper closed 2 weeks ago
Sorry but I didn't understa much of that? Do we have something I could try out or was the conclusion that Kerui is as close as it possibly can be?
There are some changes to kerui 300w config that should better support this device. But these are so close in functionality it is not worth adding a new device.
All sensors are working but there is no video stream and to change direction of the camera is very hard. In the Tuya app thee is a step by step directional arrow cross to point the camera but here you will only get a menu to select end points. There is a stop button but it has no effect because of the delay. It will not pick up the stop command until it already reached the max position.
Is there something that could be done of is this as good as it could be on this cam?
Strange. Downloaded the new file and reloaded the device. New arrow devices shows up, so it must have recognised the new file for the 300w. However, the video stream is still dead so I thought maybe just updating the file still doesn't change that it's been "paired" with the kerui and didn't really care about the new option in the file for the Fuers. So, I removed the device and tried to add it again. Now it refuses to give me the Kerui300w as suggestion but the 200w shows up instead. The 300w model doesn't even show up on the list.
I have checked. The 300 file is in the device folder. When it thought it was a 300, it could access the file as I got the upgraded buttons.
What could be wrong?
Video output does not come through the tuya protocol, so is outside the scope of this integration. For some cameras, WebRTC or RTSP can work locally if you can find the right parameters for your camera. For others, they can only work via the cloud.
The still snapshots may show up if the camera is encoding still images in the local protocol, and not sending a key/partial link for fetching them from the cloud.
Ok, but it used to recognize the camera as a kerui300w but now it can't even see that as similar. Checked permission and it has root/root 644 just as the rest of the files in the device folder.
I can't answer questions posed as "it doesn't work, what am I doing wrong?". I am not psychic.
The config has been made based on the data provided. If it is not working, you need to provide new data in order for anyone to try to figure out why. Since the DPS information is fixed and does not change, this means the Logs.
Felet härrör från en anpassad integration.
Logger: custom_components.tuya_local.config_flow Källa: custom_components/tuya_local/config_flow.py:485 integration: Tuya Local (dokumentation, ärenden) Inträffade först: 13:20:29 (1 händelser) Senast loggade: 13:20:29
Device matches kerui_200w_camera with quality of 83%. DPS: {"updated_at": 1730722823.0028386, "101": false, "103": false, "104": true, "105": false, "106": "2", "108": "0", "109": "0|0|0", "110": 5, "116": true, "117": 0, "119": "3", "134": true, "150": false, "151": "1", "160": 81, "161": true, "239": "motion", "241": "{\"video\":[{\"restype\":\"4\",\"oldres\":\"23041296\",\"newres\":\"28801620\"},{\"restype\":\"2\",\"oldres\":\"23041296\",\"newres\":\"28801620\"}],\"message\":\"2880*1620\"}"}
As you can see in the orig post, it recognised the 300w version as 93% alike but now it ignores that file completely and thinks the closest is the 200w version, with only 83% likeness.
That worked much better! Now it picked up the 300w version with 100% likeness directly. Pity about video feed but I can get that from Tuya and the rest from you. Will work! Tnx a lot!
Log message
DPS information
Product ID
o9jlvpqqunankygf
Product Name
Fuers 5MP WiFi Indoor Surveillance Camera
Information about how the device functions
Works a lot like the kerui_300w_camera exept that you can not access the camera output. no feed detected
Could not find a manual but this page might help https://fuers.co.uk/index.php/product/fuers-5mp-ip-tuya-smart-home-wifi-wireless-surveillance-camera/