[DEPRECIATED] BitBar V2: Display & Control SmartThings from the macOS Menubar

[kurtsanders]

@pmjoen

@kurtsanders is there any way to see which RGBlight is the culprit as I have a few?

Dear @pmjoen,

I have been watching the following NULL VALUES thread to see if this new ST backend issue affecting others has been rectified. It’s hard to tell and appears to be random, but certainly affecting some of the new DTH’s labeled placeholder in the classic ST client.

Null value Attributes throwing NumberFormatException

Not rectified yet, unfortunately even accessing an attribute with a null value is throwing the exception. In many cases it’s valid to have a null value since they represent uninitialized or unsupported attributes. A simple example, if the tamper attribute is not initialized it should be initialized otherwise the new ST app won’t show the state on the device page. On the flip side if it’s initialized you don’t want to reset it otherwise you lose a valid state. Thus the only solution is to check if it’s set to null and the moment you do that the platform throws an exception. Infact for devices which are disappearing or not show up after pairing, this is also an issue. If there’s an exception during the update or installed methods the app doesn’t show the device (even though the IDE does). …

As far as diagnosing, it is rudimentary at best, sorry but that is mostly ST’s capability for trapping this error. Even if you turn on verbose debugging in the BitBar app, you will not see the offending RGB device, just the ones proceeding it that are unaffected.

I recommend removing all the RGB devices from the BitBar preference section (Sorry) and add back each one separately, test, re-add, test until you get the 500 error. Then, when you find the offending RGB device(s), check to see which SmartThings DTH is being used by SmartThings, perhaps there is a different DTH or the ‘placeholder’ DTH that you can select that behaves better than the one of the offending device(s).

I am using LIFX Color RGB bulbs and the ST DTH is labeled ‘placeholder’ since the SM engineers changed what I used to use for a custom DTH, and the placeholder links to their web-socket code for cloud integration. My LIFX bulbs are working in BitBar.