Is it solved? I am facing this same issue?
Hi @Sudipta_Ghorui. At the moment, you can’t expose new items to PaperUI. This had to be turned off due to database issues that were crashing myopenhab.org.
If your goal was to use a system like IFTTT, then you unfortunately won’t have any luck at the moment. However, you shouldn’t need to expose items via PaperUI for Alexa or Google Assistant to work, since they use tags in the item definitions.
Thanks @rpwong for the quick response.
I got it. No problem I can leave without IFTTT. I was just wondering if I am doing anything wrong.
Actually, you can integrate OH with IFTTT without exposing Items using the Webhooks channels. IFTTT can both send (through myopenhab.org) and receive HTTP calls . You will have to use basic auth in the URL for the calls to myopenhab.org though.
Hi,
as I’m facing the same issue: Is it planned to be reactivated again in the future? If so, will it be published in this thread?
Thanks for your help and best regards
Also, @wsd33904 just wrote this post:
How To: Integrate Custom openHAB Cloud with IFTTT
It will probably be reactivated, but only if/when the experts can figure out how to prevent it from killing myopenhab. It’ll likely be discussed in the “Myopenhab not reachable” thread linked above, so that’s the one to follow.
Is there any progress on this?
My IFTTT applets also don’t work anymore.
Hello!
I’ve also had the same problem, and I was using almost a year old nightly because of this, but, few days ago I’ve updated OH to the latest nightly, and IFTTT applets seams to work with it. Maybe you could try updating and see if yours are working too.
Best regards,
Davor
Hi, thank you for your answer.
Still some questions
- I understood that this feature was disabled on cloud level and not in the openhab instance?
- are these nightly builds stable enough to use in my house?
Correct.
It depends. When updating to the latest SNAPSHOT you are updating to code that has just been merged and has not yet seen wide testing. So any given upgrade may break your particular configuration. But once installed, if nothing breaks, they run as stably as the milestones and the releases. To the stability of the snapshots really depends on how often you upgrade.
Hello!
Now I’m really confused. I was using february/march nightly (not sure of the exact build) and IFTTT worked without problems. After trying to update to August nightly (again, not sure exactly) IFTTT stopped working. After reverting to the version I’ve used previously, it worked again. If it was disabled at cloud level, why did it work with older version?
Best regards,
Davor
Is it than possible that this is working by just using a snapshot version of Openhab?
No, because, like you asked and I confirmed, the change was made on the cloud server. It doesn’t matter what you do to your openHAB. I cannot explain davorf’s experience. But it has always been the case that if you set up exposed Items before the feature was turned off, those Items would continue to work.
Is it correct that the features only work in one direction?
My Openhab Item is a “IF THIS” condition and should trigger another IFTTT service but this isn’t working anymore.
Is there a chance that IFTTT will be “turned on” again at the stable 2.5 release in december?
There is no word on when this will be turned back on. The problem is with the cloud server, not openHAB, so it is unlikely that any fix will be tied to the openHAB release.
And is it correct that the features only work in one direction?
Like mentioned before, my Openhab Item is a “IF THIS” condition and should trigger another IFTTT service but this isn’t working anymore.
In order for IFTTT to see the Item to react to it it to send a command or post update to it it must be exposed. The ability to expose new items it’s turned off.
Yes I understand that. But I have a exposed item what is not working anymore. It is an item that should trigger an IFTTT applet. Since August it is not working anymore.
Hi all,
I needed to add two more items to my list and in the process cleared the data held on openhabcloud when I found the new items were not being exposed.
Now it appears I have no items exposed for IFTTT. Is the situation still the same, that new items are not permitted to be added at the cloud level of openhabcloud?
As I have previously stated earlier in this thread I once again noticed the same issue, I cleared all the selected items in PaperUI and when I went back and looked ten minutes later it said I had 220 items selected this type of error could explain the situation described where people have exposed all there items, they did not mean to its a bug in the list selection code. Just a thought.
I am now stuck where I still need to add the two new items and not sure if openhabcloud is a viable option.
Thanks to anyone that can clarify.
Regards
Correct, it’s still not possible to expose items. At this point, I don’t think IFTTT is going to come back, unfortunately.
What are you using IFTTT to accomplish? Perhaps we can help you come up with an alternative solution.