ADAX NEO WIFI Modern Electric Wall Heater, Home Automation Heating

Hardware
35 
def set_room_heating_enabled(roomId, ena, token):

   # Sets heating on/off
   headers = { "Authorization": "Bearer " + token }
   json = { 'rooms': [{ 'id': roomId, 'heatingEnabled': str(ena) }] }
   requests.post(API_URL + '/rest/v1/control/', json = json, headers = headers)

I was able to turn heater off with that. To turn back on, it seems that one needs to pass the targetTemperature again, just requesting heatingEnabled: true won’t work.

1 Like
36

Sorry, was outdated. It works setting the temp now!!

BTW: is the new power consumption available throught the API?

37

I don’t see power consumption in json api spec. Would be nice to have it, maybe they have left it out in the first version.

38

could also be it is just a function of the app, where they calculate based on Watt specified and time used for heating

39

Nice, I will add it to component

1 Like
40

Edit: use danielhiversen’s integration, you’ll find it in HACS.

I’ve built a HACS compatible integration here:

(link to archived repository deleted because people keep following it)

This allows you not only to set the target temperature, but also turn the heater on and off. To do list includes config flow and async mode.

41

Since you have copied my code, it would be nice if you also credit me and remove your copyright.

1 Like
42

I’m sorry, I shouldn’t have done that. I’ve credited you and removed the copyright - if there’s anything else I should change please let me know.

Jon

43

It is ok :+1:

44

I’ve been waiting so long for this! :slight_smile:

I added the custom repository, but I am unable to find the integration.

45

Have you added it to your configuration.yaml?

46

Have now added support for on/off. Made some improvements and removed sanction as a dependency:

1 Like
47

Once you’ve added the custom repository to HACS, on the HACS Integrations page:

  1. Click the (+) in the bottom right corner and search for and add the Adax integration.
  2. HACS will show you an information page which includes configuration instructions (you need to configure this in configuration.yaml)
    You can pull up the information page again by clicking the three dots in the corner of the Adax integration card and choosing information.
  3. Edit configuration.yaml (and optionally secrets.yaml)

Broadly the same information is also here: adax/README.md at master · jon-hedgerows/adax · GitHub

Jon

48

Works OK for me now. Thanks!

1 Like
49

I am not seeing the Adax integration after clicking the (+)-button.

Is this correct?

50

why make a copy of Danieliversens module, why not help him to make his module HACS compatible, makes it easier for all of us, since Daniel has made several new customizations after your copy.
I guess he has no problem giving you credit for your contribution.

4 Likes
51

Ah, that’s because you’ve added the repository to the supervisor’s addon store. What I pulled together was designed to work with HACS.

Jon

52

Fundamentally I wanted a HACS-compatible integration now, so I built one. And because I’d built it for myself, I shared it with others. It was about expedience, nothing else.

@danielhiversen’s code sits in a repository alongside other custom components, which doesn’t appear to be compatible with the way HACS works (though feel free to correct me if I’m wrong on that) - and there’s no such things as a pull request that says “split this out into a separate repository”. Importantly - feel free to take whatever you like out of what I’ve done. That might be nothing, it might be something. Whatever works for you.

For my use case HACS wins over the addon store in the supervisor because HACS works inside home assistant core. Your mileage may vary - different people have different needs. If someone else wants to pull together a HACS-compatible integration I’ll happily switch and contribute to that.

Functionally what I did and what Daniel did are similar, though there are some differences.
Daniel’s integration now implements heat/off, whereas I picked Auto/Off. I picked Auto because that seems to reflect better what the heater does - and it’s then meaningful to report the status as Heating/Idle as appropriate (or Off).

Jon

53

Updates: https://github.com/Danielhiversen/home_assistant_adax

  • All fetching of data is now async
  • Removed sanction as a dependency
  • Compatible with hacs
  • Smaller fixes and improvements
4 Likes
54

Would be nice if their API included heater state, I mean if it is heating or not. Maybe they don’t provide that because the target temperature operates at room level (and room might have multiple heaters). Although one can figure that out from target & current temperatures the visual green feedback on thermostat card is nice (like on generic_thermostat entity I have for older heater).

I’m planning to use this to keep a summer cottage dry during winter so it won’t be controlled by temperature but by humidity instead, ie. if humidity is > 75% turn heater on, otherwise off.