Preview and Beta: Amazon Echo Control

Hi @J-N-K,

I was pulled away for a moment but finally had a chance to test and used the newest j2 version of the binding from your link above. Potentially promising but strange behavior happened when I loaded this newest jar into openHAB:

I will try cleaning cache once again, rebooting.

2020-06-22 13:57:52.389 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Downstairs_Bedroom
2020-06-22 13:57:52.396 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Upstairs_Den
2020-06-22 13:57:52.410 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Upstairs_Bedroom
2020-06-22 13:57:52.420 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Living_Room
2020-06-22 13:57:52.428 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Kitchen
2020-06-22 13:57:52.434 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Upstairs_Lights
2020-06-22 13:57:52.440 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Downstairs_Lights
2020-06-22 13:57:52.451 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:All_Lights
2020-06-22 13:57:52.459 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Foyer
2020-06-22 13:57:52.465 [INFO ] [nal.smarthome.SmartHomeDeviceHandler] - initializing amazonechocontrol:smartHomeDeviceGroup:0558c345:Upstairs_Bathroom
2020-06-22 13:57:52.554 [ERROR] [org.openhab.core.model.thing        ] - bundle org.openhab.core.model.thing:2.5.0 (178)[org.eclipse.smarthome.model.thing.internal.GenericThingProvider(155)] : The addThingHandlerFactory method has thrown an exception
java.lang.IllegalArgumentException: Duplicate channels amazonechocontrol:echo:0558c345:echo1:player
	at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:165) ~[?:?]
	at org.eclipse.smarthome.core.thing.util.ThingHelper.ensureUniqueChannels(ThingHelper.java:141) ~[?:?]
	at org.eclipse.smarthome.core.thing.binding.builder.ThingBuilder.withChannels(ThingBuilder.java:87) ~[?:?]
	at org.eclipse.smarthome.core.thing.binding.ThingFactory.createThing(ThingFactory.java:92) ~[?:?]
	at org.eclipse.smarthome.core.thing.binding.BaseThingHandlerFactory.createThing(BaseThingHandlerFactory.java:332) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.getThingFromThingHandlerFactory(GenericThingProvider.java:507) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.getThingFromThingHandlerFactories(GenericThingProvider.java:490) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.createThing(GenericThingProvider.java:433) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.lambda$24(GenericThingProvider.java:898) ~[?:?]
	at java.lang.Iterable.forEach(Iterable.java:75) ~[?:1.8.0_252]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.createThingsFromModelForThingHandlerFactory(GenericThingProvider.java:900) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.lambda$21(GenericThingProvider.java:844) ~[?:?]
	at java.util.concurrent.ConcurrentHashMap$KeySetView.forEach(ConcurrentHashMap.java:4649) ~[?:1.8.0_252]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.thingHandlerFactoryAdded(GenericThingProvider.java:846) ~[?:?]
	at org.eclipse.smarthome.model.thing.internal.GenericThingProvider.addThingHandlerFactory(GenericThingProvider.java:830) ~[?:?]
	at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source) ~[?:?]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_252]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_252]
	at org.apache.felix.scr.impl.inject.methods.BaseMethod.invokeMethod(BaseMethod.java:228) ~[bundleFile:?]
	at org.apache.felix.scr.impl.inject.methods.BaseMethod.access$500(BaseMethod.java:41) ~[bundleFile:?]
	at org.apache.felix.scr.impl.inject.methods.BaseMethod$Resolved.invoke(BaseMethod.java:664) ~[bundleFile:?]
	at org.apache.felix.scr.impl.inject.methods.BaseMethod.invoke(BaseMethod.java:510) [bundleFile:?]
	at org.apache.felix.scr.impl.inject.methods.BindMethod.invoke(BindMethod.java:42) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.DependencyManager.doInvokeBindMethod(DependencyManager.java:1813) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.DependencyManager.invokeBindMethod(DependencyManager.java:1788) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.SingleComponentManager.invokeBindMethod(SingleComponentManager.java:435) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:325) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.DependencyManager$MultipleDynamicCustomizer.addedService(DependencyManager.java:294) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1216) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.customizerAdded(ServiceTracker.java:1137) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.trackAdding(ServiceTracker.java:944) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ServiceTracker$AbstractTracked.track(ServiceTracker.java:880) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ServiceTracker$Tracked.serviceChanged(ServiceTracker.java:1168) [bundleFile:?]
	at org.apache.felix.scr.impl.BundleComponentActivator$ListenerInfo.serviceChanged(BundleComponentActivator.java:125) [bundleFile:?]
	at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:920) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:469) [org.eclipse.osgi-3.12.100.jar:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:906) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager$3.register(AbstractComponentManager.java:892) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.RegistrationManager.changeRegistration(RegistrationManager.java:128) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.registerService(AbstractComponentManager.java:959) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.activateInternal(AbstractComponentManager.java:732) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.enableInternal(AbstractComponentManager.java:666) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.AbstractComponentManager.enable(AbstractComponentManager.java:432) [bundleFile:?]
	at org.apache.felix.scr.impl.manager.ConfigurableComponentHolder.enableComponents(ConfigurableComponentHolder.java:665) [bundleFile:?]
	at org.apache.felix.scr.impl.BundleComponentActivator.initialEnable(BundleComponentActivator.java:338) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator.loadComponents(Activator.java:382) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator.access$200(Activator.java:49) [bundleFile:?]
	at org.apache.felix.scr.impl.Activator$ScrExtension.start(Activator.java:264) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.createExtension(AbstractExtender.java:196) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:169) [bundleFile:?]
	at org.apache.felix.scr.impl.AbstractExtender.modifiedBundle(AbstractExtender.java:49) [bundleFile:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:482) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.customizerModified(BundleTracker.java:415) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.AbstractTracked.track(AbstractTracked.java:232) [osgi.core-6.0.0.jar:?]
	at org.osgi.util.tracker.BundleTracker$Tracked.bundleChanged(BundleTracker.java:444) [osgi.core-6.0.0.jar:?]
	at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:908) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:168) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.Module.publishEvent(Module.java:476) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.container.Module.start(Module.java:467) [org.eclipse.osgi-3.12.100.jar:?]
	at org.eclipse.osgi.internal.framework.EquinoxBundle.start(EquinoxBundle.java:383) [org.eclipse.osgi-3.12.100.jar:?]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundle(DirectoryWatcher.java:1260) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.startBundles(DirectoryWatcher.java:1233) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:520) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:365) [bundleFile:3.6.4]
	at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:316) [bundleFile:3.6.4]

