NLV module: how to control slat tilt (orientation) via API?
Hello,
I have wired venetian blind modules (type NLV) connected via a Magellan gateway. In the Home+Control app I can see and control both the position level and the slat tilt angle — two separate controls. Everything works fine in the app.
I would like to do the same via the REST API, but I cannot figure out how.
`GET /api/homestatus` returns only position fields for my NLV modules — no orientation fields at all:
json
{
"type": "NLV",
"current_position": 50,
"target_position": 50,
"target_position:step": 1
}
According to a community post where Leslie (Community Manager) shared internal documentation
a BSO-calibrated module should also return fields like current_orientation_float, target_orientation_float, etc.
When I try `POST /api/setstate` with `target_orientation_float`, the API rejects it:
json
{
"error": {
"code": 21,
"message": "property /home/modules/0: should NOT have additional properties ['target_orientation_float']"
}
}
My questions:
1. What is the correct API call to control slat tilt on an NLV module?
2. Why does `homestatus` not return orientation fields, even though the app shows tilt control?
3. Is there a specific calibration step that needs to happen first to enable this in the API?
Thank you!
Comments
4 comments
Hello,
It looks like an unwanted regression in the 3rd party API. I asked for more information to the Product Manager, I'm now waiting from a feedback from the teams
I'll tell you once I know more
Have a good day,
Leslie - Community Manager
Hi Leslie,
Thank you for investigating — and for clarifying that this is an unwanted regression in the public API.
Just to confirm I understand correctly: Home+Control is Netatmo's own official app, not a third-party integration, right? So the regression affects only the public REST API (used by external developers), while the internal protocol that Home+Control uses still works fine — which is why tilt control works in the app but not via the API. Is that correct?
To help the team reproduce this, here is my exact setup:
Gateway: Magellan (Legrand)
Modules: 9× NLV (wired venetian blinds / BSO)
appliance_type reported by the API: "orientable_sun_shade" — the gateway correctly identifies these as BSO
Home+Control app: tilt control works perfectly (both level and slat angle)
GET /api/homestatus: returns only current_position, target_position, target_position:step — no orientation fields whatsoever
POST /api/setstate with target_orientation_float: rejected with error code 21 ("should NOT have additional properties")
The gateway and firmware clearly support tilt — the data just doesn't surface through the public API.
Is there anything I can provide to help the team debug this (firmware version, gateway logs, etc.)? And do you have a rough idea of when this might be resolved?
Thank you!
Hello,
Just to confirm I understand correctly: Home+Control is Netatmo's own official app, not a third-party integration, right? So the regression affects only the public REST API (used by external developers), while the internal protocol that Home+Control uses still works fine — which is why tilt control works in the app but not via the API. Is that correct? <= Yes, perfect sum up :)
Concerning the fix, I followed up with the teams concerning this, but I'm still waiting for more information
Have a good day,
Leslie - Community Manager
Hello,
Any feedback on when this API implementation is back to the public 3rd Party inegrations? This will be of very good use specially with the summer approaching.
Thank you,
Gonçalo
Please sign in to leave a comment.