Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Help with creating a custom json for my fan #1264

Open
simoneluconi opened this issue Jun 13, 2024 · 2 comments
Open

Help with creating a custom json for my fan #1264

simoneluconi opened this issue Jun 13, 2024 · 2 comments

Comments

@simoneluconi
Copy link

Hi,
i'm trying to create a json for my fan (LEVOIT), but i can't find anywhere how the json should be formatted, it there a guideline somewhere?

I tried looking at other config file but i can't find a fan with the same or similar option as mine.

I need the button for:

  • ON/OFF
  • Swing
  • Fan +
  • Fan -
  • Mute
  • Sleep
  • Mode switch
  • Timer

How my json file should be formatted?
Is this configuration correct or there is a better way?

{
  "manufacturer": "LEVOIT",
  "supportedModels": [
    "unknown"
  ],
  "supportedController": "Broadlink",
  "commandsEncoding": "Base64",
  "commands": {
    "off": "",    
    "on": "",
    "fan+": "",
    "fan-": "",
    "swing": "",
    "mute":"",
    "sleep":"",
    "mode": "",
    "timer": ""
  }
}

Thanks for the help.

@chemelli74
Copy link
Contributor

chemelli74 commented Aug 29, 2024

I'm interested in the list if possible commands as well

@dgel27
Copy link

dgel27 commented Aug 29, 2024

The problem is that remote sends all state, eg, it contain mode, fan mode, temperature, swing, clock, beep.. And you cannot send just fan+. To do this, need high level protocol and known of current state. Otherways, you have study all possibilities of combinations. Tasmota devices have integrated high level, so it possible to do with it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants