![]() Can you identify the DTH that it is using so I can look at the source code (if available) and perhaps a screen grab of the My Device Data page with the values Since I don’t have a Nest thermostat I cannot test/fix what is causing this 500 error. This works for Ecobee which is a cloud control thermo, but then again, I am running them with Ecobee Suite custom DTH, not ST’s OEM DTH. Thanks for pin pointing this, and I imagine you are right? Interesting, ST’s standard DTH’s are ‘supposed’ to return ‘standard’ metadata information from a Thermo capability device, like Nest, and that is all BitBar is requesting in this subroutine from above, nothing magical about those thermo metadata results which BitBar needs to display them for you. ![]() No big deal - maybe that new TCC connection has some kinks to get worked out. Since the timing is so coincidental, I suspect it was related to me switching my Honeywell Prestige 2.0 thermostat from the legacy Honeywell TCC connection to the new TCC (Total Comfort Connect) version that was just released for the new app.īitBar does not like that new TCC integration for some reason - when I removed that thermostat and refreshed, everything else in BitBar worked fine. If interested, just start a PM to (just click on my name and select message) I prefer to do this extended debugging via a private message. If you are willing, I can try to debug your RGB device over the next week or so given my crazy schedule, but that will require some sharing of your ST API strings for BitBar and the device re-added when I start to debug what you are experiencing. I would recommend, for the short-term, that you remove the offending RGB color lightbulb from BitBar devices in the SmartApp Your remaining well-behaved devices will then function in BitBar… Log.debug “Trapped Error: colorRGBList = colorUtil.hexToRgb(RGBHex): RGBHex = $” I trap for unexpected results since their are so many manufacturers of RGB light bulbs, that SmartThings just passes something I cannot work with.ĬolorRGBList = colorUtil.hexToRgb(RGBHex) That particular trapped program error is related to a RGB type color bulb device that is not reporting an expected currentColor (See below code snippet). Ran the command sudo chmod +x /".Dear you have hit a snag. Had the same problem with the launch path. Users must move and replace this file in the location of their BitBar directory Users can Download the latest version of “ST_Python_Logic.py” file by selecting the option at the bottom of the STBitBarApp menu (See Below). Using the SmartThings GitHub integration for auto-updating the oovy as recommended in Section 1.a. Users can simplify ongoing version upgrades by:.The ST_Python_Logic.cfg file installed on your PC in the users BitBar directory only contains the two strings with your specific xxx-xxx-xxx-xxx-xxx as shown in the example below:.The updated BitBar SmartApp GUI contains all the device and display options.Please make sure you have all the correct code 2.x versions of files in my GitHub. My beta version of the STBitBarApp has many new enhancements and functionality to the original version provided by Matt. The BitBar application provides the capability for displaying SmartThings devices in the MacOS top menubar and create submenus.Please note that this SmartApp requires the separate BitBar application application to be pre-installed.Please read the README file that I have updated to help you correctly install the complete application, in both the ST IDE and also on your Mac. The GitHub location for my version of the ST BitBar application has changed to “kurtsanders” and is located here.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |