@mike.maxwell Could you edit this driver so that one can "remove" (it's greyed out currently) the child device? The Fibaro Wall Plug itself you can control the on/off status of the plug, but the "child" USB port the only option is energy monitoring, which I personally don't need for USB.
The reason I want to delete this is I have 10 of these plugs and these devices are quite chatty in the logs, and I don't have any use for having the device listed on my hub since on/off control isn't provided as I'm not using the only ability the (usb) driver provides (energy monitoring).
@mike.maxwell Any chance this removal of the child device can be added to the "list"? I'm currently unable to "finish" configuring the new Schlage driver in the update because it keeps getting interrupted by the activity from these devices (I have 10 of that I don't need/nor want) the configuration does not restart itself after it gets interrupted, so each time I manually start it again, and get interrupted by another one of the ten. (literally 3 pages of logs)
Not sure I'm following on this.
I dont see any logs from the lock, so I'm unsure what you feel is getting interrupted.
Yes I was just showing the log quantity of these devices......I did eventually get the locks configured when I finally got it in between these devices reporting so many entries.
What I was referring to was that when starting lock configuration of the lock if these devices started reporting all these entries during the same time it would interrupt the configuration of the driver, and the process would have to be restarted because it would stop the configuration.
Which is why I posted this on this page and not one referring to the locks, any chance this "remove child device" can get added to the list?
I understand the request to make the use child device an option. My question was regarding the configuration, what aspect of it?, are you referring to the getCodes sequence where it fetches the initial codes?
Yes during the get/fetch codes part.....sometimes it would interrupt right at code #1 and others would be fetching code #8, 12, 17, etc.
@mike.maxwell You are officially my hero.....Thank You!
Although I learned my lesson on beta testing updates and will wait until the hotfixes are done before getting it.
Ah, no spirit of adventure?
Nope, I didn't buy into the platform only to have to continually rebuild my hubs setups after replacement hubs are sent.
Glad to hear you've taken a new approach to firmware releases! Let the eager, overachievers find the remaining bugs for the rest of us! 
2 Likes
Exactly, although now that I took your advice in solving any further chance at the Hub having NTP issues, I still don't have the stomach to rebuild this for the 13th time, as I'm still not completely done rebuilding from the last one.
1 Like
