-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[openhabcloud] Issue with item exposure in #1525 #4953
Comments
here the post in our community: |
Hi @nesys I'm trying to understand the issue you mention tagging which does not have any affect with myopenhab, the only items that will report state to myopenhab will be set in Is this what you are referring to? Note that this is only really useful for IFTTT and does not have anything todo with tagging or exposing items to Alexa or Google home
I am trying to understand what those 2 PR's have to do with this issue? I just tried on my system and things seem to be working, but i'm not sure if you are running something different? |
@nesys is referring to openHAB 2.5.0-SNAPSHOT build numbers. 😉 |
Exactly. And of course I'm referring to use IFTTT with OH. But Alexa is working correctly. I know this is not related to expose items ... I was thinking that was a useful information for you in case. Also the log above seems the flow between IFTTT and OH Cloud is working correctly, the issue is between my OH and myopenhab.org |
Got it , i understand now. I'll take a look, i ended up downgrading until the UI migrations are finished, I'll upgrade my instance a take a look. |
thanks for your support @digitaldan ... in facts from OH #1502 I see this issue (still in current OH #1534) |
Hmm, so the cloud binding is no loner able to get the stored configuration from the OH core as it used to. The config is empty and this line return a null/empty object: even though my config shows differently
@wborn any ideas on what might have changed in the core? |
@wborn Could this be related to this commit? It looks ok to me, but it does seem like the binding can not find its config service. openhab/openhab2-addons@2ef23f0 |
What might help is adding |
let me give it a try |
👍 Yep, that did it, PR coming.... |
…openhab#4953 Signed-off-by: digitaldan <[email protected]>
…#4953 (#4991) Signed-off-by: digitaldan <[email protected]>
I can confirm, issue solved in OH #1536 |
👍 |
…openhab#4953 (openhab#4991) Signed-off-by: digitaldan <[email protected]> Signed-off-by: Pshatsillo <[email protected]>
…openhab#4953 (openhab#4991) Signed-off-by: digitaldan <[email protected]> Signed-off-by: Maximilian Hess <[email protected]>
After upgrading from #1502 to #1515 and after, the item exposure seems buggy.
In facts:
Expected Behavior
switch item changed via classic UI should be also changed in https://myopenhab.org/items
Current Behavior
Nothing happens. Also if I delete all items and events, events are recreated correctly, items not (after the requested action to see the item in myopenhab.org). I've also canceled and re-created from scratch my myopenhab account ... same issue
log:
2019-02-21 09:06:22.093 [WARN ] [io.openhabcloud.internal.CloudClient] - Received command from openHAB Cloud for item 'Andrea_Presence_IFTTT', which is not exposed.
So the recipe in IFTTT is working as expected. The issue is on OH side.
Possible Solution
That is working in #1502. Maybe some changes in between (but before #1515) need to be verified
Steps to Reproduce (for Bugs)
Context
Trying to work with exposed items and IFTTT recipes
Your Environment
My current configuration is openhabian #1525 on vmware VM.
The text was updated successfully, but these errors were encountered: