search

scottyphillips / echonetlite_homeassistant

A Home Assistant custom component for use with ECHONET enabled devices.
MIT License
117 stars 39 forks source link

Sharp UA-KCP100 speed setting #176

Open PiotrWawryniuk opened 2 months ago

PiotrWawryniuk commented 2 months ago

Hello,

I started using this plugin with my device Sharp UA-KCP100, and I can see that for some reason I am able to set the speed, but not when it is in Auto state. I have checked all possible speeds in configuration. Speed setting is working as long as I am not switching to auto. Then none off options will take any effects. e.g. it looks like:

Changed to Auto triggered by service Select: Select 14:37:51 - 1 second ago - ZHome Changed to Medium-Low triggered by service Select: Select 14:37:50 - 2 seconds ago - ZHome

I was trying to switch to Medium-Low and it is automatically switched back to Auto. I can walk through all the values until I will switch to Auto (no matter if it is from Device panel or from HA). Funny thing is that when I am clicking at the device panel and choose either "Night mode" or "Pollen", HA interpretes that as "Auto" as well. But from those I can switch to other options.

Is there any way to make it working?

Thanks, P

nao-pon commented 2 months ago

Although it is not yet released, Version 3.8.0 may yield good results. Could you try the master branch?

From the HACS ECHONETLite Platform page, select redownload from the three dots on the top right and select master.

PiotrWawryniuk commented 2 months ago

Hi, just of curiosity I started using beta versions as soon as 3.8 appeared. e.g. found that new sensor related to air quality appeared. this is the one with "fresh" like naming. As you proposed - I downloaded master. Unfortunately looking at the behavior while switching, I can tell: "no difference". Definitely I can confirm, that it will match "nearest" available state (it changes selected state to the one its understands from device perspective). As long as it is not Auto-Auto (not mentioned Night nor Pollen which is also interpreted as auto). Each state that results in proper change causes "beep" in the device.

Sharp UA-KCP100 Air flow rate setting changed to Auto triggered by service Select: Select 07:09:30 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Medium triggered by service Select: Select 07:09:30 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Auto triggered by service Select: Select 07:09:27 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Medium-Low triggered by service Select: Select 07:09:26 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Auto triggered by service Select: Select 07:09:23 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Low triggered by service Select: Select 07:09:23 - 2 hours ago - ZHome Sharp UA-KCP100 Air flow rate setting changed to Minimum triggered by service Select: Select

nao-pon commented 2 months ago

@PiotrWawryniuk Please collect your debug logs and upload them here. The method for collecting debug logs is as follows.

  1. Enable debug logging on the echonetlite integration screen
  2. Restart HA
  3. Perform a series of operations
  4. If you disable debug logging, a log file will be downloaded, so please attach it.
PiotrWawryniuk commented 2 months ago

Hello, I have attached the debug info. Was changing the values randomly. I hope that helps.

home-assistant_echonetlite_2024-03-21T12-06-31.990Z.log

PiotrWawryniuk commented 2 months ago

Oh, I can confirm that new Master branch shows two additional entites: related to total and current power consumption 👍 thank you. Wishful thinking: is there any entity like PM2.5 value? I know the orignal app is reporting such thing

nao-pon commented 2 months ago

I looked at the log. According to the logs, even if you change the air volume from Auto, it doesn't seem to be accepted, and on the other hand, there are times when the change is successful. I don't really understand the cause. The specs don't mention anything like that, so it might be device-specific. I hope I can find some effective method...

Also, things like PM2.5 sensors are not clearly stated in the specifications, so I don't know much about them either. It seems that there are parameters that can be obtained outside of the specifications, so I may be able to figure it out through trial and error, but it will be difficult without the actual machine in my hands.

PiotrWawryniuk commented 2 months ago

Hello @nao-pon, Anyway I am grateful that you had time to look at it. Is there any starting point I could look at? I would like to avoid making garbage from this repo - I am thinking rather about modifiations in code on my local instance. Could you please give a hint? Reading your comment I am considering my issue report like something that will last for longer period. Anyway I would start to dig into it in my "free time".

Thanks, P.