# \[HOW TO\] View your Homey v2 flows in a browser

**URL:** <https://community.homey.app/t/how-to-view-your-homey-v2-flows-in-a-browser/7427>\
**Category:** Questions & Help\
**Created:** [January 19, 2019, 8:58pm UTC](https://community.homey.app/t/how-to-view-your-homey-v2-flows-in-a-browser/7427 "2019-01-19T20:58:18Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![DaneedeKruyff](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/daneedekruyff/32/964_2.png) [@DaneedeKruyff](https://community.homey.app/u/DaneedeKruyff)\
**Post date:** [February 7, 2019, 4:54pm UTC](https://community.homey.app/t/how-to-view-your-homey-v2-flows-in-a-browser/7427/34 "2019-02-07T16:54:23Z")

</div>

Ok, so in your case retrieving the IP address wouldn’t even enable you to connect **Homey 2 flow viewer** to your Homey.

I suggest reporting this to Athom [here](https://support.athom.com/hc/en/requests/new) because that’s not intended behaviour. In your situation you wouldn’t be able to connect to your Homey when the Cloud services can’t be reached, not something you want.

See this [topic](https://community.homey.app/t/is-there-still-no-local-access-v2/8778)

---

_[View the full topic](https://community.homey.app/t/how-to-view-your-homey-v2-flows-in-a-browser/7427)._