Spoke too soon. The issue has returned, after discovering devices on Alexa. How can I determine why this one particular Hue group keeps hanging up inside the Alexa app. I’m certain there’s a connection between Hue, ST and the smartapp.
May I ask how to update to the version?
1.8
The App, Bridge device handlers and a new plug switch device handler was added
Copy code from github from those to the ones made when installing remember to press publish > for me once you have copied the new code
its easier to setup github integration with IDE then its only a few clicks to update
I prefer the github integration. can I just do the github integration to update and overwrite files? or I have to manually remove the smart app and device handlers before doing the github?
HUE B SMART UPDATE 1.83 (Changes to App & Bridge Device Handler)
- Changes to choose Scene/Bulb/Group Pages (Requested by @leonardo)
Scenes - Now able to display longer names & shows the Group/Room ID
Groups - Now able to display longer names & shows the Group/Room ID
NOTE: It is not required, nor necessary to donate to use this SmartApp. This is a free open source software, That I have taken over development as no one else did. But if you feel like it, you can donate here.
How do i pause/remove the app?
just remove all bulbs, groups and scenes then the app
Removed original hue hub.
when i press the button to include the hub it says im dont have the rights or something to do this. Oh well back to original hue solution. See many others are having this issue. Installed all Dhs and app
From logs
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: error physicalgraph.app.exception.UnknownDeviceTypeException: Device type ‘Hue B Smart Bridge’ in namespace ‘info_fiend’ not found. @line 193 (linkButton)
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: trace bridge.value.serialNumber = 0017884ed879 *****************
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: trace state.host = 192.168.0.60:80******************
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: trace state.user = sp7NvNMWwD6TbOxmxVaFItFgRI5y1md45FG3EDs8 ******************
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: info Bridge uuid:2f402f80-da50-11e1-9b23-0017884ed879={deviceAddress=0050, devicetype=04, hub=4f643f1d-c2bb-4d34-802f-16f8399f7c86, itemsDiscovered=false, mac=0017884ED879, name=Philips hue (192.168.0.60), networkAddress=C0A8003C, serialNumber=0017884ed879, ssdpNTS=null, ssdpPath=/description.xml, ssdpTerm=urn:schemas-upnp-org:device:basic:1, ssdpUSN=uuid:2f402f80-da50-11e1-9b23-0017884ed879, stringCount=04, verified=true}
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: trace username sp7NvNMWwD6TbOxmxVaFItFgRI5y1md45FG3EDs8
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: trace ssdp uuid:2f402f80-da50-11e1-9b23-0017884ed879
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:12: info Bridge linked!
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:10: info Button Pressed - Link Done - Save Username
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:09: debug linkButton [id:1cfa61e7-3af7-4246-9e52-5384fb52c644, ip:192.168.0.60, linkingBridge:true, mac:0017884ED879, name:linkButton, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017884ed879]
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:09: info IP Address is 192.168.0.60:80
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:09: info MAC Address is 0017884ED879
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:09: info Sending Developer Request
1cfa61e7-3af7-4246-9e52-5384fb52c644 19:11:05: debug linkButton [id:1cfa61e7-3af7-4246-9e52-5384fb52c644, ip:192.168.0.60, linkingBridge:true, mac:0017884ED879, name:linkButton, ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017884ed879]
The bridge DH is not installed or not published
My bad got it to work
Quick question everything is super but I use ikea bulbs with hue hub because it’s has worked much better then pairing directly to st.
I have a 600 color bulb and I can’t set kelvin values
Going from -1 to 4000 doesn’t change anything. My color ambiance lights work fine
I figured out i can make a 2700K and 3500K scene in hue and just trigger them using webcore for the 600lm ikea bulbs. Also. I had this issue on the same bulb with native hue app. Kelvin didn’t show up there.
Thanks a lot for this awesome app. If i Wasnt a poor student I would donate a couple of beers.
@tmleafs any reason why i cant capture and restore attributes correctly?
Basically, if the colormode is hs the capture and restore works fine
If colormode is ct, capture works but restore doesnt work as intended. instead of it restoring to the last color temperatue it will restore to hs and last stored hsl values. cant set colormode to ct, throws error.
I have asked on webcore on multiple threads… no workaround except one i came up with:
First test what colormode the bulb is in and then store/restore only the applicable attributes (hsl versus colortemp+level).
This actualy works but makes for a more resource intensive piston. would be nice to capture all attributes and restore all attributes, including having the ability to set the colormode of the bulb.
am i stuck using my work around?
any help is appreciated… thanks!
I’ve been working on a huge rewrite the last few months that probably fixes this let me clean it up a bit and I will put it on github as beta branch for you to try
1 Like
No worries sir, take your time. Thank you for everything you have done over the years!!
Hoping someone can help me out
I was on the meethue(my hue) site cleaning up and deactivating old devices and integrations that I accumulated. It seems that I must have deleted the ST\Hue B Smart link because I can no longer control any hue devices from the ST app. The logs show an unauthorized user message.
How do I reauthorize the connection?
Is there a read me file on this? Forgive my ignorance but do I need to delete the hub and then re-add?
Switching from official to hue b smart? Then yes