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

The Device Monitor SmartApp is being affected now too according to my Live Logging.

Tagging @erocm1231 as an FYI. I’ll cross post too.

Dear @NewHere17,

This one is harder to detect where the problem is as the SmartThings API error seems to indicate that this music player device does not have a ‘status’ value which I am looking for to indicate whether the music player is ‘playing’, or paused/transitioning. It could be that you have selected a non-Sonos device in your list of musicplayers for BitBar to display. I think this SmartThings API ONLY WORKS WITH SONOS devices at this time. {Please let me know what type of music players you have}

If these are all SONOS devices, can you turn on all your SONOS system device and see if that will cause a ‘status’ value to be available via the SmartThings API. Otherwise you might have to de-select any Sonos devices as MusicPlayers in the BitBar Output App to avoid this sections error. :frowning:

Here are the 7 Sonos devices I have( Sonos 1, Sonos 5’s, Sonos Base) and they are both version 1 and version 2 systems. The green dot indicates playing and red, not playing/paused/transitioning, etc.

I have made some overnight performance enhancements in the latest release of the groovy App as well as lowered some system event history defaults to avoid the rate-limit. Everything is working as before and I have added back all the devices before the new limits as well as limited device event history.

Of course, if one turns on all the devices with extensive event log history, they will undoubtedly hit the rate-limits. :rage:


Hi @kurtsanders

i use only sonos.
Play 5 in the “arbeitszimmer” and a stereo double in “bad”
before the update to 3.00 it works perfect.

@NewHere17: I have PM you.

@kurtsanders @Nezmo @NewHere17 @greg @jkp

We did in fact release some new rate limits early. They are being rolled back and there will be an update to the docs and a communication about the change before we start enforcing any new rate limits. Apologies for all of those who were inconvenienced by this.


Thanks @jody.albritton,

So are the new rate-limits rolled back as of now, or going to be rolled back. Just trying to determine if my version changes made the SmartApp work again or if the rate-limits were rolled back.

Just curious, how will a SmartApp know that it exceeded the runtine rate limit so that it can communicate to the user that they might need to select less devices or functions?

The changes should be rolled back now and if you look at the docs.smartthings.com link I posted above about rate limits, there are some header values returned about the current rate usage and rate limit reset time.

1 Like

@jody.albritton, many thanks. Pretty awesome you handled this on a Sunday.

@kurtsanders, I had not yet implemented your updated app and I can confirm my BitBar is functioning again.


If I restart my mac i get these errors

After 20-30 seconds i going to click “refresh all” and then everything works.

I think that your Mac OS system internet modules are not fully initialized for BitBar’s initial internet request, when it is starting up. The error that you are encountering is explained below:


  • Often, URLError is raised because there is no network connection (no route to the specified server), or the specified server doesn’t exist.

My Apple MacBook Pro 2017 macOS High Sierra 10.13.4, upon reboot/startup, does not encounter this URLError condition and displays the BitBar Menu as expected. But my Apple MacBook might be newer than your model and hence able to ready the internet connection before BitBar requests a HTTP connection with SmartThings.

I have uploaded a new release of ST_Python_Logic.Py 3.04 that provides an error handler to trap for this HTTP error rather than raise a system error. Since I cannot determine whether the HTTP error condition maybe due to many different factors, I simply have BitBar print am error message that alerts the user to check their internet connectivity and refresh BitBar again.

1 Like

Thanks :slight_smile:

does the new v3 support RGB devices?

1 Like

V3 would handle these devices as a switch or dimmer… Are you asking if I can add the ability to change color?

yes, it would be nice to change the color with bitbar.

2 new thinks :slight_smile:
If i add the new fibaro door/window sensor 2 to the temperature section i get the error:

fibaro motion sensor zw5 works in the temperature section, since yesterday i get an error with my 4 motion sensors (the old fibaro motion sensor (without ZW5 in the description)

Dear @NewHere17

Would you verify that your installation is current at:

  1. ST_Python_Logic.py v3.04
  2. BitBar Output App v3.01

I added some ‘NoneType’ error checking in these minor releases to account for a ‘NoneType value’ being returned in certain devices. It might mitigate this issue you are experiencing with the fibaro motion sensor. If you are on this release, let me know.

As far as RGB devices that have a capability of color changes, I’m not sure how I could add a micro side control for the RGB device like BitBar displays for devices with a dimmer capability (10%-100% by 10). Perhaps showing a primary & secondary color list instead of a dimming level? Is this what you are requesting?

1 Like

I updated to 3.04 and 3.01

Now i get the error

If i select the devices fibaro door/window 2 and motion sensor i still get the java exception

it´s possible to set the Red/Green/Blue Color with numbers? something like a textfield?

BitBar, being a display only menu, cannot accept input at this point. But we have a few options I could explore:

  1. A pre-defined short side menu list for an RGB capable device, as in,
  • Red
  • Green
  • Blue
  • White
  • Cyan
  • Magenta
  • Orange
  • Purple
  • Yellow

and/or possibility to define a custom color menu list in the BitBar Output GUI for all RGB devices as in:

  • Name: HexCode
  • Name: HexCode
1 Like

Just wanted to confirm what @NewHere17 was seeing

I get a 20%20AM with 26%20AM

Adding a favorite device removes the error. Having no favorite device adds the error back.

Favorite device is listed as optional, but is required to avoid the error.

Hi @kurtsanders

Yes. That would be a great new feature :slight_smile:

1 Like