This issue is new to me in this version. The first picture I posted used to look just fine. No Info missing and wind/rain were on one line, I use the bloomsky display throughout the day so the change is a major issue. And the second pic the fonts were larger and easy to read,
Yep looks like an oversight rather than an intentional feature. @slagle how can we feed this back? Clearly fonts are not taking into account the dpi like they used to.
So, now with my thermostats, I CANNOT see the actual temperature set, only the current temperature. So, have no idea what temp I am increasing or decreasing. Any way to fix this
Iām having two major problems that may be related to this new version releaseā¦
1. Canāt See Thermostat Setpoint
As with @DR_C immediately above, the Setpoint is no longer visible in my Thermostat Device Handler.
2. Camera Preset Buttons Gone
The buttons representing my cameraās presets are gone, and so I canāt change where itās pointing.
In my case, this is a HUGE problem, because this cam reboots pretty much daily, and when it comes up, thereās no way to make it automatically go to the correct place. So, I have to go into the DH for it in the ST app, and click the appropriate preset button.
Of course, there is the web admin interface I can use as well, but thatās only available in IE on Windows (neither of which I have on my Android phone).
3. Hue Iris DH Wonky
Since Iām using a modified DH for the Hue Iris lights, I canāt tell exactly whatās going on, but something looks different in there now, and I can no longer adjust the saturation (I thin thatās what itās called).
Does anybody have any ideas on what may be causing these problems, and/or how to fix them?
Can you tell me how you setup the temp probe? I would like to put one in my swimming pool.
For me, Green means regular on/off light switches or on/off GE plug, Blue means Dimmer light switches
Rick
More info: New Color Theme in ST App?
So. Is anyone elseās Phillips Hue lights completely unresponsive to Smartthings since the update?
All my strips are working fine.
No issues at all.
Iām not using a bridge if that is significant.
@slagle, this is getting ridiculous:
I just got off a chat with support. I had a custom device handler for (RBoy apps) which while it always worked before. Seems the upgrade has caused an issue. They were able to go in and put the default device handler in for my thermostat. I see the setpoint now, BUT, not as many features as my custom device handler had.
I imagine RBoy will fix it eventuallyā¦but for now I can at least see my set points and adjust if I need to.
I just got off a chat with support. I had a custom device handler for (RBoy apps) which while it always worked before. Seems the upgrade has caused an issue. They were able to go in and put the default device handler in for my thermostat. I see the setpoint now, BUT, not as many features as my custom device handler had.
I imagine RBoy will fix it eventuallyā¦but for now I can at least see my set points and adjust if I need to.
I donāt expect developers to fix something ST has broken. Text/Rendering issues have plagued the mobile app for a very long timeā¦
My hue is completely unresponsive as well. All of them work from the Hue App, but are not working from ST. In the logging i get null number format exception for the bridge:
ā5ā:ā07ā:ā00ā āPM: error java.lang.NumberFormatException: For input string: ānullā @ line 645
5ā:ā07ā:ā00ā āPM: debug poll()
The most FRUSTRATING part of this is that the BETA version released to the community for testing worked FINE atleast with all RBoy DTHs and that something I specifically tested so ensure that something like this doesnāt happen. So obviously the Android product team decided to make some changes AFTER the Beta version released to the community and into the production release WITHOUT sending it to the community for testing. So whatās the point of BETA testing @Aaron and @Joe-UK? Looks like all that effort was a total waste IMHO.
Edit: I think the Android team should recall this release and either release the old version or the BETa version that was tested by the community. Itās high time they got their act together.
Iām not really sure how long this has been an issue in the Android SmartThings app, but the SmartThings mobile app is missing the ability to delete a configured time from a SmartApp. The function exists and works on the iOS app.
Iāve submitted a bug report to supprt. Support request #329459
Are you still seeing the issue on 2.3.1? If so, please submit a bug report and DM the ticket number.
What was fixed in 2.3.1? Iām still seeing major text/icon rendering issues just like I posted aboveā¦
We fixed a crasher and corrected text sizes in an Android 2.3.1 hot fix. Itās available in the play store now
Iām on 2.3.1 build 211001, and still have those text issues on all my phonesā¦