Closed bencou closed 1 year ago
Sorry I'm wrong for the trigger at sunrise. It can't be the change in inverter working mode since the integration would be off. Other than that, my question remains the same.
After device entities enumeration in the action part of my automation, i got this message ;
Logger: homeassistant.components.homeassistant Source: components/homeassistant/init.py:123 Integration: Home Assistant Core Integration (documentation, issues) First occurred: 23:29:00 (1 occurrences) Last logged: 23:29:00
The service homeassistant.turn_off does not support entities sensor.modbussaj_active_power_of_inverter_total_output, sensor.modbussaj_bus_voltage, sensor.modbussaj_error_count, sensor.modbussaj_inverter_error_message, sensor.modbussaj_inverter_status, sensor.modbussaj_inverter_working_mode, sensor.modbussaj_l1_power, sensor.modbussaj_l2_power, sensor.modbussaj_l3_power, sensor.modbussaj_power_generation_on_current_day, sensor.modbussaj_pv1_power, sensor.modbussaj_pv1_total_current, sensor.modbussaj_pv1_voltage, sensor.modbussaj_reactive_power_of_inverter_total_output, sensor.modbussaj_total_power_generation
Thus my question becomes; Why does the homeassistant.turn_off service not support these entities ?
I found the right service to call in the community (programmatically-disable-enable-integration/322971) See the blog on 2021.06, reply from cyn / Jul'21 The homeassistant.update_entity service can enable/disable polling for updates based on a schedule. System options - enable (automatic) polling for updates must be unchecked. No more problems !
Using an Elfin EW11A powered by my R5-5K-T2-15 SAJ Inverter RS485 serial port and after sunset, the modbus communication is no more possible. In this state, there is a lot of error messages.