Hello,
when migrating over my configuration from 1.8 to 2.0 it seems to me that groups cannot be bound to a binding any more. Is that true?
Was quite handy in previous versions to send updates when the group status changed.
thanks
macmeck
I’m not sure that was ever a documented feature. I’ve never seen nor heard of binding something to a Group. But if this has changed, it is a regression.
What behavior are you seeing when you do this in OH 2? Parsing errors in the log or does it simply not update?
Use case might e.g. be to send a physical button press from a binding to a group of lights?
In general, I would assume that this is still possible, just as for openHAB 1.
@macmeck Please give a concrete example, what isn’t working anymore.
Well, I had it the other way round. Send an update via the MQTT binding once the status of a group (presence in my case) changed.
Item definition is something like (worked in OH1.8)
Group:Switch:OR(ON,OFF) gPresence "Presence [MAP(presence_display.map):%s]" {mqtt=">[broker:presence/status:command:*:MAP(presence_out.map)]"}
The log says
2017-01-25 13:44:03.630 [ERROR] [el.item.internal.GenericItemProvider] - Binding configuration of type 'mqtt' of item 'gPresence' could not be parsed correctly.
org.eclipse.smarthome.model.item.BindingConfigParseException: cannot process unknown item type Group
at org.openhab.core.binding.internal.BindingConfigReaderDelegate.getOpenHABItem(BindingConfigReaderDelegate.java:84)[176:org.openhab.core.compat1x:2.0.0]
at org.openhab.core.binding.internal.BindingConfigReaderDelegate.getOpenHABItem(BindingConfigReaderDelegate.java:56)[176:org.openhab.core.compat1x:2.0.0]
at org.openhab.core.binding.internal.BindingConfigReaderDelegate.validateItemType(BindingConfigReaderDelegate.java:37)[176:org.openhab.core.compat1x:2.0.0]
at org.eclipse.smarthome.model.item.internal.GenericItemProvider.internalDispatchBindings(GenericItemProvider.java:311)[123:org.eclipse.smarthome.model.item:0.9.0.b4]
at org.eclipse.smarthome.model.item.internal.GenericItemProvider.internalDispatchBindings(GenericItemProvider.java:284)[123:org.eclipse.smarthome.model.item:0.9.0.b4]
at org.eclipse.smarthome.model.item.internal.GenericItemProvider.processBindingConfigsFromModel(GenericItemProvider.java:167)[123:org.eclipse.smarthome.model.item:0.9.0.b4]
at org.eclipse.smarthome.model.item.internal.GenericItemProvider.modelChanged(GenericItemProvider.java:347)[123:org.eclipse.smarthome.model.item:0.9.0.b4]
at org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl.notifyListeners(ModelRepositoryImpl.java:207)[122:org.eclipse.smarthome.model.core:0.9.0.b4]
at org.eclipse.smarthome.model.core.internal.ModelRepositoryImpl.addOrRefreshModel(ModelRepositoryImpl.java:120)[122:org.eclipse.smarthome.model.core:0.9.0.b4]
at org.eclipse.smarthome.model.core.internal.folder.FolderObserver.checkFile(FolderObserver.java:272)[122:org.eclipse.smarthome.model.core:0.9.0.b4]
at org.eclipse.smarthome.model.core.internal.folder.FolderObserver.access$1(FolderObserver.java:265)[122:org.eclipse.smarthome.model.core:0.9.0.b4]
at org.eclipse.smarthome.model.core.internal.folder.FolderObserver$WatchQueueReader.processWatchEvent(FolderObserver.java:146)[122:org.eclipse.smarthome.model.core:0.9.0.b4]
at org.eclipse.smarthome.core.service.AbstractWatchQueueReader.run(AbstractWatchQueueReader.java:122)[98:org.eclipse.smarthome.core:0.9.0.b4]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_111]
@Kai if this is supposed to be working, I would open an issue on github?