close-issue-app[bot]
commented
3 years ago Hi there. Thank you for filing this issue. Unfortunately, we cannot help you, as you haven't sticked to the provided template and/or have not provided all information requested. Consequently, this issue has been closed. We're more than happy to help out where we can once you raise a new issue containing all requested information in the requested format. In this regard, please take note that: - read the template thoroughly - all given header lines (starting with ###) must not be deleted - everything enclosed by is intended to give you guidance and should be replaced by your input specific to the issue - Listings regarding your environment must be filled out completely where applicable (bug reports and user questions). - Not following the template or providing insufficient information can still implicate manual closure. So please, first help us a bit to help you!
Describe the question or issue you are having
I installed deCONZ GUI by following https://phoscon.de/en/conbee/install#raspbian. It interfaces with my Homebridge installation on the Raspberry Pi.
I then set deCONZ to start automatically when my RPi boots up via:
But I found that this prevented me from opening the GUI. Is that to be expected?
So, I stopped that autostart service and instead used
@Smanar helpfully pointed out that the autostarted GUI would eventually switch to select the Conbee II device in https://github.com/dresden-elektronik/deconz-rest-plugin/issues/3415#issuecomment-736840094
So everything is more or less working as intended for me (except I would prefer the GUI to not search for my nonexistent Raspbee, and start minimized).
However--- am I supposed to be able to open the GUI when the headless autostart is enabled?
Environment