Also, my machine just informed me there are updates available and it wants to update openHAB from openhab2 (2.5.6-1 => 2.5.6-2), so I will let that happen now as well.

Already found the duplicate channels issue. That was an error during merge where some channels got duplicated. Will provide a new version ASAP.

I just updated openHAB overall, cleaned cache, and restarted and the biggest issue I’m having is it won’t recognize my Amazon Account Thing/shows it as “uninitialized” in PaperUI, and shows “No Amazon account thing.” at the configuration URL.

When I try to delete the “uninitialized” Amazon Account thing in PaperUI, it won’t let me delete it and says “ERROR: 409 - Conflict” and then in the log says:

2020-06-22 14:52:09.454 [INFO ] [st.core.internal.thing.ThingResource] - Received HTTP DELETE request for update at 'things/amazonechocontrol:account:0558c345' for an unmanaged thing 'amazon
echocontrol:account:0558c345'.

Exact same issues for me - showing “no account thing created." Does show an Amazon Account Thing in PaperUI, but it’s showing as “uninitialized” and refuses to let me delete it, giving: “ERROR: 409 - Conflict”.

I have cleaned cache/tmp and have rebooted but still the problem persists.

If it’s unmanaged (which means it’s defined in a .things file) you can’t remove it from PaperUI. I’m not sure that error is 100% correct.

I have updated the -f2.jar once more, this should solve the account initialization issue (at least it works in my setup) and also the duplicate channels issue.

I just dropped your new .jar file in and things are much, much better!! :blush:

My “LastVoiceCommand” feature is FINALLY working again! :heavy_check_mark: :tada:

