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

Missing Devices (Atlantic ZoneControl 2.0). #20

Open
qelanhari opened this issue May 13, 2022 · 15 comments
Open

Missing Devices (Atlantic ZoneControl 2.0). #20

qelanhari opened this issue May 13, 2022 · 15 comments
Labels
enhancement New feature or request

Comments

@qelanhari
Copy link

Hi !
I'm trying to use the Local API.
No issue using the endpoints but some of my IO devices are not returned from the local API when they are from the cloud API.
These are officially supported device (Atlantic ZoneControl 2.0) that I can control from the Tahoma App.
I can also control them via Cloud API. They are simply not returned by the local API using the /setup/devices endpoint.
I only get my Sliding Gate and my Garage Door and surprisingly my unsupported WaterHeater (Atlantic Calypso).

Thank you for the feedback.

@adriweb
Copy link

adriweb commented May 13, 2022

Not all protocols and devices are supported by the local mode.

@qelanhari
Copy link
Author

Is this a temporary restriction ?
Can we have details on the restriction critiria to know what to expect ?

@Minasu
Copy link

Minasu commented May 14, 2022

Hello,

No, the heating equipment is not seen by the local API and that is very unfortunate.

Example: #11

@vhenriet-sfy vhenriet-sfy changed the title Missing Devices in local API but ok in cloud API. Missing Devices (Atlantic ZoneControl 2.0). May 17, 2022
@vhenriet-sfy vhenriet-sfy added the enhancement New feature or request label May 17, 2022
@nyroDev
Copy link

nyroDev commented Oct 30, 2022

Hello @Somfy-Developer
Is there an ETA or similar to have all devices accessible locally please?

@iMicknl
Copy link

iMicknl commented Oct 30, 2022

+1! It would be great if all devices could be exposed, otherwise there is still need for a hybrid approach where local and cloud API are used together..

@HpNoTiQ56
Copy link

+1 : I'd loved that my atlantic electric heater could use local API.
ATM, I'm using both local and cloud integration in Home Assistant.
Any ETA or won't fix status?

@nyroDev
Copy link

nyroDev commented Dec 6, 2022

After update 2022.6.4-6, still no new devices accessible locally (at least for me)

@Quentame

This comment was marked as off-topic.

@qelanhari
Copy link
Author

This whole repo only concerns local api.

@qelanhari
Copy link
Author

After update 2022.6.4-6, still no new devices accessible locally (at least for me)

Same after the last update

@HpNoTiQ56
Copy link

Any news on this one?
Can't use local and cloud integration at the same time!

@Tronix117
Copy link

I'm also adding my voice to this. I can't understand why it's restricted this way. What is the meaning of having the need to go through the cloud when everything can be handled locally...
For now I' really starting to be regretful of choosing IO for some of my devices. So far only restrictions over restrictions due to this troublesome closed protocol (even if you say it's opened), it does not represent the future of home automation.
I hope matter compatibility will be handled in a better way

@MacDoofy
Copy link

MacDoofy commented Jan 8, 2024

@llavorel-somfy seems you are the official representative here for the Tahoma developer mode. Would you have any information on adding the climate control feature to this ?

@daahmer
Copy link

daahmer commented Jan 17, 2024

I'm also disapointed that heaters are not available on local API.
each time that Overkiz servers are unavailable or when I lose my internet connexion, I cannot pilot my heaters.
I recently changed my bridge (from cozytouch to tahoma switch) because there was local API on tahoma switch. at no time did I suspect that the APIs weren't complete.
Could you please give us some visibility on the fix for this issue please.

@Tronix117
Copy link

@llavorel-somfy hello, could you help us understand why the reason behind that ?

Is it :

  1. it's on the roadmap, not just there yet !
  2. no time/budget available to support this
  3. technicaly complicated, it's not just a filter to remove
  4. legal reasons (no need to provide further details if they can't be disclosed)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests