It’s a feature that has never been requested and/or no developer has been willing to volunteer to create it. I believe the use case envisioned by the developers for BasicUI/ClassicUI is that a sitemap is wholly self contained. Instead of creating different sitemaps for different parts of your home automation, you would create different sitemaps for different users of your home automation.
You would define a sitemap that includes everything that that given user is expected to do. Switching between sitemaps is not something that is expected to be done.
Not Groups. Groups give you no control. You want to use Frames and subelements. For example:
Text item=gIndoorTemps label="Climate [%.0f °F]"{
Frame label="Status and Controls" {
Setpoint item=aNest_TargetTemp minValue=50 maxValue=75 step=1
Switch item=aNest_Fan
Text item=vNest_State
Text item=vNest_Online
Text item=vNest_LastConnection
Switch item=aMBR_Humidifier
Slider item=vMBR_Target_Humidity
}
Frame item=gIndoorTemps label="Current [%.0f °F]" {
Text item=gIndoorTemps
Text item=gIndoorHumidity
Text item=vMBR_Temperature
Text item=vMBR_Humidity
Text item=vNateBR_Temperature
Text item=vNateBR_Humidity
Text item=vNest_Temp
Text item=vNest_Humidity
Text item=vBasement_Temperature
Text item=vBasement_Humidity
// Temperature
Switch item=ChartVisibility mappings=[h=Hour,d=Day,w=Week,M=Month,y=Year]
Image url="http://argus:8080/static/temp.jpg" refresh=1000
// Humidity
Switch item=ChartVisibility mappings=[h=Hour,d=Day,w=Week,M=Month,y=Year]
Image url="http://argus:8080/static/hum.jpg" refresh=1000
}
Pay attention to the curly brackets. When you create an element (e.g. Text in this case) and supply curly brackets, everthing defined inside the curly brackets is put in a subpage of the sitemap. In this case, the indoor climate information for my house. NOTE: this subsection pasted in above is not complete, you must have a closing } for every {.
Clicking on “Climate” leads to
Clicking on the back arrow goes back to the previous sitemap page.
You can file an issue on the openhab-uis repo, but I believe that BasicUI is also on the chopping block along with PaperUI with one unified UI being built to replace them both so I’m not sure much would be done to create a home button unless you implement it yourself at this point…
HABPanel does support navigation between panels. And you can probably make something work using a Webview.