The Amazon Account thing is online and the /amazonechocontrol configuration URL is showing all my my devices correctly, and shows them as defined. :heavy_check_mark:

The “Smart Home Devices” are showing as “Online” in PaperUI and in the log :heavy_check_mark::grinning:
However they aren’t responding when I try to turn them on or off. :x::slightly_frowning_face:

So much closer though! I’ll try a reboot…

I need some logs. Maybe set to DEBUG so you don’t get flooded too much and see if something happens when you try turning on or off.

I’ll see what I can find for you. I just set it to TRACE and tried to have it turn some Amazon Echo Control lights on and off, but nothing appeared in the log. I’ll try DEBUG now and see what I get…

Just to make sure, we are talking about the same thing: you say something like „Alexa, set the brightness of xyz to 50%“ and nothing happens? Can you show a thing definition for that? Thanks for your cooperation, I think we can solve that last issue, too.

Yes, exactly! I’m keeping it simple though and am just trying with a simple “on/off” switch. I’ve tried verbally asking Alexa to turn the switch on and off through the Echo Dot, and I’ve also tried using the API to send a command directly to the switch. The log shows the device and shows the requested command but nothing happens. And there are no errors in the log, even with it set to TRACE.

Here are my configuration files for a sample light:

smarthome.things

Bridge amazonechocontrol:account:0558c345 "Amazon Account" @ "Accounts" [discoverSmartHome=2, pollingIntervalSmartHomeAlexa=30, pollingIntervalSmartSkills=120]
{
   Thing smartHomeDevice      Upstairs_Den_Light "Upstairs Den Light" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjk2ZjZhMmM4LTczNTQtNGRiYS05NzA3LWM4OTA1MjAyOTI5YSIsInN0YWdlIjoibGl2ZSJ9_10002cee76"]
}

smarthome.items

Switch Upstairs_Den_Light "On/Off" { channel="amazonechocontrol:smartHomeDevice:0558c345:Upstairs_Den_Light:powerState" }

When I turn this device ON or OFF, the openhab.log file shows nothing, no errors. And the events.log file shows the command, and then immediately changes the command to “NULL” but I think it has always done that.

events.log

2020-06-22 16:11:27.219 [ome.event.ItemCommandEvent] - Item 'Upstairs_Den_Light' received command ON
2020-06-22 16:11:27.221 [nt.ItemStatePredictedEvent] - Upstairs_Den_Light predicted to become NULL

Ok. So if the log shows the command, that is already very good. IMO that is the harder part. Can you show that part of the log?

How can you send via the API? I guess I can do that without an Echo and debug it locally.

Here’s a screenshot of my log.
I just tested the item “Stairs_Light_Switch”. You can see where the ON/OFF command is captured in the events.log (on top) but the openhab.log (bottom) doesn’t show any acknowledgement of the on / off command.

It might be a little confusing, as to why there are two items for my stairway light, “Stairs_Light” and “Stairs_Light_Switch”… This is because that item is an RF controlled switch and has only one signal that is sent for both “ON” and also “OFF.” So technically I could just repeat “turn ON the stairs light” over and over and it would turn on and off and on and off… To keep the device from becoming backwards (for example, if the item is “OFF” in the system but the physical light is actually on) I created a dummy item (“Stairs_Light”) which uses a rule to only send the “Stairs_Light_Switch” signal when it is supposed to. So if “Stairs_Light” is OFF and I ask Alexa to turn it OFF, it won’t send the “OFF” command to “Stairs_Light_Switch” because it is already off. Stairs_Light_Switch is the actual device I am trying to control with the AmazonEchoControl binding…

I can’t just pick any light as an example because remember these devices have all been originally configured with Alexa directly, through the Alexa app, and so if I ask her to turn one of them on or off directly she will do so, but openHAB isn’t involved. This is why I chose the “Stairs_Light_Swtich” item as an example, because it’s an odd-one-out/isn’t one that Alexa natively controls but is configured through openHAB.

Sorry if I’m not making sense. Basically, right now the devices are defined but they’re not responding or doing anything when a voice command is made, and no errors are logged.

This is a very good idea - you should be able to! To control the device directly through the API, I can simply navigate to a url such as this in my browser:

