06-20-2016, 08:02 AM
Oops. 
I didn't understand this information, which now makes sense:
I think I have this straight now. OpenHab runs on the Pine, which should have sensors connected, if using OpenHab is to make any sense. But OpenHab itself doesn't generate output that you can view via the HDMI connector on the Pine64. So, to access the data from those sensors, or to adjust any settings, or for whatever reason you need to see something relating to the Pine64's sensors, you open a browser and access OpenHab from elsewhere on the network. That is, from another computer.
Thanks for your kind replies.
I didn't understand this information, which now makes sense:Quote:This is a "headless" build, the setup process thru serial console, no HDMI vidoe output.
- Initial boot can take a few minutes before http://openhab:8080 becomes available.
I think I have this straight now. OpenHab runs on the Pine, which should have sensors connected, if using OpenHab is to make any sense. But OpenHab itself doesn't generate output that you can view via the HDMI connector on the Pine64. So, to access the data from those sensors, or to adjust any settings, or for whatever reason you need to see something relating to the Pine64's sensors, you open a browser and access OpenHab from elsewhere on the network. That is, from another computer.
Thanks for your kind replies.
NexusDude of Central Texas
- Setup: Pine64+ 2GB, On/Off button, RTC battery, 5V fan, LG 1.8A power adapter, Cat6 Ethernet, HDMI to TV, USB keyboard & mouse, SanDisk Ultra mSD "32GB" (28.7GB). Using Win32DiskImager.
- Best OS experiences: Debian XFCE >> Android Lollipop > the rest