New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Download dump file for homebridge-deconz and homebridge-hue2 #1268
Comments
I'm actually trying to create a dynamic settings interface, using @homebride/plugin-ui-utils. Maybe I could create the option to download the dump file there? How do I create a button on the form that looks like the DOWNLOAD button? Or like the SAVE? I managed to create a button alright, but I cannot make it black or purple - only ugly white, red, or blue. I do see an error in Safari's JavaScript console, but I don't think it causes any ill effects:
|
hi erik just going through some of the issues here, did this come to a resolution? |
Not yet. Homebridge deCONZ is now on v1.x and fully functional, except for the dynamic settings interface. I’m more into backends and not really experienced in UI development (that’s why I’m using Homebridge in the first place: to let HomeKit handle the UI). I looked into creating a PR for homebridge-config-ui-x, but had a hard time understanding the code. |
Is your feature request related to a problem? Please describe:
I'm finally migrating homebridge-hue to dynamic platform accessories. Rather than updating the plugin, forcing a big-bang migration, I'm actually creating two new plugins: homebridge-deconz and homebridge-hue2, see ebaauw/homebridge-hue#1070. Both new plugins will be creating a dump file, just like homebridge-hue.
Describe the solution you'd like:
Same feature as #676 for homebridge-hue: an option to download the dump file from the plugin Settings in the UI.
The dump files will be named:
homebridge-deconz.json.gz
andhomebridge-hue2.json.gz
.Describe alternatives you've considered:
None. If it ain't broke...
Additional context:
Since the new plugins can now persist data in
cachedAccessories
, there's no longer a need to add the API key (username) to config.json. Consequently, I'm also getting rid of the user-defined keys in config.json.I'm still in the process of developing the new plugins, and they're not yet creating the dump files, so there's no hurry to implement this. Just filing the issue already, so you can do this at a moment that's convenient for you. As always, thanks!
The text was updated successfully, but these errors were encountered: