vlebourl / custom_vesync

Custom VeSync component for Home Assistant
96 stars 59 forks source link

plasma pro function #146

Closed alpharesearch closed 1 year ago

alpharesearch commented 1 year ago
          Sorry I didn't see this message... 

Can you open a new feature request for the plasma pro function? Provide the diagnostics file with it and I'll try to add it. If not possible with only the diagnostics file, I might request access to your device if you're ok with that, but we'll discuss that later. Cheers.

_Originally posted by @vlebourl in https://github.com/vlebourl/custom_vesync/issues/56#issuecomment-1543550465_

alpharesearch commented 1 year ago
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2023.5.2",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.11",
    "docker": true,
    "arch": "x86_64",
    "timezone": "America/New_York",
    "os_name": "Linux",
    "os_version": "6.1.25",
    "supervisor": "2023.04.1",
    "host_os": "Home Assistant OS 10.1",
    "docker_version": "23.0.3",
    "chassis": "vm",
    "run_as_root": true
  },
  "custom_components": {
    "lutron_caseta_pro": {
      "version": "2022.2",
      "requirements": []
    },
    "scheduler": {
      "version": "v0.0.0",
      "requirements": []
    },
    "multiscrape": {
      "version": "6.5.0",
      "requirements": [
        "lxml==4.9.1",
        "beautifulsoup4==4.11.1"
      ]
    },
    "picotts_remote": {
      "version": "1.0.1",
      "requirements": []
    },
    "hacs": {
      "version": "1.32.1",
      "requirements": [
        "aiogithubapi>=22.10.1"
      ]
    },
    "vesync": {
      "version": "1.0.0",
      "requirements": [
        "pyvesync==2.1.6"
      ]
    },
    "bhyve": {
      "version": "3.1.2",
      "requirements": []
    }
  },
  "integration_manifest": {
    "domain": "vesync",
    "name": "VeSync",
    "codeowners": [
      "@markperdue",
      "@webdjoe",
      "@thegardenmonkey",
      "@vlebourl"
    ],
    "config_flow": true,
    "dhcp": [
      {
        "hostname": "levoit-*",
        "macaddress": "*"
      }
    ],
    "documentation": "https://www.home-assistant.io/integrations/vesync",
    "iot_class": "cloud_polling",
    "issue_tracker": "https://github.com/vlebourl/custom_vesync",
    "requirements": [
      "pyvesync==2.1.6"
    ],
    "version": "1.0.0",
    "is_built_in": false
  },
  "data": {
    "fans": [
      {
        "device_name": "Markus Hepa Fan",
        "device_image": "https://image.vesync.com/defaultImages/deviceDefaultImages/wfon_apr_lap-c302s-wusb_us_240.png",
        "cid": "**REDACTED**",
        "connection_status": "online",
        "connection_type": "WiFi+BTOnboarding+BTNotify",
        "device_type": "LAP-C302S-WUSB",
        "type": "wifi-air",
        "uuid": "**REDACTED**",
        "config_module": "WFON_APR_LAP-C302S-WUSB_US",
        "mac_id": "**REDACTED**",
        "mode": "auto",
        "speed": 1,
        "extension": {
          "airQuality": -1,
          "airQualityLevel": 1,
          "mode": "auto",
          "fanSpeedLevel": "1"
        },
        "current_firm_version": null,
        "device_region": "US",
        "pid": null,
        "sub_device_no": null,
        "config": {
          "display": true,
          "display_forever": true
        },
        "device_status": "off",
        "enabled": false,
        "config_dict": {
          "module": "VeSyncAirBypass",
          "models": [
            "Core300S",
            "LAP-C301S-WJP",
            "LAP-C302S-WUSB"
          ],
          "modes": [
            "sleep",
            "off",
            "auto",
            "manual"
          ],
          "features": [
            "air_quality"
          ],
          "levels": [
            1,
            2,
            3,
            4
          ]
        },
        "features": [
          "air_quality"
        ],
        "modes": [
          "sleep",
          "off",
          "auto",
          "manual"
        ],
        "air_quality_feature": true,
        "details": {
          "filter_life": 9,
          "mode": "manual",
          "level": 0,
          "display": false,
          "child_lock": false,
          "night_light": "off",
          "air_quality": 1,
          "display_forever": false,
          "air_quality_value": 16
        }
      }
    ]
  }
}
alpharesearch commented 1 year ago

Thank you for looking at this. I'm fine with giving you access to my device.

vlebourl commented 1 year ago

Hey, thank you for the diagnostics. However, I don't see anything related to a "Plasma Pro" in it... Could you try downloading the diagnostics with Plasma Pro both on and off and make a diff to see where there is a change? Otherwise, it might not be supported by the underlying library, in which case there is nothing I can do yet.

github-actions[bot] commented 1 year ago

'There hasn't been any activity on this issue recently. Is this issue still present? Please make sure to update to the latest Home Assistant version and version of this integration to see if that solves the issue. Let us know if that works for you by adding a comment 👍. This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.'

alpharesearch commented 1 year ago

Hey, thank you for the diagnostics. However, I don't see anything related to a "Plasma Pro" in it... Could you try downloading the diagnostics with Plasma Pro both on and off and make a diff to see where there is a change? Otherwise, it might not be supported by the underlying library, in which case there is nothing I can do yet.

Looks like the Plasma Pro is not implemented in the underlying library, because there is no difference in the diagnostic regardless of the state. I guess this was to be expected because I just asked to treat it like a core300s. But all the core300s functions are there.

vlebourl commented 1 year ago

Best course of action would be to open an issue on the pyvesync repo and ask for the feature to be added.

github-actions[bot] commented 1 year ago

'There hasn't been any activity on this issue recently. Is this issue still present? Please make sure to update to the latest Home Assistant version and version of this integration to see if that solves the issue. Let us know if that works for you by adding a comment 👍. This issue now has been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.'