Seems the update changed some of the API for modules. I’m going to be looking at updating home assistant in the coming weeks. This will give me the opportunity to reproduce the error locally and fix this module.
@barrymossel Regarding your Experia module - I would suggest testing the functionality outside of the home assistant environment. The functions in this module don’t use any core Home Assistant features, so you should be able to run it (with some minimal modifications) as a standard python script on your machine. This will simplify your testing / debugging cycle and help you develop your module.
The thing is the logging in to those access points is quite different. I can see what is done there, but my Python knowledge isn’t good enough to get that to work. Fortunately I will have a Fritzbox through XS4ALL within two weeks.
The device tracker for experiabox v10 doesn’t work annymore. (issue on github)
It recently got an firmware to V10 T03.7, perhaps this caused it or is it a breaking change in home assistant…
Can anyone comfirm this issue?
I have a Experiabox V10 but I have two Experia Wifi access points from my internet provider to extend coverage in my house.
These access points disable wifi on the Experiabox router, so that device trackers doesn’t work anymore.
Can you create a tracker for this device? Arcadyan Experia WiFi
Two things/questions:
When I add the hide_if_away piece in the config, HA says the config is an invalid function
When I leave the above out, the config is OK, but after a HA reload there is no known_devices.yaml being created.
How can I debug this? I do see the following in the log:
INFO (SyncWorker_5) [custom_components.experiaboxv10.device_tracker] Loading wireless clients…