Eclipse Community Forums: Eclipse SmartHome » SOLVED: Using config to enable/disable background discovery

Help

Home

Home » Eclipse Projects » Eclipse SmartHome » SOLVED: Using config to enable/disable background discovery

Show: Today's Messages :: Show Polls :: Message Navigator

SOLVED: Using config to enable/disable background discovery [message #1800269]

Sat, 22 December 2018 14:14

Mark Hilbush

Messages: 4
Registered: November 2018

Junior Member

When a system is stable and in steady state, and there's no need to discover things, system resources can be saved by disabling discovery services for the bindings one has installed.

I understand how to enable/disable background discovery using the background config parameter and the configurationPid when the Discovery Service is declared using the @Component annotation. Like this with a configurationPid of discovery.nameofbinding

discovery.nameofbinding:background=false

However, what about when the Discovery Service is created, activated, and registered in the Handler Factory, such as how it's done in the Hue binding? Is there a way to enable/disable background discovery using a configuration parameter when the Discovery Service is running using this approach? If not, is there some other way to do it?
https://github.com/eclipse/smarthome/blob/0.10.x/extensions/binding/org.eclipse.smarthome.binding.hue/src/main/java/org/eclipse/smarthome/binding/hue/internal/HueThingHandlerFactory.java#L137

[Updated on: Fri, 28 December 2018 17:11]

Report message to a moderator

Re: Using config to enable/disable background discovery [message #1800450 is a reply to message #1800269]

Fri, 28 December 2018 16:57

Kai Kreuzer

Messages: 673
Registered: December 2011

Senior Member

For those there is no common way to enable/disable discovery. The only option is to make it a config parameter of the bridge whether or not it shall provide information about newly discovered devices - see https://github.com/eclipse/smarthome/blob/master/extensions/binding/org.eclipse.smarthome.binding.bluetooth.bluegiga/src/main/java/org/eclipse/smarthome/binding/bluetooth/bluegiga/handler/BlueGigaBridgeHandler.java#L174-L178 for an example.

Report message to a moderator

Re: Using config to enable/disable background discovery [message #1800451 is a reply to message #1800450]

Fri, 28 December 2018 17:08

Mark Hilbush

Messages: 4
Registered: November 2018

Junior Member

Thanks. I had a feeling that would be the case. I ended up doing exactly what you suggested.

Report message to a moderator

Re: Using config to enable/disable background discovery [message #1800621 is a reply to message #1800451]

Thu, 03 January 2019 19:02

Markus Rathgeb

Messages: 105
Registered: August 2014

Senior Member

An "external" component could be easily deactivated programmatically.
See e.g.

It should be easy to create a simple service that can be configured which other components should be disabled (e.g. org.eclipse.smarthome.config.discovery.internal.DiscoveryServiceRegistryImpl or every implementation of ...)

Report message to a moderator

Previous Topic:	SOLVED:API Incompatibility still exist \| Update of master done
Next Topic:	Swipe functionality for Dimmer/volume controls

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Feb 28 06:42:39 GMT 2020

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter