Didn’t get this. You are creating a REST integration, but then do another step for a MQTT wrapper? Why this?
In fact, with the REST you have a polling interval, like 1 minute or more to fetch the data.
With the MQ, it is the mower that pushes the data, so you get it instantly.
I would let the MQ update the “status” part, as it is doing in what you are currently using now, and complete it with the REST sensors for more details on all that is available.
Yes. Ofc. This is what I’m using because of same reasons. Use what is available via MQTT and some REST service calls.
But where is then the difference of your integration to the one time service-call above with the mentioned 1-2 additional REST service calls?
Not a lot of extra value, just time saved for people and no configuration needs in yaml, only config flow
2 Likes
Ok. Understood. 
Current status (in dev environment):
- Config flow working, including setup for MQTT & REST API
- I have written a Python library, called it aiorobonect (aiorobonect · PyPI ) which I am using in the integration, to make it more standard (who know perhaps it will become a standard HA integration)
- MQTT autodiscovery is working
- MQTT entities are added. Currently supported: device_tracker (for GPS enabled devices), vacuum, buttons (for the actions) and sensors
- The REST API sensors are “under construction”
2 Likes
Does anyone know how to make a time chart of a different status like mowing/charging/sleeping etc.
Like on this image:
How much better is the MQTT performance compared to REST?
Any ETA on the first release? @geertmeersman
Well, like in immediate updates? 
ETA, I hope perhaps releasing a first version by tomorrow evening or Monday evening
Nice, I’ll help test it if you want some assistance
Great! Join me on discord and I can provide some test code.
discord link is expired
Can you please share your YAML-Code? This looks so great. 
Sure. But without support because of very limited time at the moment.
1 Like
Beta version published
Including MQTT sensors & REST.
Available through HACS (you need to indicate beta releases)
What‘s wrong when I get the following error after update to the v1.0.0beta
This error originated from a custom integration.
Logger: homeassistant.config_entries
Source: custom_components/robonect/__init__.py:47
Integration: Robonect (documentation, issues)
First occurred: 11:33:37 (1 occurrences)
Last logged: 11:33:37
Error setting up entry Fredi for robonect
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 387, in async_setup
result = await component.async_setup_entry(hass, self)
File "/config/custom_components/robonect/__init__.py", line 47, in async_setup_entry
if entry.data[CONF_MQTT_ENABLED] is True:
KeyError: 'mqtt_enabled'
You need to remove the integration and add it again, it’s a “breaking” version. Meaning I did not build in the “migration”