http://localhost:8080/basicui/CMD?Stairs_Light_Switch=ON
http://localhost:8080/basicui/CMD?Stairs_Light_Switch=OFF

or / also

http://localhost:8080/classicui/CMD?Stairs_Light_Switch=ON
http://localhost:8080/classicui/CMD?Stairs_Light_Switch=OFF

Edit: For testing, if you already have an amazon.com (or, amazon.de) account you could also install the Alexa app onto your smartphone and could then add a test smart home device if you have any wifi-controlled items in your home already (I assume you must, because you use openHAB!) (like a TP-link or Hue, etc.) you could link that skill in the Alexa app on your phone or also use the Alexa web interface to add the skill and connect your test device. Then you can talk to Alexa using your smart phone - just open the app and touch the blue circle at the bottom of the screen.

Here are a few additional ways you can talk to Alexa without having a physical Echo device. You could actually even then register your virtual/web Alexa as an Echo Dot in openHAB. Any time you access/login to Alexa somewhere, Amazon adds a device to your account & creates a serial number, etc. which will show in the /amazonechocontrol binding URL - see my screenshot from earlier as an example Many/most of the features will work in openHAB if you use your virtual/web Alexa (like “LastVoiceCommand” for example).

The latest binding has now solved the “No Account Thing Created” issue for me as well. Thanks!!!

The alexa guard feature is still not working which is unfortunate, but not the end of the world.

I may have figured something out! Normally, the Amazon Echo Control binding shows when you scan for new items in your PaperUI Inbox. But the binding is missing/not showing up at all, and won’t let you scan for new items. Maybe this is why we aren’t able to control the devices yet - something isn’t right on the back-end.

Edit: Actually - this is probably much more helpful… Good news! Some of the AmazonEchoControl Smart Home Devices are actually working! I went to the “Control” tab of PaperUI and all the AmazonEchoControl “Smart Home Device Groups” are working properly! They show as online in the log as well. Here’s a screenshot of the device groups in my PaperUI “Control” section. So however you have the Smart Home Device Groups currently configured in the .jar binding is the correct way! Maybe you can look at that that to see what is not correct for the regular devices…

Here’s my .things file, showing how I have Device Groups and Devices configured as an example:

