HA 0.90.1 broke the besmart custom component about home-assistant HOT 21 CLOSED

due to some update from the besmart () side the component is getting some strange value such

{'error': 0, 'outTempDependency': 'DNCON', 'tempNow': 'null', 'tempOut': '', 'cityBack': None, 'countryBack': None, 'heating': '0', 'heatingEnable': '0', 'mode': '0', 'holiday_end_time': '0', 'roomMark': '<omissis>', 'thModel': '1', 'saveT': '5.0', 'comfT': '26.0', 'frostT': '5.0', 'eS': 1, 'eC': '/A', 'bat': 'N/A', 'con': 1, 'bcon': 0, 'dhw': None, 'tempUnit': 'N/A', 'advance': 0, 'booster': 'N/A', 'season': 'null', 'cmdIssued': 'N/A', 'dhwActive': 'null', 'wifiSignal': 'null', 'boilerMode': 'N/A', 'programWeek': [['N', '/', 'A'], ['D', 'N', 'C', 'O', 'N'], ['N', '/', 'A'], ['D', 'N', 'C', 'O', 'N'], ['N', '/', 'A'], ['D', 'N', 'C', 'O', 'N'], ['N', '/', 'A']]}

or

{'error': 0, 'outTempDependency': '2', 'tempNow': '17.4', 'tempOut': '13', 'cityBack': '<omissis>', 'countryBack': 'IT', 'heating': '1', 'heatingEnable': 'N/A', 'mode': '0', 'holiday_end_time': '1547506800', 'roomMark': '<omissis>', 'thModel': '5', 'saveT': '18.6', 'comfT': 'N/A', 'frostT': 'N/A', 'eS': 0, 'eC': '0', 'bat': 'N/A', 'con': 1, 'bcon': 0, 'dhw': 'N/A', 'tempUnit': '0', 'advance': 'N/A', 'booster': '0', 'season': '1', 'cmdIssued': '0', 'dhwActive': 'N/A', 'wifiSignal': '84', 'boilerMode': 0,

I have made a commit with some change to manage some error condition (mainly to handle these cases of response with string like 'null' or 'N/A').

just an information besmart is just rebranding the backend service of this by this Chinese company http://www.cloudwarm.com, look this http://www.szacs.com/doce/product-detail-95.html

from here is possible to download the firmware http://www.besmart-home.com/fwUpgrade/ for your wifi box maybe they do some kind of customization.

unfortunately for the moment I don't see a way to deal directly with the thermostat.

from home-assistant.

from home-assistant.

hello

I'm using these binary sensors

binary_sensor:
  - platform: template
    sensors:
      heating:
        friendly_name: "Heating"
        value_template: "{{ state_attr('climate.besmart_thermostat', 'hvac_action') == 'heating' }}"
      cooling:
        friendly_name: "Cooling"
        value_template: "{{ state_attr('climate.besmart_thermostat', 'hvac_action') == 'cooling' }}"
      thermostat_status:
        friendly_name: "Thermostat status"
        value_template: "{{ state_attr('climate.besmart_thermostat', 'heating_state') == true }}"
      battery_state:
        friendly_name: "battery state"
        device_class: battery
        value_template: "{{ state_attr('climate.besmart_thermostat', 'battery_state') == '1' }}"
        icon_template: mdi:battery

from home-assistant.

hi @faxbio yes I know I have to change also the folder name from climate to besmart there are new guide lines to follow for custom component, unfortunately I have not so much time right now to fix all, so thank you very much for your contribution

from home-assistant.

I also have a besmart thermostat but I could not get the username and password for the wifibox, it's a default one?

from home-assistant.

from home-assistant.

Hello all,

today my children let me play a bit with HASS so I was able to fix the issue with the custom component, I have also updated the file structure to follow the new specification.

let me know if it works on your environments as well

from home-assistant.

I have also changed the way to report the operation mode and now it export also the season mode and the temperature mode

from home-assistant.

from home-assistant.

Everything working fine after the update. Well done!

from home-assistant.

It's working for me too, thank you! I thought the code was interacting directly with the wifibox, not with the besmart servers, it's possible to get DHW information this way?

L.E. I can select between all modes but setting the temp from HA is not working.

from home-assistant.

I have update the BeSmart climate to HA 0.97.0 it seems to work, I have included the battery state

from home-assistant.

Hi, are your besmart integration still working fine? after few update (now my HA >0,100 ) i noticed that HA is showing the correct value from thermostat but if i try to change some setting (temp, mode etc..) from the climate component nothing happens and I can see in the debug line of the log an error . While tryin to understand it, i noticed that the android Besmart app is changed...maybe its correlated? What about your side?

from home-assistant.

Hi, are your besmart integration still working fine? after few update (now my HA >0,100 ) i noticed that HA is showing the correct value from thermostat but if i try to change some setting (temp, mode etc..) from the climate component nothing happens a

Did you update the custom component ?
I am on 0.101.2 and don't have this behaviour (I had it before the last update)
I have A LOT of warnings/errors but since this is a working in progress I just sit here waiting for the developer! :)

from home-assistant.

Good news...same old story, Ha needs more than one reboot to start working as expected after some update.... :-S .
It is working now for me too.

from home-assistant.

however for the moment do not use it, I don't know why my besmart application is a bit crazy nowadays

from home-assistant.

from home-assistant.

I agree with you! I'm seeing strange behaviour in the app as well.
Also, I am monitoring the availability of their server (www.besmart-home.com) and there are a lot of micro situation of unavailability.

from home-assistant.

Any news in this topic? I am interested in integrating my Riello heating device controlled by besmart with HA.

from home-assistant.

Perfect, but I am missing some guide how to install that component.
I saw files in 'code' tab here, but there is a lot of things connected to thermostat and I am not sure which are optional and which are obligatory.
Do I need only to recreate custom_components/besmart and put my account data there or I need to mirror configuration from all yaml files there?
customize_glob.yaml - this I dont understand completely as well as things from groups.yaml

from home-assistant.

Ok, I think I have handled it well, both of my besmarts are visible in lovelace and I can control them.
I however cannot make heating history log to work correctly.

There is something like this in original config:

binary_sensor:
  - platform: template
    sensors: # https://www.home-assistant.io/components/binary_sensor/
      heating:
        friendly_name: "Heating"
        value_template: "{{ is_state('climate.besmart_thermostat', 'on') }}"

I have checked developer tools for besmart_thermostat and I noticed that there is no "heating" attribute, instead there is "heating_state" and it doesn't take "on" value at all. Instead it is false ot true. So I edited it to this, but it still doesn't work:

binary_sensor:
  - platform: template
    sensors: # https://www.home-assistant.io/components/binary_sensor/
      heating_state:
        friendly_name: "Heating"
        value_template: "{{ is_state('climate.besmart_parter', 'true') }}"

from home-assistant.