When I want to install the new version and checked the code it’s gives me an error:
- Component error: rdw - No module named 'sodapy
Awesome, nicely done! Thanks for creating this 
I keep forgetting my APK dates, especially since letters now come in through MijnOverheid.
1 Like
When I want to install the new version and checked the code it’s gives me an error:
Component error: rdw - No module named 'sodapy
That error is not specifically related to the RDW component, but is a generic error message from Home Assistant. It means that the dependencies described in the manifest.json file were not installed, and that the RDW component cannot find the sodapy library.
Is this the first custom component you’ve installed in Home Assistant?
Can you try manually install the sodapy library by doing:
pip install sodapy
or:
sudo pip install sodapy
It’s not the first custom component that i’ve installed. Have more custom components.
I’m not doing any manually installs before. I know it will be done by SSH but don’t use this. So will check if I still added this in the future.
Okay, thanks for your reply. At this moment I’m not sure why this error comes up. What version and type of Home Assistant installation do you use? Home Assistant Core/Home Assistant Docker/HASS/etc?
With the new names I’m not sure what they call it now. But I’m using Hassio on the raspberry pi 3.
HassOS 3.11 with supervisor version 209
Current operation system 3.11
Home assistant 0.106.5 version
Hi,
I added our 2 cards manually in the configuration.yaml but somehow when i look at the integration page i see this:
When i delete all the onces without sensors they are still coming back after reboots
Hi Giel, sorry for the late reply. Please try the following:
- make sure that you remove the rdw entry from your configuration.yaml
- remove all RDW component files from the custom_component directory
- remove ALL sensors, entities and other references
- reboot/restart Home Assistant
- Install the latest version of the RDW component in the custom_component directory
- Add the cars to your configuration.yaml
@Giel538 (and others): I have confirmed this issue in a test environment and I’m working on a solution.
@Giel538 and others: I’ve just released v2.9.6 of the RDW component. The problem with the endless re-adding of new sensors should be fixed in this release.
Furthermore all cars will now also show up as a device, and the sensors will show up as entities of this device. I’ve also added a Dutch translation, which comes in handy since most of us are Dutch anyway
1 Like
Ok thanks.
I will let you know in case its not working.
Thanks for the effort.
1 Like
Hi, I removed everything and want to add new car in UI integrations when I click RDW nothing happens and only the following error is trown in the logs.
Error occurred loading configuration flow for integration rdw: No module named ‘custom_components.rdw.config_flow’
Looks like Home Assistant can’t locate the config_flow.py file. Please check if the config_flow.py file is present in the /custom_components/rdw/ directory. To fix this try removing the /custom_components/rdw/ directory and re-install the latest RDW component by doing git clone https://github.com/eelcohn/home-assistant-rdw/ rdw.
Thnx for the headsup but that is not working either. The file is present.
I’ve just published v2.9.7. You can now change the date format using the “Options” button on the integrations page in the GUI.
I’m not sure why that happens, it seems like there’s a file missing, or you’ve got a problem with permissions to the files. Try removing the rdw folder containing all RDW files, and re-install a fresh version of the RDW component.
I have one more problem. I have 2 cars and with restarting home assistant sometimes on of the 2 cars fills with the initialization.
2020-05-15 18:02:58 WARNING (MainThread) [custom_components.rdw] Unable to update data from endpoint m9d7-ebf2 for XXXXXX: HTTPSConnectionPool(host=‘opendata.rdw.nl’, port=443): Max retries exceeded with url: /resource/m9d7-ebf2.json?kenteken=ZP051X (Caused by NewConnectionError(‘<urllib3.connection.HTTPSConnection object at 0x7fc0f01b8e50>: Failed to establish a new connection: [Errno -2] Name does not resolve’))
2020-05-15 18:02:58 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Auto Giel (configuration.yaml) for rdw
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/config_entries.py”, line 216, in async_setup
hass, self
File “/config/custom_components/rdw/init.py”, line 106, in async_setup_entry
raise PlatformNotReady
homeassistant.exceptions.PlatformNotReady
2020-05-15 18:03:00 INFO (MainThread) [homeassistant.components.binary_sensor] Setting up binary_sensor.rdw
Its not a problem that it fails, but once it failed it will not retry to re-initialize the sensors. I have to restart home assistant again to make it work.
[edit]
hmmz restarting will not fix this. Do you know what this error means?
This means that Home Assistant can’t resolve the hostname opendata.rdw.nl. Your DNS server isn’t working and/or reachable. This is not a specific RDW-component problem, and you’ll probably see have this problem with other Cloud-components in Home Assistant as well.
That should not happen. The RDW component should re-initialize the sensors automatically like any other component in HA when the internet connection is up again/when the DNS server is up again.