Bridge amazonechocontrol:account:0558c345 "Amazon Account" @ "Accounts" [discoverSmartHome=2, pollingIntervalSmartHomeAlexa=30, pollingIntervalSmartSkills=120]
{
   Thing smartHomeDevice      Upstairs_Den_Light "Upstairs Den Light" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjk2ZjZhMmM4LTczNTQtNGRiYS05NzA3LWM4OTA1MjAyOTI5YSIsInN0YWdlIjoibGl2ZSJ9_10002cee76"]
   Thing smartHomeDevice      Bathroom_Fan "Bathroom Fan" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjAyOWU2NGFhLTk5OGQtNDY5NC05Nzk5LWIwZGU0ZjZiZWI3MCIsInN0YWdlIjoibGl2ZSJ9_01861e9f999055d8d7efa0f46b0f76f0"]
   Thing smartHomeDevice      Upstairs_Den_TV "Upstairs Den TV" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjAyOWU2NGFhLTk5OGQtNDY5NC05Nzk5LWIwZGU0ZjZiZWI3MCIsInN0YWdlIjoibGl2ZSJ9_0129551c9bdc5fae5ef7a521c8059e0c"]
   Thing smartHomeDevice      Stairs_Light_Switch "Stairs Light Switch" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjAyOWU2NGFhLTk5OGQtNDY5NC05Nzk5LWIwZGU0ZjZiZWI3MCIsInN0YWdlIjoibGl2ZSJ9_01ebc627ee74ce8c19fa409993bb0af7"]
   Thing smartHomeDevice      tvvol "tvvol" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjAyOWU2NGFhLTk5OGQtNDY5NC05Nzk5LWIwZGU0ZjZiZWI3MCIsInN0YWdlIjoibGl2ZSJ9_01672ff46cc9234677c8e362a6878ea9"]
   Thing smartHomeDevice      Upstairs_Den_AC "Upstairs Air-Conditioner" @ "Smart Home Devices" [id="SKILL_eyJza2lsbElkIjoiYW16bjEuYXNrLnNraWxsLjAyOWU2NGFhLTk5OGQtNDY5NC05Nzk5LWIwZGU0ZjZiZWI3MCIsInN0YWdlIjoibGl2ZSJ9_01ff576748f3009d744ff2f5b415c6d3"]
//  
//
   Thing smartHomeDeviceGroup      All_Lights "All Lights" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.219bf010-0436-48d1-89ea-c007992ac00c"]
   Thing smartHomeDeviceGroup      Downstairs_Lights "Downstairs Lights" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.9f03c094-9989-4782-918f-328211cef4b7"]
   Thing smartHomeDeviceGroup      Upstairs_Lights "Upstairs Lights" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.93c319b1-f0c1-4f50-90c1-4538cc9a2d76"]
//
//   
   Thing smartHomeDeviceGroup      Foyer "Foyer" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.c375d295-c145-4229-ba70-9fda92d7047b"]
   Thing smartHomeDeviceGroup      Kitchen "Kitchen" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.45b396a6-c611-4d91-b2fb-420da39a9876"]
   Thing smartHomeDeviceGroup      Living_Room "Living Room" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.97b0a4df-fab0-4857-9a11-0d8d221dcd03"]
   Thing smartHomeDeviceGroup      Upstairs_Den "Upstairs Den" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.ef22e55c-0139-4b30-8721-228bc3cf9085"]
   Thing smartHomeDeviceGroup      Upstairs_Bathroom "Upstairs Bathroom" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.9fbe6ccb-f88b-4d4d-a888-5057fd44a77a"]
   Thing smartHomeDeviceGroup      Downstairs_Bedroom "Downstairs Bedroom" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.5113f317-ef2f-4f17-a2e6-1e30542eff03"]
   Thing smartHomeDeviceGroup      Upstairs_Bedroom "Upstairs Bedroom" @ "Smart Home Devices" [id="amzn1.HomeAutomation.ApplianceGroup.A2B51JCRLL3VUJ.a4df517b-fed1-4650-bfb0-48afa74a8224"]
}

I haven’t played around much with the Alexa Guard feature yet, but I did just notice that all of my “Smart Home Device Groups” that I had setup into my smarthome.things file are in fact showing as “ONLINE” in PaperUI, and are working/are able to be controlled via openHAB! So if we can copy what’s correct in the coding for how the Device Groups things have been setup to the regular Devices and Alexa Guard and other thing types, we should be good to go!

Back in daylight again here in Australia - Ive added the new f2 binding in and I dont have thing files all paperUI - as @richaardvark said the binding doesnt seem to allow discovery, so I dont have any smart devices to see how they behave.
I did get them discovered perhaps in the f1 binding if this helps?

@J-N-K - I might have found our issue…

Comparing the existing Beta Release .jar file (2019-10-23 - which if re-installed still allows all Echo Smart Home Devices to work flawlessly, btw) against the latest updated .jar from @J-N-K (2.5.6-f2), it seems that the latest 2.5.6-f2 version is missing the Smart Home Devices thing-type definitions from within the "thing-types.xml" file inside the .jar package. This was the biggest difference between the two versions - I think this data needs to be included from the previous Beta release and updated within the new, in-process Beta working draft. This is also probably why we aren’t currently able to search for things in the PaperUI Inbox - because the Smart Home Devices thing-types are not currently defined.

See this screenshot for more details…

I have found more issues and will provide a new version soon.

1 Like

Please try <link removed, see below>

1 Like

Great news! Everything seems to be working perfectly! All devices, groups! And the “LastVoiceCommand” feature etc. are all still working perfectly! And I’m not seeing any errors at all in the log! This is so fantastic!! Thank you so so very much @J-N-K! I will turn on TRACE logging for the next hour or so and monitor it to see if anything strange happens, but as of right now it seems to be working beautifully! It loaded very quickly and everything came right online!!

:trophy::1st_place_medal::tada::tada::raised_hands:t2::clap:t2::clap:t2::clap:t2: