home-assistant.io VS ha-rest980-roomba

> What's the blocker here?

It's an open source project. Stuff generally gets worked on by people who care about features. You seem to care about this. https://github.com/home-assistant/home-assistant.io

As the next step the content of the image should be written to zvol. Might help: https://github.com/home-assistant/home-assistant.io/issues/25294

I found a very simple solution for this here:

Thanks for digging into this! Based on your response and the response from u/antirobot, it appears neither the ESPHome server nor the embedded client support wsMQTT (makes sense because I was looking in vain for an option to specify the connection type). It appears HA only recently added support for wsMQTT, so I'm not too surprised.

The LIFX doc update is here: https://github.com/home-assistant/home-assistant.io/pull/22383

If coding isn't your thing, you can contribute to the Home Assistant Docs and help make tutorials and documentation more accessible. Make sure you read the contribution guidelines for understanding their contribution process. This team is super great to work with; I've already made a few contributions to their docs.

Just came across this mention of zeroconf fix in HA HomeKit bridge, might be helpful.

If you find any issues with the documentation, you can comment on the PR at https://github.com/home-assistant/home-assistant.io/pull/15555

I use this project to integrate my S9 into Home Assistant as it lets you do room based cleaning via HA. When following those steps, use the “HA Addon” section in each step to keep things simple.

You can also follow this to integrate your Roomba with Home Assistant, along with room based cleaning. The controls are sent to the Roomba over your local WiFi with MQTT.

I used this guide to set it all up. The map overlay that I created could use some work - I traced around a builders floor plan of the house but it doesn't quite line up with what the Roomba sees

To fix the issue use Rest980 and optionally PHP-Nginx with HomeAssistant - create an automation trigger based on the robot state (evacAllowed: false) and update the state to (evacAllowed: true) with some faked Cleanbase data to trick the robot into allowing the Cleanbase to evacuate ("dock":{"known":true,"pn":"4638607","state":301,"fwVer":"4.0.3"}). It's been rock solid for me.