First of all, thank you for developing this integration.
Do you know it there has been any progress on this subject since your last post?
I opened a Pull Request to add the integration. But I am still waiting for a second code review before this can be merged. You can follow it’s progress on
1 Like
While waiting for the official integration to be available, my custom component GitHub - astrandb/senz_hass: SENZ WiFi integration for Home Assistant can be used. It is fully functional and can be installed with HACS.
You will need a client_id and a client_secret from Raychem/Senz to access the API. Can be requested from the manufacturer at https://api.senzthermostat.nvent.com/ Ask for credentials for use with integration for Home Assistant. Unfortunately there is no self-service function but they normally respond within a day or two.
I tried this and was given a form to fill out. I have no idea what to enter, can you please help me?
Definition of the project - Give a short description of the project
Grant types/flows - Define which grant type you need (chose one of the 3 types below):
- Implicit
- Authorization code
- Hybrid
Offline access - Yes or No, depending if you need to work with a refresh token
ID - This is the Client ID, you will use this to identify yourself with
Client Name - This is the name that will be displayed to the end user on the consent page.
Example: The “Client Name” is asking to access your account on your behalf.
Redirect Uris - Defines the allowed redirect URIs this Client ID is allowed to receive access token on.
Multiple can be added in order to support a test and a live version of the program
Post logout redirect Uris - If the external application supports openid logout. You can set-up the redirect URIs the end user will be redirected to after logout from the SENZ WIFI Identity service.
Multiple can be added in order to support a test and a live version of the program
Allowed CORS Origins - If the external application is a website, it needs to be a verified CORS origin. This allows the website to talk to the SENZ WIFI Identity service
Company Name - This is for us to be able to contact you in case needed
Contact Name
Contact Info
Access to SENZ WIFI - Describes the fact that your API development will access the thermostats and what it will do with this access.
Description - Describes what the integration is doing and how this will affect the thermostat in the end user’s account
Permission - Describes that by allowing the access, the end user is granting permission to connect with his thermostats
@Schlbuditz Please see an example here senz_hass/application_form.md at main · astrandb/senz_hass (github.com)
1 Like
Thank you Åke!
A small update: Paulus has set up account linking for senz, note that core version 2022.3.0 or higher is required.
@milanmeu Do you think it is possible for the custom component to use the account linking? If yes, what changes are needed.
You can already use it if you trick the cloud component into thinking that you are already using version 2022.3.0. To do this, you need to add the following to config_flow.py:
from awesomeversion import AwesomeVersion
from homeassistant.components.cloud import account_link
account_link.CURRENT_VERSION = AwesomeVersion("2022.3.0")
And add the code above or the following to __init__.py:
from homeassistant.components.cloud import account_link
account_link.HA_VERSION = "2022.3.0"
1 Like
Thank you, it works like a charm!
Hmm … when adding the integration and the nvent webpage tells me this:
“Sorry, there was an error: unauthorized_client”
Any ideas?
You usually get this message when something is wrong with your client_id, client_secret, username or password.
When you update your HA to 2022.3 (release expected tomorrow) you don´t need your own client_id/client_secret anymore. Probably easier to troubleshoot then.
I upgraded to beta 2022.3.0b4 yesterday. I have the 0.0.5 from your rep.
… hmm, i just reinstalled the integration via HACS but now I get this:
“The component is not configured. Please follow the documentation.”
It doesn’t work with 2203-beta you need to wait for final release (or add the lines suggested above.)
Ah. Great.
Thanks, I finally got it to work, some info for other people running into the unauthorized_client issue.
You will need to send your redirect URL to Raychem/Senz in order for this to work, if your URL doesn’t match the one Senz have you will get the unauthorized_client.
Maybe good to add a note for that in the readme?
1 Like
Just a note to thank everyone who worked on this integration. Worked great for me out of the box starting with the 2022.05 release.
However, around the time I upgraded to HA 2022.6.3 (I think, although it may be unrelated to the upgrade), it suddenly started failing with the following error, which has persisted since then (over several days and several HA restarts):
ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Home Assistant Cloud for senz
File "/usr/src/homeassistant/homeassistant/components/senz/__init__.py", line 100, in async_setup_entry
account = await senz_api.get_account()
File "/usr/local/lib/python3.9/site-packages/aiosenz/api.py", line 35, in get_account
File "/usr/local/lib/python3.9/site-packages/aiosenz/auth.py", line 55, in _request
File "/usr/src/homeassistant/homeassistant/components/senz/api.py", line 24, in get_access_token
aiohttp.client_exceptions.ClientResponseError: 500, message='Internal Server Error', url=URL('https://account-link.nabucasa.com/refresh_token/senz')
Is it just me or affecting everyone?
Late reply but I have the same issue
I only get two option for this integration “AUTO” and “HEAT”, why no more entity? I want to set the exact temperature via HA.
1 Like