Miguel Angel Nubla
Miguel Angel Nubla
$ mirobo discover INFO:miio.discovery:Discovering devices with mDNS, press any key to quit... WARNING:miio.discovery:Found unsupported device lumi-camera-aq1_miio75547134._miio._udp.local. at 192.168.1.33, please report to developers edit: copied over from #347: https://fr.gearbest.com/ip-cameras/pp_978606.html?wid=1433363
I understand that ESPAltherma should remember the switch state and recover it after connection to mqtt, but when I set it to off and send "R" to POWER to restart...
### Latest firmware used? Latest built from master ### Information Wireless motion detector DIO Chacon 54503 ### Sniffed data https://docs.google.com/spreadsheets/d/1akmaFqjuS9YmJ1XGOrc9-wFbcI69av02PvmEZjVeBS4/edit?usp=sharing I have been having trouble with a DIO Chacon device....
Enhancement #2
### The problem When arming the night mode with a low battery device, AJAX alarm is reported as disarmed instead of the expected STATE_ALARM_ARMED_CUSTOM_BYPASS. Maybe this warrants a new STATE_ALARM_ARMED_NIGHT_CUSTOM_BYPASS....
### Describe the issue you are experiencing The IPv6 addresses home assistant core receives can be used to reach the port of regular addons (without host networking enabled) just fine....
**Checklist:** - [x] I updated to the latest version available - [x] I cleared the cache of my browser **Release with the issue:** Current main branch, post 5.2.0 **Last working...
**Describe the bug** MQTT over TLS is not working, double-take always try to connect using plain MQTT regardless of configuration **Version of Double Take** v1.13.1-8e2728d **Expected behavior** MQTT over TLS...
This fixes #294. Users may have been using TLS configuration without realizing plain MQTT was being used regardless. Maybe put up a warning on the next release?