stranGE

We have the same problem. We migrated our Prometheus to Victoria Metrics. We are federating several Prometheus instances from big Kubernetes clusters with vmagent. The "up"-metric is missing. The same...

I think we found the problem. Victoria Metrics shows different behavior than Prometheus. Even you configure honor_labels to true, VM adds "exported_" prefix to the up metric, means "up"-metric is...

I think the easiest way should be: make the behavior configurable?

thank you, for the quick answer.

better to keep the issue open :)

You setup the hardware? You compiled the "portal" branch of https://github.com/capull0/serialusb/tree/portal ? The skylanders.py will be loaded from serialusb. You have to provide pluginpath and the plugin as argument.

Steps on your raspberry: 1. clone repository and all subrepositories `git clone -b portal --single-branch --depth 1 --recursive https://github.com/capull0/serialusb.git` 2. change to serialusb directory `cd serialusb/sw` 3. build serialusb `make`...

google for "avrdude atmega pro micro"

Sorry, i don't have the time to give that deep support. Try to get first the "original" serialusb running, not my fork. Means you have serialusb in between your Skylanders...

i figured out why some portals are not working. a imaginators portal always sends: P: 81 53 00 00 00 00 24 01 00 00 00 00 00 00 00...