-
Notifications
You must be signed in to change notification settings - Fork 0
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
TypeError: list indices must be integers or slices, not str #1
Comments
At first glance there doesn't seem to be any realtime information for the device you have connected in Eplucon. Could you tell me what devices you have? I'll try to put some more debugging logs in for version 1.1.0 |
I've got a th-TOUCH connected. Whenever I login to the Eplucon portal I can see the information about this device. |
I've released 1.1.0 Beta could you try this and send me the output of the debug? There should be something along the lines of the following:
|
Please find the log attached. |
Alright so from the log it seems that you actually have 2 devices linked in your Eplucon and 1 is working fine (the heat_pump) and another one called I'm not sure what devices a I think I should be able to extend the error handling a bit and remove devices that we get API errors from or maybe just support devices with the type |
The |
I see. In the current state the integration basically only supports the realtime info API which seems to only work with a heat pump. I will update the code to match this. I might build support for other types later on but I would first need to setup some mocking tests for the API and need access to a few real API calls where actually data is returned for those devices as the API docs don't go into detail about what they return ( it only states it will return |
I can give you access to my API of that helps. |
If you could send it to me that would be great! |
Please update to v1.2.1 this should be fixed now. |
Version: 1.0
After adding the integration and adding my API key I encounter the following error
The text was updated successfully, but these errors were encountered: