I too have to agree with Mecky. I too spend an hour or two adding items to the cloud setup, adding dummy triggers and scratching my head as to why it’s not appearing on myopenhab. I hope we can get more Foundation members involved in this issue as I (and many, many others) chose OpenHAB believing it to be the superior automation platform. It surely was a few years ago. I want it to be that again and hope we can find a way to get this service back as we are definitely falling behind Home Assist in this regard.
For better or worst the people on this platform chose it because OpenHAB had the services and bindings they needed, its not good enough to simply shrug your shoulders and list a few excuses, why we should be satisfied with less.
Would it not be more productive to try and find a solution rather than see this system fall apart bit by bit?
What do you think the volunteer actually does? (if you would have read this whole thread you would know who this is) In order to keep the openHAB cloud service working in generell, the IFTT Integration had to be shutdown. The observed overload was caused from that part.
Since this is an opensource project it can improve only if volunteers improve it. Can you contribute in any way?
How should this help ? The Foundation is not responsible or involved in any development, it is “just” supporting the project.
Like @opus wrote, we need volunteer developers who could assist on those issues.
And fore those asking for a paid cloud service, setup yourself a myopenHAB instance, instructions can be found here or on github, attach it to IFTTT and you have your very own paid service whithout any trouble regarding to much traffic.
Just an FYI that @digitaldan has been working on a solution, which is stated in this thread and referenced in numerous places. I don’t blame you for not reading the whole thing, but you only needed to backtrack 20 posts to find it, rather than assuming no one is trying to fix the issue.
I get that it’s frustrating when things aren’t working, particularly for those of us who don’t have the expertise to contribute to development. However, I think it’s an unnecessary leap to say that the system is falling apart. Since this issue was identified six weeks ago, people have implemented their own workarounds. Meanwhile, there have been lots of other positive developments, such as the release of 2.5 M2. So, let’s just keep things in perspective.
It took a hours for me to understand why my items are not appearing at myopenhab.org, before I find this thread. I’ve checked all settings many times, switched items on/off, cleared cache, investigated tons of debug logs.
Guys, can anyone add a notice at “Items” page to not confuse members? It’s a not a obvious that someone disabled this feature for new items.
Not pushing, as I know how hard this must be to unravel and fix, but do we know any more news on this?
Are we talking soon or is it looking more like never? I’m kind of in a holding pattern for a number of things that use IFTTT webhooks that I want to integrate but can’t.
I’d rather hold out for the official OH cloud service than work on running my own but an update would help out…
Hi,
Same problem here. I also spent a lot of hours wondering why new items didn’t get published to myopenhab.org before finding this thread. Please, add a notice on myopenhab.org’s items page so that it doesn’t happen to more people.
If I understood it correctly, what brings the high load is the item updates to IFTTT to use them as triggers.
While it isn’t fixed, can the item exposing to myopenhab.org be re-enabled, so that sending commands from IFTTT to myopenhab.org new items works?
Thank you for your hard work!
Regards.
I have. That’s why I said NEW items, not just items.
My old IFTTT applets are working (i just send commands from IFTTT), but I can’t publish new items to myopenhab.org, so I can’t set up new applets that send commands to new items.
I might be missing something here…and hopefully I am as it means I can crack on…
I use IFTTT webhooks for a load of different things - all work great - but when creating them, either to send or receive, you need to use an exposed variable on OH cloud. Now, all of my originally exposed variables are available and subsequent OH rules work fine, but since OH cloud had this issue I can’t expose any new items, which means I can’t write new IFTTT webhooks as I have no variables to use???
Are you saying using that URL method bypasses the need to expose variables?
Hi @mgbowman,
I knew this, but that way you have to give IFTTT your myopenhab user and password, giving access to all your items, not only exposed ones.
But thank you for your interest, anyway.
Google Assistant doesn’t read exposed items, but it does require the cloud connector to be functioning. So if you’re only using GA, then you don’t need to expose any items via PaperUI.
The key here is that you need to have your items tagged and labelled in text-based .items files. There’s currently no way to do that in PaperUI. If you’re already using .items files, then ALL of your items must have labels…not just the ones that you want GA to see.
Yes. I came across this thread with a new OH installation and the need for IFTTT (it’s the only supported platform by my sleep / bed sensors). It works for me and my two items are not list in OH.
The cloud connector simply exposes the REST API via https://myopenhab.org so you can interact with any of your items.
I think that was mentioned much earlier in this thread or another one. I didn’t understand what the person was saying at first, because I habitually include labels on all of my items (so it didn’t affect me).
Please report back if this solves your problem. I haven’t tested it myself, but if it is the issue then I think the docs could be edited for clarity.
I’ve always received “unable to update settings. Please check connection” without any details at my side or at myopenhab.org. I’ve found that one of my items has 2 tags (“Lighting”, “Switchable”):
I’ve removed one tag and everything connected ok now! GA is working after many hours of debug!!!
I can be wrong, but this item line was generated by home builder.
It’s a simple issue, but unfortunately error handling is so awful that it’s not possible to understand what’s wrong
Russel, thanks for your help. It was valuable note that items are not required to be “exposed” to cloud to work with GA.
