John Lancaster

Some weeks turned into some months, but this should all work now. The mechanics behind the Hass plugin have been extensively reworked to support returning values from calls to the...

This type of error is caused by an MQTT message having a binary payload, which causes decoding it into `utf-8` to fail. Unfortunately, really fixing this is going to be...

After looking at the code, there's already a feature to cover this, and there's already a better error message in the dev branch. Unfortunately, you do have to already know...

Hi there, glad to hear you like some of the changes. This is normal and depends on what MQTT topics are being subscribed to by AppDaemon, which is configured in...

In that case, you'd subscribe to `qolsys/#` to get everything under that topic. For example, I subscribe to `zigbee2mqtt/#` in my setup Check [this site](https://www.hivemq.com/blog/mqtt-essentials-part-5-mqtt-topics-best-practices/) for more information about MQTT...

Not sure what's going on with the logging callbacks, but generally functions like this (sending the logs somewhere) happen in Python with logging handlers. This is an example of what...

This will be fixed in the next release. Example usage: ```python import json from datetime import timedelta from appdaemon.plugins.hass.hassapi import Hass class History(Hass): def initialize(self): entity = 'climate.play_room_radiator_1_heat_demand' history_start_time =...

This is now working properly in the dev branch. Unfortunately the Home Assistant REST API doesn't support getting the history for a whole domain like that `self.get_history(entity_id="sensor", days=5)`

Try adding these lines somewhere in your app definition. It'll suppress the warning log lines for the event subsystem. ```python import logging logging.getLogger('AppDaemon._events').setLevel('ERROR') ```

This works now in the dev branch