Enable/disable TrueDetect #138
Comments
|
@mrbungle64 is this something that can be exposed via your client? |
|
yes, it's an option that one can de/activate using the mobile app. I already extracted the command (using MITM and intercepting the messages). I can share it if this can be useful as soon as I get back to my home PC. |
|
|
@mgmellia have just published a beta version of the plugin. uses the Eve app to enable/disable. @mrbungle64 thank you! |
|
Thanks @bwp91 ! I also added a Here is part of the log from the homebridge if this can help [24/07/2023, 21:23:24] [Deebot] [1] device(s) found in your account. |
|
Hey all @mgmellia @mrbungle64 @bwp91 Following this closely, am I correct to assume that only/all features that can be disabled "globally from the advanced" menu can be implemented into the homebridge plugin? I have bunch of request but I can't personally what is realistic ask from you if I can't know what can be implemented into the plug. Would you be interested in working on improvements with a zealous user? I've event sent a mail today to Ecovcas suggesting various things |
Wow, this is great! But could you please explain the logic a bit more? The TrueDetect switch in the Eve app does not reflect the current global setting in the ECOVACS app - is this supposed to be like that? Also, once I activate a scene that has the TrueDetect switch off, it stays like that, even after the cleaning job is finished. This could/should be improved I think. I would prefer TrueDetect to return to the previous setting (maybe define a default value that is always set once cleaning jobs are finished). But great work so far! |
|
The first beta was just a test to try to control the status of true detect. The newer beta (just pushed now) is an attempt to retrieve the current status and update. This probably won't work at first because I don't know the incoming values for on/off but if anyone can share some logs of hopefully this would be super |
|
i don't own a device with this feature (i dont think!) so may take a bit of to-ing and frow-ing to get this to work! |
When enabling TrueDetect in the ECOVACS app instantly: „receiving update (TrueDetect: 1]“ EDIT: I notice the ChargeState update is output twice when TrueDetect is disabled. |
|
Please try newest beta |
Looking good! |
|
In the periodic updates the ChargeState is output three times however?? |
|
@xyz667 just pushed one more beta to try |
Don't worry about this - beta versions of the plugin display more logging than necessary, it's just how it's all working behind the scenes |
|
on my Deebot OZMO T8 Pure the beta version seems to not correctly detect the TrueDetect feature :( [Deebot] [Giacomo 3] initialising with options: {"hideMotionSensor":false,"motionDuration":30,"lowBattThreshold":15,"showMotionLowBatt":false,"showBattHumidity":false,"showAirDryingSwitch":"presetting","supportTrueDetect":false,"commandType1":"","spotAreaCommand1":"", the log in fact do not show such property which exists on the app (and I can turn it on/off from there) |
|
@mgmellia and in fact i will tag @xyz667 for reasons explained later i try to keep this plugin as 'clean' as possible rather than by default exposing any features that end up showing as 100 switches in the home app. so the features that i expose by default, generally, are the "clean" and "go charge" options. Things like this new true detect I like to keep 'opt-in' meaning you will need to use the plugin config to enable this per device if it supports it. I don't have access to my homebridge instance right now, so that's why I was hoping that @xyz667 could share a screenshot of the config setting and how it appears in the homebridge ui 😀 |
|
@incline02 the above message may start to help with your query. Any additional features I tend not to immediately implement in the plugin unless it's starting to cause a stir on here. Optimistically speaking, anything possible through the ecovacs app should be possible with the plugin. But this also depends on whether the lovely mrbungle64 has implemented the feature on his package that this plugin heavily relies on. |
|
feedback on newest beta would be great, @mgmellia i assume you are no longer encountering the issue in your first screenshot earlier about the eve app? |
As requested, here‘s a screenshot (unchanged to previous beta versions): |
I too am seeing the additional „Config Name“ entries in EVE, even in the latest beta? (German language EVE app) Btw why am I defining names for the different predefined areas when they are not shown anywhere (only 1,2,3 in EVE)? |
Sorry but last night I had to fight against nodejd update and homebridge that lost all plugins and configurations. |
|
Oh the configured name thing i understand now. Ironically at the time i assumed it was something in german (without thinking) but it’s actually english 🤣 |
do you mean in the plugin settings screen? |
Yes. But I just noticed that this screen says „Note“ not „Name“ - I misread. |
|
I did some test with my DEEBOT OZMO T8 PURE and the Beta-5 version of the plugin. EDIT - Solved :) |
Cool. Now you need to set the areas as well, and you could create HomeKit scenes for certain areas/rooms with TrueDetect on or off. In theory this actually works for me. However:
Edit: one of my 5 areas works as expected, the respective scene starts a cleaning job of this area, the others just start an Auto job as described in 2 above. No idea why. |
|
I managed to create a scene to clean the kitchen with TrueDetect disabled, and two scenes to enable/disable it. everything works as supposed 👍
My problem is that the kitchen area ID is equal to 0. So I'm not sure this is allowed. As said, I'll do more tests during the weekend. But for now - it works much better than the Ecovacs app which does not allow disabling the TrueDetect on a per-room basis. |
No, |
My problem is that the kitchen has mapSpotAreaID=0... It is not clear to me how can I set a scene via the EVE app to clean only the kitchen. If I understood correctly, the value "0" is kind of a "no specific area" -- or "all areas". Am I correct? Below a snap of the logs [30/07/2023, 08:43:35] [Deebot] [Giacomo 3] MapSpotAreas: {"mapID":"1118464773","mapSetID":"647257770","mapSpotAreas":[{"mapSpotAreaID":"0"},{"mapSpotAreaID":"1"},{"mapSpotAreaID":"4"},{"mapSpotAreaID":"5"},{"mapSpotAreaID":"2"},{"mapSpotAreaID":"6"},{"mapSpotAreaID":"7"},{"mapSpotAreaID":"10"},{"mapSpotAreaID":"9"}]}. EDIT: |
|
Something is definitely off with those area definitions. I’ve checked 20 times. Area 3 in the Homebridge device settings is set to MapSpotAreaID 3, but it doesn’t go and clean that area when triggered. At least not the area as shown in Ecovacs app with the corresponding name in Homebridge log. Another thing I don’t understand: why is the Deebot switch on all the time? (Either the Clean or the Go Charge subswitch always enabled) Shouldn’t the Go Charge subswitch disable when the boot is back in the base and charging? |
|
Hi @bwp91 , while we’re at it, what about adding a few more toggles on top of TrueDetect? ;-) These are the ones that could be useful IMO: |
Hm. Currently all 2 switches are off. Maybe because Air Drying is in progress and I’ve disabled the switch for that in Homebridge config? |
Anything here would be possible 😄 |
|
Getting back to this. After 4+ weeks of testing, the new features work perfectly for me. |
The TrueDetect 3D feature can be disabled only "globally" from the advanced menu.
It would be nice to be able to program it from the plugin and then use it coupled with the predefined areas to dis/enable it based on the room.
The rationale is that TrueDetect in some rooms does not work properly and this confuses the robot that avoids entering some part of the floor as it thinks there is something there (which is not correct). The ability to disable/enable the TrueDetect feature would solve this issue.
The text was updated successfully, but these errors were encountered: