openweather plugin ?

[PerH]

Just started looking into the background stuff for the domoticz plugin.. It uses a separate Miio-server instance to talk to the vacuum, and i suppose that could be upgraded to push directly to MQTT? it uses the python miio library..

I have no idea of how to go about that, and with what layer.. guess i could ask the miio server developer..

[therealdb]

@perh I’m writing an mqtt client for my deebot. I’m working slowly but it’s coming nicely. I’ll publish the device file with a virtual http device next week.

[CatmanV2]

@therealdb said in Generic support for vacuums:

@perh I’m writing an mqtt client for my deebot. I’m working slowly but it’s coming nicely. I’ll publish the device file with a virtual http device next week.

Might have to buy a Deebot then
C

[therealdb]

@catmanv2 it’s based on nodejs, but since you’re on openluup, you’d run nicely along it. Logic is still rough, but I’m pushing maps via telegram as well when cleaning is completed

[ronluna]

@therealdb could use homebridge 2 openluup also...

[therealdb]

@ronluna I've taken a look and it's using the same base library. I'll push some changes I did in the next days, since the library is good but not well organized. I've already added a couple of features. But I digress.

I've finally completed the part pushing via MQTT. I could get nice maps pushed to me and my wife via Telegram with the map, when it started (un'ora fa - one hour ago), how many square meters (69) and the duration.

Next week I'll build the device file for Vera/openLuup. I've started pushing the variables, so it's just a matter of stabilizing them, make them generic and build the UI.

[CatmanV2]

Love it. Will this work with any Deebot?

C

[therealdb]

@catmanv2 yes. keep in mind it's not lua-based, but a nodejs app pushing data into mqtt. since mqtt it's supported under openLuup these days, it's not that difficult, but it's not plug-and-play. home assistant should have similar features, but it's written in python and I'm not that proficient - plus I'm not really runnning HA in production, since I prefer to thinker with APIs and similar these days.

[CatmanV2]

I understand about half of that

C

[therealdb]

@catmanv2 If you go the HomeAssistant or homebridge route, it's pratically plug&play
I'm just playing with stuff, because I'm working too much, life is still slow, and I need to fill some voids. It should be easier to integrate than via my route
But a generic device file should benefit everyone, regardless of the routes you'll follow to map your vacuum.

Next I'll get a robo mower, because I'm tired of cutting the grass, and I'll probably write another device file with associated services, so anyone could map their and see status, alerts, etc.

[PerH]

I suggest that you buy a xiaomi mi vacuum as well!

(good job!)

[therealdb]

So, I've just started to collect variables. In honor of this place, I'm starting to use this new service ID: urn:smarthome-community:serverId:Vacuum

I've consolidated this variables, but I'm waiting for feedback (@akbooer , @rafale77, @toggledbits):

• CleanState: the clean state (idle, auto, alert, etc)
• LastClean: the last clean date
• LastCleanImageUrl: a map of the last clean, if available
• LastCleanSquareMeters: (should we just use a generic unit of measure?)
• LastCleanDuration: the duration
• LastCleanDurationFormatted (last clean formatted)
• LastError/LastErrorCode
• ChargeStatus (0/1)
• SleepStatus (0/1)
• CleanSpeed (number)
• Description: something more verbose, like "docked and charging", or "auto", "clean started at", etc.

Is there anything I'm missing?

[rafale77]

I think all the "Last****" variables are very good but I tend to be a minimalist for the rest. I would actually suggest to remove the sleepStatus, the ChargeStatus binary sensors and add the BatteryLevel instead. Does the CleanState include Cleaning/Paused/Stopped?

[therealdb]

I think we could define the values for CleanState. Right now, I'm using:

• auto
• pause
• idle
• returning
• alert
• spot_area

BatteryStatus is taken from the standard service, as well as status (on/off) and I actions are possible via Switch service as well (SetTarget 1/0).

This post is more a request for feedback, we could add/remove variables if necessary.

[akbooer]

I'd like to make intelligent comments, but I've yet to go into any details of robot vacuums. You seems to have covered that basics above.

[toggledbits]

Bin full/empty, filter OK/need change, very common across HA platforms I'm seeing...

[PerH]

The domoticz xiaomi vacuum also has a Reset consumables (filter, brushes, sensor cleaning) counter (in that can be reset.

[therealdb]

@perh same for the evovacs lib I’m using.

I’ll add the new variables to the proposed list and then start with actions.

[CatmanV2]

Thread resurrection but my Deebot arrives today (hopefully) I didn't want to jump into anything

With MSR running on the same host as OpenLuup and AltUI can I use the Deebot plug for additional funkiness?

Cheers

C

[therealdb]

@catmanv2 I have my deebots under home assistant and I’m activating them via MSR, based on our presence. I have also notifications, via custom code. No need to map under Vera/openluup, because I control them via its native Alexa skill.