I am using a Shelly1 in order to get back the positon of the manual external switch. This takes somethimes up to one minute.Is there any possibility to increase the speed of feedback or force an immediate feedback.
Which branch are you using? master or snapshot? @igi and I saw API timeouts when using both event sources (button+output) and pressing both buttons on a 2.5 at the same time. I saw something similar with the Shelly1. We tried to work around by not setting the button event url, but that doesn’t solved the problem. Nevertheless this change was active in the snapshot for several days and has been removed in the latest snapshot-build.
If you experience this with the latest snapshot build oder the master branch I need a TRACE Log to see what happens.
Reducing the status interval increases the polling, which doesn’t make sense to catch the button or output events. You could verify in the Web UI if they are set correctly after the binding has started, both have to point to your OH system.
@markus7017 Considering the huge interest in this binding (and especially the Shelly devices), I wonder, why you didn’t yet create a PR for it. Note that PRs are automatically built and published, so people can always get the latest jar very easily - no need to manually publish it anywhere else. Btw, the forum here is not meant as a storage for binaries as this increases our backup size massively and is a burden for the maintenance of the forum in the long run. It would thus be nice, if you could refrain from it.
I think many would welcome a PR and possibly getting the binding in the official 2.5 distro release. Wdyt?
That’s the plan. However, I’m still on 2.4 so need to move to 2.5, do refactoring and then open the PR.
I removed the one post with the binary, had some special reason to do that.
@markus7017: really a fantastic job. The Bindig is very helpful and I have now made it an integral part of my openhab environment. Installation and commissioning were done quickly and ran smoothly for me.
Now I want to make the shellies (or at least some of them) usable via Alexa as well. openhab Cloud connector and Alexa Skill are set up correctly (they already worked with my self-constructed MQTT solution). The shellies added via the binding are not found by Alexa.
I have already uninstalled Cloud Connector and Skill, rebooted and reinstalled the system - no success! I have set up a completely new cloud instance - no success!
Does anyone have one or two tips what else I can do?
I didn’t used the skill so far. I prefer the HUE emulation. The Alexa devices are able to control HUE devices locally without looping through the Internet. This means there is no public access to your home (and yes, the voice sample is send to amazon). This gives at least a better feeling on the security side even knowing that Alexa itself is accessing the Internet/amazon’s cloud service.
In this case you need to flag those items, which should be exposed to Alexa/HUE (default is NO). This can be done by adding the tag Switchable or Dimmable to the item. So this setup should work and I don’t know if the skill also requires tagging the items to make them available to Alexa.
See also: https://www.openhab.org/addons/integrations/hueemulation/
