# Architectural design map/diagram of automations **URL:** \ **Category:** Ideas & Suggestions\ **Tags:** homey-pro\ **Created:** [May 28, 2026, 10:25am UTC](https://community.homey.app/t/architectural-design-map-diagram-of-automations/155454 "2026-05-28T10:25:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ensaftigcalzone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ensaftigcalzone/32/79107_2.png) [@ensaftigcalzone](https://community.homey.app/u/ensaftigcalzone)\ **Post date:** [May 28, 2026, 10:25am UTC](https://community.homey.app/t/architectural-design-map-diagram-of-automations/155454/1 "2026-05-28T10:25:44Z")
I’m missing a way to effectively document an entire automation that spans over multiple flows in one place in Homey. I’m of course using the “notes” in my advanced flows to document close to each specific part of the automation, but I would really like a “diagram” or at least an expandable notes card that I can use to describe the high level design with all dependencies. I think that could be useful as some of my automations contains a mix of advanced and “standard” flows which doesn’t have the notes ability at all (third party app solving this would mean more of a mess in my opinion). I understand that I could link to a third party diagram/documentation solution but I would much rather have the documentation as close to home(y) as possible. 🙂 Another possibility would be to be able to build the relationship between flows within flows and then visualize them based on their relationship to one another. ---
**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\ **Post date:** [May 28, 2026, 10:48am UTC](https://community.homey.app/t/architectural-design-map-diagram-of-automations/155454/2 "2026-05-28T10:48:48Z")
Maybe this is useful to you? It’s about generating automated descriptive documents, not sure how to create diagrams (if possible at all): > [@How I built a self-maintaining Homey documentation system with Claude](https://community.homey.app/t/how-i-built-a-self-maintaining-homey-documentation-system-with-claude/155308): > > Written, of course, with the help of Claude… The problem When you’re deep in a flow at midnight adjusting a lux threshold or rewiring a logic branch, you know exactly what you’re doing. Six months later, you don’t. Which flows read the Holiday mode variable? What’s the contract between the heating watchdog and the house state flow? This gets harder as a setup grows. I have 114 flows and over 230 devices, spanning energy management, security, heating, presence, lighting, climate monitoring, aud… > [@How I built a self-maintaining Homey documentation system with Claude](https://community.homey.app/t/how-i-built-a-self-maintaining-homey-documentation-system-with-claude/155308/4): > > Happy to share. I actually already put my MCP server I a public GitHub repo as it was the easiest way for me to deploy easily to multiple machines and keep them up to date with the latest version. So that’s at [GitHub - jmdraper/homey-mcp · GitHub](https://github.com/jmdraper/homey-mcp) I don’t want to share my actual docs but I had Claude create an example template based on my current docs - attached. I haven’t got round to putting the Homey app in a repo yet but will do when I get a moment. Or you can ask Claude to create one to in… ---
**Author:** ![ensaftigcalzone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ensaftigcalzone/32/79107_2.png) [@ensaftigcalzone](https://community.homey.app/u/ensaftigcalzone)\ **Post date:** [May 29, 2026, 7:25am UTC](https://community.homey.app/t/architectural-design-map-diagram-of-automations/155454/3 "2026-05-29T07:25:40Z")
Could be worth trying out, thanks for the tip. I like the idea of keeping the documentation in sync with the environment, preferrably I would like for something Homey native though to keep it close to the resources utilized, but will give it a try. 🙂 ---
**Author:** ![ensaftigcalzone](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/ensaftigcalzone/32/79107_2.png) [@ensaftigcalzone](https://community.homey.app/u/ensaftigcalzone)\ **Post date:** [May 30, 2026, 5:52pm UTC](https://community.homey.app/t/architectural-design-map-diagram-of-automations/155454/4 "2026-05-30T17:52:26Z")
I started using the other threadstarters solution with my own tweaks now, so thanks for pointing me in the right direction. 🙂