Skip to content
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

client.get_setup() - Different responses with Cloud and Local API #1183

Open
Eridani78 opened this issue Mar 24, 2024 · 2 comments
Open

client.get_setup() - Different responses with Cloud and Local API #1183

Eridani78 opened this issue Mar 24, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Eridani78
Copy link

Running client.get_setup() with the cloud API on a Somfy TaHoma server, I get the first item
"id": "SETUP-xxx-xxxx-xxxx"
which seems to be correct.

Running client.get_setup() with the local API on the Somfy local server, I get the first item
"id": "_CountingAttr(counter=82, _default=None, repr=<function obfuscate_id at 0x7fff295e1580>, eq=True, order=True, hash=None, init=True, on_setattr=None, alias=None, metadata={})"
making the response difficult to exploit as a Json string.

I suspect this behavior not as expected ?
Could you please advise .
Thanks

@iMicknl
Copy link
Owner

iMicknl commented Mar 24, 2024

I would need to look into this, but id is not present on the Local API.

@iMicknl
Copy link
Owner

iMicknl commented Jun 1, 2024

What is your use-case here and can you share a code snippet of what you are trying to achieve?

@iMicknl iMicknl added the bug Something isn't working label Jun 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants