skoona/homiemonitor

Homie 3.0 Convention Administrative Monitor for ESP-8266 Devices

homiemonitor's Issues

Devices are not shown

and the following error message appears in the container logs

homieMonitor    | 2019-05-28 20:29:26.792 HMIE:WARN  Services::Providers::Content#call Failure Request: Provider: Homie Monitor, klass=ArgumentError, cause=invalid byte sequence in UTF-8, Duration: 0.024 seconds, Backtrace=["/usr/local/lib/ruby/2.6.0/psych/visitors/yaml_tree.rb:298:in `visit_String'", "/usr/local/lib/ruby/2.6.0/psych/visitors/yaml_tree.rb:136:in `accept'"]

ArgumentError::invalid byte sequence in UTF-8, Duration: 0.179 seconds

I have an issue that is similar to issue #4.
I get the error ArgumentError::invalid byte sequence in UTF-8, Duration: 0.179 seconds when discovering devices. This error is probably related to degrees symbol in several mqtt topics. However this degrees symbol is presented by 0xC2 0xB0, which is a normai UTF-8 symbol.
Why is this error generated and what can I do to solve it?

The log of the mqtt topics in attached.
mqqt.log

Docker image for 64bit Raspberry OS

Hi,
I recently installed the 64bit Raspberry OS (Bullseye) on a Raspberry Pi 4.
Starting the homieMonitor Docker image shows following error in the log:

standard_init_linux.go:219: exec user process caused: exec format error

Is it required to build a new image for arm64?

Feature Request: clean homie device from MQTT

Would be cool, if there would be a feature like this script within Homie Monitor:
https://gist.github.com/andreasgruener/9935ffecbc59404375e7a9cb4a9a8812