decode doesn't work

[bbrendon]

I couldn't get --decode to work.

# upb-cli -d PU08044FFF068655C5
Invalid command! Powerline repeater argument can only be 1, 2, or 4 which translates into 2, 4, or 6.

So I tried the example in your documentation and it also doesn't work.

# upb-cli -d 08008708FF2264E
Invalid command! Word count doesn't add up.
# upb-cli -V
1.1.6
# node -v
v7.10.1

[bbrendon]

Well, I removed PU from my string and it worked so I guess maybe something is wrong with the docs?

[DaAwesomeP]

Unfortunately, it's been many years since I worked with the UPB protocol, and I can't just look at a command and see the issue anymore. I believe that the PU is the PIM saying that it received the message in pulse mode. That definitely isn't hex, and I programmed it to pickup only on the UPB protocol and not the PIM-specific parts. Also, I only own the original Simply Automated RS-232 PIM, so that is what I tested with.

There must be something wrong with that example. This is most likely a result of a typo or out of date dependencies on a very new NodeJS version. I believe that I last developed the CLI tool with NodeJS v4. You could try with NVM. I don't think that the NPM version shouldn't matter. Unfortunately I am unavailable this next week, so I cannot fix it until after January 16. The non-CLI version (programmatic library only) is more future-proofed and should work flawlessly on newer NodeJS versions if you would like to try that (unless that decode error is a bug from there). It uses promises and has no dependencies.

[bbrendon]

I'm using upb-cli as a poor man's library for a python program. It's actually working quite well. Some UPB messages come back un-decoded but no major issues. My main problem is my programming skills at this point.