Issues with Dlink DSP-W110 flooding logs with events

Configuration
1

Greetings all,

I have a couple of Dlink DSP-W110s and although the work great. They are flooding my logs with events making it difficult to troubleshoot other issue. The events like like this:

2017-09-24 15:43:34 WARNING (Thread-9) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:44:03 WARNING (Thread-2) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:44:03 WARNING (Thread-2) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:44:04 WARNING (Thread-2) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:44:04 WARNING (Thread-11) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:44:05 WARNING (Thread-11) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:44:05 WARNING (Thread-11) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:44:34 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:44:34 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:44:35 WARNING (Thread-3) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:44:35 WARNING (Thread-5) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:44:36 WARNING (Thread-5) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:44:36 WARNING (Thread-5) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:45:05 WARNING (Thread-4) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:45:05 WARNING (Thread-4) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:45:06 WARNING (Thread-4) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:45:06 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:45:07 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:45:07 WARNING (Thread-3) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:45:35 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:45:35 WARNING (Thread-3) [pyW215.pyW215] Unable to find CurrentConsumption in response.
2017-09-24 15:45:36 WARNING (Thread-3) [pyW215.pyW215] Unable to find TotalConsumption in response.
2017-09-24 15:45:36 WARNING (Thread-11) [pyW215.pyW215] Unable to find CurrentTemperature in response.
2017-09-24 15:45:37 WARNING (Thread-11) [pyW215.pyW215] Unable to find CurrentConsumption in response.

an on and on…

These particular switches don’t have either temperature or power consumption sensors. I suspect the issue is HASS is attempting to poll sensors that do not exist. I am no coder and not sure what to do next. Any help that can be provided would be greatly appreciated.

Thank You!

2

Anyone have any ideas?

3

Hi @Shadex12, would you mind posting your config for these devices?

4

@xstrex certainly. Below should be the relevant part of my config:

#Add D-Link Smart Plug

  • platform: dlink
    host: 192.168.86.134
    name: Bedroom Fan
    username: admin
    password: redacted

  • platform: dlink
    host: 192.168.86.144
    name: Bedroom Speakers
    username: admin
    password: redacted

5

Looks like the readings that are filling up your logs are written into the component. The component states that it works with DSP-W215 & DSP-W110, even though, according to this page, only the DSP-W215 has the sensors for power_consumption, total_consumption & temperature. So the component would have to be updated to specify which model is being used, and which sensors to look for. If I were you, I’d throw this information into a feature request.

6

@xstrex thanks for you help. That’s the conclusion I came to as well.

How is the best way to make this request? Just post this to the feature request forum? Or is there a way to contact the author of the component directly?

7

@Shadex12 I would toss as much detail as you can into a post in the feature request section, a lot of the devs frequent the forum and it’s bound to get some exposure there. I’ve done this for several issues I’ve come across, and they’ve got the attention they need. I know in the interim this is probably pretty annoying, ya might want to tweak the logger component and try to exclude these messages.

Best of luck.

8

@xstrex I will look into posting the feature request.

The logger thing I didn’t even know about and might be my best options as I don’t think many users use these devices. I am thinking my chances of getting it fixed quickly are slim.

Going the logger route, I am not sure how I can exclude my events as they don’t seem to be coming from a component per say. I may have to exclude event warning and lower. I am a bit hesitant to do so as I may miss other things.

Thank again for all your help!

9

@Shadex12 Yea, np!

I’d agree with you, getting issues like these fixed quickly is pretty rare.

As for the logger route, it’s only a band-aid, but most likely the messages your seeing are coming from the Dlink switch component. So drilling down, and excluding those messages, based on that particular component, might be the best bet. Problem is, you’ll exclude ALL components in the switch domain. I’d do something like this:

logger:
  default: info
  logs:
    homeassistant.components.switch: critical

Another route to the feature request, is to post an issue on the Home Assistant github page, just be sure and document every detail.