You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was trying to setup my deebot configuration within homebridge. Plugin installs without errors and does find my deebots (i have two in my account), and homebridge buttons for "Clean", "Go Charge", "Charging status" do appear for both deebots.
They also seem to work as indended.
(1)
Then i was trying to get Eve running for predefined rooms (spot areas). First of all it seems that "hideMotionSensor": false
has to be set, as the predefined area infos are hidden behind that motion entry within Eve. It makes sense after digging through it, but maybe a hint somewhere in the setup docs could clarify that, to save one from needless struggle.
(2)
After having found that i encountered, that the plugin (it seems) only reads the spot areas of the first configured device, or does not correctly reset the firsts values for the following device(s). So the spot areas are set to the same value or a mix of both for each device.
Hi Ben, having just added my second deebot device, I have noticed similar behavior in the current plugin version (v6.1.1.) regarding spot areas. At first the behavior seemed completely irrational. However, after some testing, I realized that the entries for the second device seem to overwrite the entries for the spot areas of the first. Since the range IDs are not necessarily sequentially ascending, some entries show unexpected behavior, while others simply result in an error message.
When I find some time, I'll have a look at the code, but so far a workaround for my devices has been just to extend the first list of spot areas by the number of entries in the second list and then only use the last entries that are not overwritten by those in the second list.
Thank for your comment. If have to say that I left behind domoticz and homebridge i while ago. I gave home assistant a try and have to say that it is quite impressive how much is working there without a struggle and off the box, that also holds for it's homekit module as for deebot (and much more).
I was trying to setup my deebot configuration within homebridge. Plugin installs without errors and does find my deebots (i have two in my account), and homebridge buttons for "Clean", "Go Charge", "Charging status" do appear for both deebots.
They also seem to work as indended.
(1)
Then i was trying to get Eve running for predefined rooms (spot areas). First of all it seems that
"hideMotionSensor": false
has to be set, as the predefined area infos are hidden behind that motion entry within Eve. It makes sense after digging through it, but maybe a hint somewhere in the setup docs could clarify that, to save one from needless struggle.
(2)
After having found that i encountered, that the plugin (it seems) only reads the spot areas of the first configured device, or does not correctly reset the firsts values for the following device(s). So the spot areas are set to the same value or a mix of both for each device.
results in the following logs:
which is identical for both devices (and resulting from the first configured device).
Hiding the first device
leads to
which is the 2nd device configuration enriched by the last three spot areas of the first (disabled) device.
Another try has been to change the order of the devices in the configuration.
which gives the same result as before (so it seems that the "longer" configuration wins and is taken for all devices.
Will try to circumvent it somehow for the moment.
Details of your setup.
(1)
HB1.7.0
Plugin6.1.1
Docker instance (oznu/homebridge) on RPi4, Node.js v18.19.0
Both are DEEBOT N8.
The text was updated successfully, but these errors were encountered: