Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature request] Automatically identify host device
See original GitHub issueIs your feature request related to a problem? Please describe.
There exist a multitude of OS specific releases of RaspberryMatic.
It is sometimes difficult to asses the host hardware without physical access. Users are often unaware that they could check the host device by
- Enabling SSH in the frontend
- Querying
/proc/device-tree/model
Example for my device:
# grep Model /proc/device-tree/model
Raspberry Pi 2 Model B Rev 1.1
This makes the OS update process unnecessarily difficult and error prone.
Describe the solution you’d like
Automatically query /proc/device-tree/model for the type of host device RaspberryMatic is running on.
Present the user with the appropriate link to the OS update package for their specific model.
Bonus:
Automate the download and installation of updates.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
What do you mean exactly about “architecture”? RaspberryMatic is using buildroot/Linux for the OS stuff, and OCCU for the homematic/CCU stuff which is published by eQ3. And sorry, no big time for documentation here (as usual). So feel free to ask specific questions (but probably better in the german speaking HomeMatic Forum, if possible).
@jottr Sorry, but instead of simply adding a link and/or device model info the WebUI, I would like to give #616 more priority as I feel if we touch this area now anyway we should better go for the bigger than and integrate it nicely. Users have lifed with it so long already and given they know the hardware they are using simply displaying a link and/or device tree model info doesn’t help a lot. Furthermore, with the upcoming 64bit version of RaspberryMatic RaspberryPi2 users have to switch installation archives and reinstall their SD card anyway. Thus, no easy way to go.
And last not least I have heard that eQ3 is working on such an auto-download mechanism themself. Thus, we should probably better wait what they will come up with in the next upcoming firmware updates.
So sorry, but I still see no benefit in working on this right now.