> For the complete documentation index, see [llms.txt](https://docs.pollination.solutions/user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pollination.solutions/user-manual/rhino-plugin/interoperability/ladybug-tools/entity-components.md).

# Entity components

An entity component it is similar to a Rhino param. Right click on it to access to menù of actions. Generally the available features are:

* **Synchronize**: It refreshes the data which the component is reading.
* **Select**: It selects the objects from Rhino canvas
* **Bake**: It bakes Honeybee objects or Pollination Rhino objects
* **Internalise**: It saves in persistent memory the data
* **Clear**: It clear the persistent memory

### Current Limits

* They do not internalise Honeybee object in the persistent memory
* They do not support automatic synchronization for now

## From Pollination Rhino to Honeybee

Use one of the entity components, for example \_Pollination Room \_and right click on it.

![Menu of the actions](/files/-Mf2bQM6TiiUYMu5rKq3)

Click on \_Select Pollination Rooms \_to select the rooms you want from Rhino canvas. It convert every Pollination Rhino room to a Honeybee room.

![Selection of the Pollination rooms](/files/-Mf2cM2x8smSCR8Digv9)

Continue the workflow with Honeybee. For example, I can add border shades to all apertures. Use one of the preview components of Honeybee to check the geometries.

![Continue the workflow with Honeybee](/files/-Mf2dAW_M3AL73Q8G4xe)

At this point you can decide to continue with Honeybee or going back to Rhino using the Bake feature.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pollination.solutions/user-manual/rhino-plugin/interoperability/ladybug-tools/entity-components.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.