Request support for Pet Feeder #2027
Comments
|
hey @make-all , i was reading some more about yoru integration, seesm i can add my own device in the "devices" dir? Would that work for now? since i was receiving error below: |
|
Adding a config in the devices dir will not help, as you are getting the "Failed to refresh device state for Test" error. This is because the device is not returning any data. If you can find a way to force the device to return some data, then it will be detectable, and can proceed to looking for a matching device config in the devices directory. |
|
hmm, how can i do that? how can i force the device for data? maybe by accessing it from the smart life add, and then maybe feed a portion ? |
|
if i add it back to localtuya, and then do a local activity, will that work? will that provide data to be detactable? Probably not ? since it opens a session i belive, and only once sessios is allowed? |
|
aha!!! when adding it to tuya-local, and forcing some data, it was now added in your intergration, all entities are disabled , probably because the type doesnt match with my DP points? I choose "ceres_plus_petfeeder" during the setup when adding it
|
|
ok, added a new yaml file like below , added it to the devices dir, changed the product id...
|
|
Ceres is not a good match. The problem with these pet feeders not providing much / any info by default is that they can't reliably be distinguished from each other. Ceres requires the "101: basic_indicator" dp - I don't know whether that device consistently reports that, or the user that reported it came across a workaround like you used. That happens to match on your device, along with a few more of the optional video related controls, but the manual_feed id is 245 on that device, and 201 on your device, so the important feature that you want is not going to be available. If you do write a config, I think even if the number entity for dp 201 shows Unavailable and may be disabled in the UI as a result, you can still set it with the number.set_value service. |
|
hmm, not following, i added a yaml file in the custom_components\tuya_local\devices not sure what i need todo ? |
|
i took a lot of copy/paste config from the petlibro_camera_feeder file, |
|
when i want to add the device, and i force the state change of DP 101 , it indeed adds the device, i just need/want to know how can i force it using my new added config file, it still propeses to use the ceres file |
|
ok, i'm a step further now, seems the "optional: true/false" is in important setting to match a device, when adding the device, it now asked me to setup the v330 device, so i selected it, but still all values are unavaible and disabled? what am i missing here? the DP 101 is the DP where i match the device |
|
ahh, i now why, after restarting HA, i see this: 2024-06-20 16:52:53.406 ERROR (MainThread) [custom_components.tuya_local.device] Failed to refresh device state for Petfeeder. Once i change someting on the petfeeder manually, all entities are alive ... that means i just need to find out the DP that makes the device refresh, seems 101 doesnt do the trick ... how can i find that out? |
|
Created a PR for mine v330 , it works, but to make the entities avaible, i need todo manally an action on my petfeeder Not sure if you know a trick to find out what DP is giving state so its detectable ? |
|
I don't know any tricks for finding this out without trying all of them. |
|
i tried them all in the device file, by defining : "optional: false" to all DP do other devices also have such kind of behaviour? have you seen it before? |
|
At least one dp need to not be marked optional. Otherwise there is nothing left to match against. Probably it is best to wait for the enhancement that will remove that restriction and allow matching without dps. |
|
What enhancement is that? Is that a new feature coming? But then I still have the issue if I restart HA, that all entities are unavailable, right? Untill I manually force an event... |
|
Probably. |
|
Ok, I see a similar issue here, I can try changing it to 3.2 ? |
|
You can try, but I think you would be getting a different error and the workaround of making a change using the app while adding would most likely not work if the protocol version was the source of the problem. |
|
adding it by using 3.2 is working! seems the config file is correct, 101 is a working DP |
|
tried restarting HA, entities also still avaible |
|
Btw, do you also have support for camera streams? My petfeeder camera doesn't expose RTSP 554 , I need the tuya cloud integration to fetch it... Thnx |
make-all
added
awaiting confirmation
- Add camera - Add additional attributes for non-useful data. Issue #2027
make-all
removed
new device
- Add camera - Add additional attributes for non-useful data. Issue make-all#2027
Only differences in config were product id and name, and original used camera entity, while new one used switch after review feedback because the device is returning a filename in json not the image data. Original report make-all#2027 seems to say that one does too. PR make-all#2105
Hi, requesting device support for a Cat Pet Feeder, as discussed before, i wasnt able to add the device
-->
Log Message
Information about DPS mappings
Product ID: ibnk6keua0zzc2gr
Information about how the device functions
When i add it to tuya cloud integtation, it looks like below:
here is the json exported, from the cloud integation, i use it in cloud integration too, since that intergation aslo creates an camera entity... I dont think localtuya or tuyalocal supports camera entities?
ALso important, when i added it to localtuya/tuya cloud, there was 1 important DP missing, it was DP 201 , thats the one where i send values too, to make the catfeeder actually feed... i used the set DP service, it would be wonderfull it you can add this DP 201 too, so can send portions to it , like, below example, i'm sending 5 portions, but as discussed, it can be a numeric entity too ...
Do you need more info from me.
The text was updated successfully, but these errors were encountered: