Any thoughts or opinions about adding a debugging GUI? I'd be willing to write and demonstrate a PyQt5 gui. Would probably end up looking like a tree-view for each device with a toolbar that has buttons for adding new device, deleting an existing device, repair network, etc.. Each node on the tree would give the latest information and allow its features to be directly controlled. I could see it turning into a pretty useful tool for debugging and even general z-wave development (adding new devices that have very little available information, e.g. the Ring security front panel and door/window sensors which are using some of the proprietary codes but are still accessible from a z-wave USB device).
Qt5 and the PyQt5 bindings are both GPLv3 so there shouldn't really be any licensing issues. It might be better to throw it in a separate library (pyzwaver_gui for example) so that this library doesn't have a hard dependency to the GUI, which would be better for those that don't need it).
Thoughts?
Any thoughts or opinions about adding a debugging GUI? I'd be willing to write and demonstrate a PyQt5 gui. Would probably end up looking like a tree-view for each device with a toolbar that has buttons for adding new device, deleting an existing device, repair network, etc.. Each node on the tree would give the latest information and allow its features to be directly controlled. I could see it turning into a pretty useful tool for debugging and even general z-wave development (adding new devices that have very little available information, e.g. the Ring security front panel and door/window sensors which are using some of the proprietary codes but are still accessible from a z-wave USB device).
Qt5 and the PyQt5 bindings are both GPLv3 so there shouldn't really be any licensing issues. It might be better to throw it in a separate library (
pyzwaver_guifor example) so that this library doesn't have a hard dependency to the GUI, which would be better for those that don't need it).Thoughts?