Battery Attribute

[daconrad0]

Is it possible to get the battery state so I can change the batteries as needed. I currently only see the following:

[postlund]

Maybe, I don't know. Don't have any battery powered devices myself.

[kintaroju]

@daconrad0 hi, is your unit the s161? the s160 doesn't have a battery?

[daconrad0]

Yes Dennis Conrad

…

On Nov 2, 2020, at 5:45 PM, kintaroju ***@***.***> wrote:  @daconrad0 hi, is your unit the s161? the s160 doesn't have a battery? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[kintaroju]

@daconrad0 question for you, does your s161 report the change in state from dry to wet at all? I've configured my device correctly in the configuration.yaml under binary_sensor and it sees the device, but when I get a cup of water and let it beep for 20-30 seconds, I don't see a change in state in the UI entity, does yours show a change in state in the UI entity?

[kintaroju]

@postlund since @daconrad0 indicated that the s161 works with your integration, what would it take for us to help you get the data to poll battery states from the s161?

[postlund]

@kintaroju We need to find the action used to extract that information. Start by running this command and pasting the result:

python custom_components/dlink_hnap/dlink.py <ip> <pin> actions

Replace and with the information for your device.

[kintaroju]

@postlund, i am using hassos to run home assistant, and took me a while to get into the docker session, below is the error I got, when i installed python3:

when i tried to install python i had an error installing it.

[postlund]

@kintaroju Try:

pip install xmltodict

And run again, should work.

[kintaroju]

@postlund I get the following error messages below. I know that I can ping the device in question:

[postlund]

@kintaroju Verify that the IP address is correct. I would expect not since you get a timeout.

[kintaroju]

@postlund I've validated the IP, and I've check the AP to ensure that the MAC matches the IP, and I've did a test ping from HassOS to the device and it's all correct. I've even double checked the PIN on the back of the device and what I inputted is correct.

I've even reassigned the IP and that didn't help either. Do you have any other ideas to help troubleshoot the issue?

BTW i am testing this first on my s160 first before attempting this on the s161 to make sure I have the process down pat.

[postlund]

Humm, that's strange. Maybe you can try to find an MDNS/zeroconf client and look for the HNAP service? I think it's called _dhnap._tcp.local or so. I suspect that they might use a different port number and we can see that in the service.

[kintaroju]

@postlund thanks for that tidbit about mdns being the culprit. i managed to get the s160 on the same vlan/subnet as the home assistant server and it managed to query the device. I will test the s161 shortly after i move the device.

I believe there is something up with opnsense and the mdns-repeater service as it's just a simple option to select 2 interfaces and mdns is "supposed" to work, which doesn't seem to be the case. If you can provide some tips on what I could be missing here that would be appreciated. For the moment for my workaround I've had to create a new SSID to allow the devices to connect to the main network because the silly devices don't support "fast roaming" 802.11r on my ubiquiti APs.

[kintaroju]

@postlund I've placed the s161 on the main network at home, and now i get the following error message:

[postlund]

@kintaroju MDNS isn't really needed as I haven't implemented support for discovery. What I'm interested in is what port is announced for the HNAP service. HNAP is just SOAP over HTTP and normally served over port 80 (unencrypted). The MDNS could reveal if it's another port. So have a look at the service and let me know what it says.