Peblar - CoolBlue BlueBuilt #134022
Comments
|
Hey there @frenck, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) peblar documentation |
This comment was marked as duplicate.
This comment was marked as duplicate.
|
Same problem with white-label product Logger: homeassistant.config_entries Error setting up entry Peblar for peblar |
|
@mathiasmoons Which versions are installed on your Peblar unit? |
|
@mathiasmoons Hmm that firmware version will indeed output something different (and isn't usable with this integration for sure) Is that the latest firmware version available to you? |
|
@frenck , I have same issue as @mathiasmoons but I have the normal Peblar Home with the latest firmware: |
|
@pieter-1978 on the Nevertheless, issues from @mathiasmoons are different in a way, that firmware 1.6 introduced the API this integration relies on; and he is on 1.5 |
|
@frenck , you are right🙈 mine is a bit different indeed. I do have the Peblar Home. Below the log; homeassistant.components.peblar] Unexpected exception |
|
@frenck, I was able to update the firmware to 1.6.2 Logger: homeassistant.config_entries Error setting up entry Peblar for peblar |
|
I've opened a PR to mitigate the missing Pull request: #134486 I'm pretty sure this isn't the last thing we discover; once it is available in beta, I'll do a shout-out here as I could use some help with testing against more devices. 🙏 ../Frenck |
|
@cafferata @mathiasmoons @pieter-1978 Can you please try again with Home Assistant 2025.1.0b7? ../Frenck |
|
Hi @frenck , works now, looks great I must say! I am currently using the Peblar by using the Rest API but will move to this integration later. I quickly checked the functions and the only thing I see missing is a ON/OFF switch to start/stop the charging. The slider you made for the “charge current limit” goes from 6A~16A. In order to stop the charging you must go below 6A. It would be great if we can have a switch where “OFF” is 0A and “ON” the set value of the “charge current limit”. |
|
@frenck , forgot to mention; the value of “ChargeCurrentLimitActual” is missing as well. Not the end of the world but sometimes interesting to monitor👍 |
This is actually something I want to pick up with Peblar. It sounds odd to set it to 0A to turn off charging; especially if I make it a switch, I will not be able to restore it to the previous value once the switch is turned on again. IMHO, this should be functionality in the API from Peblar directly. |
Agree with you, it is indeed strange they did not implement this in the API. |
You can't with this integration, just as one can't do it with their own web UI either. Anyways, let's get back on topic, I want to know if the issue is resolved for the OP ;) |
😉sorry for going off topic. For me the issue is resolved |
|
Hi Frenck, I also confirm that the integration is working fine here after the last update. |
|
Thank you so much for the work you’ve done so far—it’s much appreciated! I’ve just tried Beta 7 and attempted to complete the Peblar installation. Unfortunately, I ran into an issue and received the following stack trace: Logger: Error setting up entry Peblar for peblar
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 640, in __async_setup_with_context
result = await component.async_setup_entry(hass, self)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/peblar/__init__.py", line 51, in async_setup_entry
api = await peblar.rest_api(enable=True, access_mode=AccessMode.READ_WRITE)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/peblar/peblar.py", line 124, in rest_api
user = await self.user_configuration()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/peblar/peblar.py", line 235, in user_configuration
return PeblarUserConfiguration.from_json(result)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "<string>", line 4, in __mashumaro_from_json__
File "/usr/local/lib/python3.13/site-packages/peblar/models.py", line 414, in __pre_deserialize__
d["BopSourceParameters"] = orjson.loads(d.get("BopSourceParameters", "{}"))
~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
orjson.JSONDecodeError: Input is a zero-length, empty document: line 1 column 1 (char 0)I’ve double-checked the API settings and everything appears to be configured correctly. Please find a screenshot attached for your reference. Let me know if you need any additional information to troubleshoot this.
Thanks again for all your efforts! 👏🏻 PS. I should have time to debug the Python package this weekend. Let me know if there’s anything specific you’d like me to focus on. |
|
@frenck I also upgraded to beta 7, but I get the following log. Logger: homeassistant.components.peblar Unexpected error fetching Peblar Peblar version data |
|
@mathiasmoons Interesting to see you apparently have no customizations? Could you maybe post a screenshot of your firmware version page from the chargers web UI? |
|
Oh never mind, you already did earlier. Interesting. I will see if I can adopt to that. 👍 |
|
I've addressed both issue reported above in this PR bump: I've marked it for beta, will let you guys know when it is available in beta for testing again. ../Frenck |
|
Alright, @cafferata @mathiasmoons Home Assistant 2025.1.0b8 is available, which contains fixes for both reported issues. Giving that a shot would be greatly appreciated 🙏 ../Frenck |
|
I installed Beta 8, but I am receiving the following log. Logger: homeassistant.components.peblar Unexpected error fetching Peblar Peblar version data For context, this charger is managed and provided by my employer through a lease. I contacted them about the latest software, and they informed me that I can update the firmware myself (which I did, upgrading to version 1.6.2). However, they also mentioned that the Customization firmware cannot be updated because it is non-standard.(?)
|
|
@mathiasmoons Aah check, thanks for that context. It thus doesn't have any upstream update capabilities 👍 That I can work with. |
|
Logger: Unexpected error fetching Peblar Peblar version data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 379, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/peblar/coordinator.py", line 81, in handler
return await func(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/peblar/coordinator.py", line 133, in _async_update_data
available=await self.peblar.available_versions(),
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.13/site-packages/peblar/peblar.py", line 190, in available_versions
return PeblarVersions.from_json(result)
~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^
File "<string>", line 16, in __mashumaro_from_json__
mashumaro.exceptions.MissingField: Field "firmware" of type str is missing in PeblarVersions instancePS. I now see that this is the same stack trace as @mathiasmoons. 🤓 |
|
@frenck, Does that mean it is impossible? |
It is definitely doable, it just means that you won't have update notifications in Home Assistant. I'm not sure if I'm able to fix this before the final release, but will keep working on it. We are making progress 😄 |
|
Ok, yet again, processed the above warnings and bumped the Home Assistant end. This last bump will be included in the next release (2025.1.1). ../Frenck |
|
Thanks, @frenck! I’ll keep an eye out for the next release (2025.1.1) and will test the fix as soon as it’s available. I’ll be sure to report back with the results. |
|
I just noticed the 2025.1.1 release is out, so I tested it right away. I’m happy to report that the configuration was successful! 🎉 Please find a screenshot attached for reference.
Is there anything specific you’d like me to test further? Also, would you like me to prepare a PR to remove the Known limitations for white-label products like the CoolBlue BlueBuilt, or would you prefer to handle that yourself? Thanks again for all your work on this—it’s much appreciated! |
Nice! 🎉
I'll pick that up, there is some small room for improvement (Peblar was kind enough to provide me more context). I want to add virtual integrations for it as well.
You're welcome ❤️ ../Frenck |
The problem
I noticed the Known Limitations section in the Peblar release notes:
“Peblar is also sold as white-label products, like the CoolBlue BlueBuilt. This integration is tested with the Peblar branded products, and it is unknown if it works with white-label products.”
Coincidentally, I have a CoolBlue BlueBuilt charging station and would be happy to assist with testing. While setting it up, I encountered an “Unexpected error,” and the log details weren’t very clear to me. See the traceback below.
If it’s helpful, I can run additional tests or share more details to support troubleshooting or development. Let me know how I can assist!
What version of Home Assistant Core has the issue?
2025.1.0b2
What was the last working version of Home Assistant Core?
NA, new integration added in this release
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Peblar
Link to integration documentation on our website
https://rc.home-assistant.io/integrations/peblar
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/peblar/config_flow.py", line 47, in async_step_user info = await peblar.system_information() ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/peblar/peblar.py", line 230, in system_information return PeblarSystemInformation.from_json(result) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^ File "<string>", line 231, in __mashumaro_from_json__ mashumaro.exceptions.MissingField: Field "hardware_uk_compliant" of type bool is missing in PeblarSystemInformation instanceAdditional information
No response
The text was updated successfully, but these errors were encountered: