Agents In Use
What’s new todayLast update
11 use cases added today

Grok Bot builds Home Assistant heating logic

@Mercurion5d reports Grok Bot building heating logic with seven daily schedule slots, four away levels, window-based radiator cut-offs and thermostat recovery rules, without the user writing code.

Source published x.comAgent: Grok Bot
OUR ADAPTATION

Suggested prompt

Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.

Document my existing Home Assistant heating rules, including schedules, occupancy, window cut-offs and thermostat recovery. Identify gaps without assuming any connector or changing live settings.

Evidence at a glance

Sourced account
Source poster / publisher
@Mercurion5d
Original account
Read the source ↗
Published
Source link checked
Reported result
@Mercurion5d reports a code-free heating setup with seven daily schedule slots, four away levels, per-window radiator cut-offs, sensor corrections and thermostat recovery logic.
Human involvement
The user requested a diagram and says he wrote no code. The post does not describe access setup, approval of individual heating changes or an independent test.

A linked account supports attribution. It does not mean we independently reproduced its result.

Report an issue with this caseOpen correction email

Opens your email app with the case link included. Nothing is sent automatically.

How the agent did it

  1. The poster describes Grok Bot building the household heating logic without him writing code.
  2. The resulting rules use daily schedules and four distance-and-time away levels.
  3. Window sensors cut off the corresponding radiator and room sensors correct thermostat readings.

@Mercurion5d asked Grok Bot to draw how the household heating worked and was surprised by the extent of the system it had built. The post describes seven schedule slots per day, four away levels based on distance and time, and home-office detection for his wife. He says he did not write a line of it.

The heating rules combine occupancy with room-specific controls. Each open window cuts its own radiator, while room sensors correct thermostat readings. The poster also describes self-healing when a thermostat drops out. Scout's supplied diagram description adds recovery triggers for a thermostat coming back online or a setpoint being changed by hand.

This is an account of Grok Bot building automation logic, not proof that a conversational agent makes every heating decision at runtime. The Home Assistant rules are the resulting system. The source does not explain how the bot accessed Home Assistant, and its closing request for a connector should not be turned into evidence that one was used.

The text reports seven schedule slots, although the supplied diagram description lists eight trigger times. This entry follows the text's stated count without resolving that discrepancy. No heating-bill saving, energy measurement or approval policy for individual changes is reported.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: X · @Mercurion5d

Frequently asked questions

How did Grok Bot connect to Home Assistant?

The post does not say. It asks about a possible Home Assistant connector, so this account does not establish a connection method.

Did an agent run every heating decision?

The account attributes building the logic to Grok Bot. It does not establish that an agent, rather than the resulting automations, runs each heating decision.

Are the schedule counts consistent?

The text says seven daily slots; Scout’s supplied diagram description lists eight trigger times. The discrepancy remains unresolved.

More details

Remaining steps

  1. Recovery rules address thermostat drop-outs and, in the supplied diagram description, manual setpoint changes.
  2. The user asks Grok Bot to draw the heating system so he can see how its rules fit together.

About this account

Grok Bot reportedly built the heating rules and produced a diagram on request. The resulting Home Assistant automations handle the recurring controls; runtime agent intervention is not established.

Source: Scout's verbatim public X API capture, read live on 2026-10-30 and explicitly authorised as the source for this entry. Reviewed the supplied post text, author bio and media description where available; did not open X or independently inspect attachments or replies. No affiliation with the agent maker is stated in the supplied bio. Results are the poster's account, not independently reproduced. Suggested prompt written by Agents In Use; no exact task prompt is reproduced.

Credit: @Mercurion5d

Source published

Added to Agents In Use

Source checked

Tools and topics

Grok Bot · Home Assistant

Heating · Smart home · Window sensors

Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.