I’m still looking into this. It might take me a few days to get back to you.
Just to let you know, this worked flawlessly!!
I can now add and control grouped elements of my Hue beyond Pendant
Thanks for sorting this so quickly!!
Daniel
1 Like
So, the whole updating fiasco got too confusing for me because the results were never the same throughout the day. Sometimes SmartThings would update within seconds of a Homekit command and other times it would take several minutes. That said, I found the solution to my problem in another thread. When using CoRE, it optimizes commands by default by skipping commands it doesn’t think are needed. So, for example, if a bulb or a group of bulbs appear to be in the “On” state, it will skip the command to turn it on. To resolve this, in each Piston, you can scroll down to the bottom, tap “Advanced Options” and turn on “Disable command optimizations” and tap Done to save the change. Works much better now!
1 Like
Hi,
I see on the live logging warnings from Hue advanced as below. They are quite frequently.
What are the reason for them ? how can we solve the issues ?
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:07:32 AM: warn Input color missing
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:07:31 AM: warn Input color missing
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:42 AM: warn Error returned from Hue bridge, error = [address:/lights/11/state/effect, description:parameter, effect, is not modifiable. Device is set to off., type:201]
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:16 AM: warn Error returned from Hue bridge, error = [address:/lights/11/state/sat, description:parameter, sat, is not modifiable. Device is set to off., type:201]
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:16 AM: warn Error returned from Hue bridge, error = [address:/lights/11/state/hue, description:parameter, hue, is not modifiable. Device is set to off., type:201]
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:16 AM: warn Error returned from Hue bridge, error = [address:/lights/11/state/effect, description:parameter, effect, is not modifiable. Device is set to off., type:201]
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug BODY: {"hue":25559,"sat":254,"on":false,"alert":"none","transitiontime":10}
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug PUT: 192.168.254.244:80/api/v8iTEYrP91zQKvstKIyeBSn61h6WAHtL1BUBWB4z/lights/11/state
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: trace Bridge: 0017882F03CF - Host: 192.168.254.244:80
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug Executing 'setColor([transitionTime:2, hue:39, saturation:100, switch:off])'
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug BODY: {"effect":"none"}
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug PUT: 192.168.254.244:80/api/v8iTEYrP91zQKvstKIyeBSn61h6WAHtL1BUBWB4z/lights/11/state
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: trace Bridge: 0017882F03CF - Host: 192.168.254.244:80
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:15 AM: debug Executing 'setEffect(none)'
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:11 AM: warn Input color missing
b0a9c521-4876-4404-93c9-d5ad6fa7be99 9:05:11 AM: warn Input color missingHow are you attempting to set the color when warn Input color missing is appearing? The other errors are because something is setting the color of a light that is turned off.
The popcorn effect is when you send a command to a group of lights and the lag between when different ones actually change is visible in the room, so someone in the room notices the lights coming on individually. There is video in the following thread:
There is also some detailed technical discussion of Hue polling and delays including comments by smartthings staff in the following:
There are several reasons why this can happen with hue bridge in SmartThings. Including an overworked repeater somewhere in the mix.
Often the problem is solved by using a Hue scene rather than trying to create a group of bulbs with third-party software.
In this particular case, the issue is that people had smartthings automations which had been working just fine, in some cases for months, and then all on its own the popcorn effect began. A number of people were affected at about the same time but there were no similar reports in general Hue forums. More details in the first thread above.
Thank you for the info. Personally, I always have had the “popcorn” effect (I’ve had my SmartThings hub/Hue bulbs since 2015). The only solution I have ever found is to use a native Hue group. (A scene would also work but I have absolutely no use for scenes with my use-case.)
In the first link, the OP mentions his code didn’t go through any “each” loops, implying that the commands should be sent simultaneously. From what I understand, this assertion is not correct. Regardless of whether you type the command like devices.each { it.on() } or devices?.on(), once compiled the code will be executed the same way (loop through each device and send the on() command). The “?” is what tells the code to do this for all devices - without this, the command would only be executed for the first device - but sequentially just like a loop, not all at one time. Basically, it just allows for less typing and cleaner code. It’s possible I’m wrong about this, but I’m fairly certain that I’m not.
That being said, it makes sense that turning on multiple lights sequentially, which is what people are really doing, would now take longer. The more recent updates to the code actually listen to the response from the hub and confirm that a light did what was expected before updating the state. In my opinion, this is the proper behavior. So when you send the on() command to three lights sequentially, you send on to the first one, wait for a response, on to the second one, wait for a response, on to the third one, wait for a response. There is some asyncronicity to this but because everything with SmartThings is cloud based the more processing it’s doing the more latency there is with sending commands.
I don’t plan to try to fix this issue because to me, nothing is broken. If you are sending commands to lights individually, you shouldn’t expect them to behave like a single fixture. It you want them to behave as a single fixture, create a group - then there is only one command and one response. In my personal setup, any lights I want to turn on at the same time (such as multiple bulbs in the same fixture) are included as a group. If I ever wanted to control those lights individually (I never have), I would simple use the Hue app. I don’t have any lights duplicated in SmartThings as an individual light and as a group to keep things clean, but there’s no reason you couldn’t do so if your use-case requires it.
So basically, if you have a group of lights you frequently turn on together, make a group. That’s why groups exist.
1 Like
I think, if you’ve seen that behaviour in the code then it’s a very likely cause of why things are much more noticeable than before. Some people like myself in the UK seem to suffer from variable lag from the UK shard and at times the delay for a single hue light is anything up to 6-7 seconds. If you have a few, then you’ll be in and out of the room before it switches on all the lights.
The grouping is a good solution and of course only available where people use customised Hue connect smartapps like yours.
1 Like
hi,
I have several smart apps that set the color of the hue bulbs.
how can I find which one is triggering the “warn Input color missing” warning.
once I catched CoRe setting the bulb color to “orange” when I got that warning.
hi,
I could not get any response about this. any ideas ?
Can you not just remove each of the smart apps until you finally get what you need?
Have you had a look in the Philips Hue app to see if it’s there?
Sorry about the late response. For whatever reason I never got an email notifying me of your post.
I would start by looking in Live Logging, and see what other SmartApps log things just before you see that warning. That may not result in an apparent answer, though. If not, your best bet would probably be to choose a particular bulb to test with and assign the SmartApps one at a time, letting each one do the color setting, and see if you get that warning before proceeding to add the next one.
I see many errors on my log. please see below.
among them, there’s this debug Bridge with 5CCF7FE8824A not found message.
what is that ?
I also see “debug Device (5CCF7FE8824A) was already found in state with ip = 192.168.254.245:80.”
these are all available in the following partial log with "warn Input color missing"
I get that too frequently.
it is really disturbing. please help me. I can’t remove all my smartapps.
677c908-1c40-4ed1-b614-60cca12d4b4b 12:20:44 AM: debug Device data: (192.168.254.245:80) - reporting data: (192.168.254.245:80).
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:44 AM: debug getChildDevices(false), children=19
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:44 AM: debug Bridge with 5CCF7FE8824A not found
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:44 AM: trace [uuid:38323636-4558-4dda-9188-cda0e6e8824a:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e6e8824a, networkAddress:C0A8FEF5, ssdpNTS:null, devicetype:04, mac:5CCF7FE8824A, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:38323636-4558-4dda-9188-cda0e6954719:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e6954719, networkAddress:C0A8FEFC, ssdpNTS:null, deviceAddress:0050, mac:5CCF7F954719, devicetype:04, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:4dd31a38-693c-aa71-7751-0d7589ea5233::urn:schemas-upnp-org:device:Basic:1:[ssdpUSN:uuid:4dd31a38-693c-aa71-7751-0d7589ea5233::urn:schemas-upnp-org:device:Basic:1, networkAddress:C0A8FE52, ssdpNTS:null, deviceAddress:07AA, mac:3CCD93830ACF, devicetype:04, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:2f402f80-da50-11e1-9b23-0017882f03cf:[ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882f03cf, networkAddress:C0A8FEF4, ssdpNTS:null, serialNumber:0017882f03cf, mac:0017882F03CF, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:basic:1, stringCount:04, lastActivity:1489094442158, verified:true, name:Philips hue (2F03CF), devicetype:04, idNumber:2F03CF], uuid:38323636-4558-4dda-9188-cda0e695d55b:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e695d55b, networkAddress:C0A8FEED, ssdpNTS:null, deviceAddress:0050, mac:5CCF7F95D55B, devicetype:04, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:38323636-4558-4dda-9188-cda0e620a75a:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e620a75a, networkAddress:C0A8FEFB, ssdpNTS:null, devicetype:04, mac:5CCF7F20A75A, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-or...[TRUNCATED]
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:44 AM: debug Device (5CCF7FE8824A) was already found in state with ip = 192.168.254.245:80.
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:44 AM: trace Location: devicetype:04, mac:5CCF7FE8824A, networkAddress:C0A8FEF5, deviceAddress:0050, stringCount:04, ssdpPath:/description.xml, ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e6e8824a, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, ssdpNTS:
531b07dc-91ee-46a1-9b2b-90823337e067 12:20:43 AM: trace Parsing description
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:42 AM: warn Input color missing
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:42 AM: warn Input color missing
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:42 AM: debug getChildDevices(false), children=19
531b07dc-91ee-46a1-9b2b-90823337e067 12:20:42 AM: debug Parsing 'index:17, mac:0017882F03CF, ip:C0A8FEF4, port:0050, headers:SFRUUC8xLjEgMjAwIE9LDQpDYWNoZS1Db250cm9sOiBuby1zdG9yZSwgbm8tY2FjaGUsIG11c3QtcmV2YWxpZGF0ZSwgcG9zdC1jaGVjaz0wLCBwcmUtY2hlY2s9MA0KUHJhZ21hOiBuby1jYWNoZQ0KRXhwaXJlczogTW9uLCAxIEF1ZyAyMDExIDA5OjAwOjAwIEdNVA0KQ29ubmVjdGlvbjogY2xvc2UNCkFjY2Vzcy1Db250cm9sLU1heC1BZ2U6IDM2MDANCkFjY2Vzcy1Db250cm9sLUFsbG93LU9yaWdpbjogKg0KQWNjZXNzLUNvbnRyb2wtQWxsb3ctQ3JlZGVudGlhbHM6IHRydWUNCkFjY2Vzcy1Db250cm9sLUFsbG93LU1ldGhvZHM6IFBPU1QsIEdFVCwgT1BUSU9OUywgUFVULCBERUxFVEUsIEhFQUQNCkFjY2Vzcy1Db250cm9sLUFsbG93LUhlYWRlcnM6IENvbnRlbnQtVHlwZQ0KQ29udGVudC10eXBlOiBhcHBsaWNhdGlvbi9qc29u, body:eyIxIjp7InN0YXRlIjp7Im9uIjp0cnVlLCJicmkiOjI1NCwiaHVlIjoxMzEwNywic2F0Ijo1MSwiZWZmZWN0Ijoibm9uZSIsInh5IjpbMC40MTIyLDAuMzg1OV0sImN0IjoyOTYsImFsZXJ0Ijoibm9uZSIsImNvbG9ybW9kZSI6ImhzIiwicmVhY2hhYmxlIjp0cnVlfSwidHlwZSI6IkV4dGVuZGVkIGNvbG9yIGxpZ2h0IiwibmFtZSI6IkxpdmluZyBSb29tIFRhYmxlIExhbXAiLCJtb2RlbGlkIjoiTENUMDAxIiwibWFudWZhY3R1cmVybmFtZSI6IlBoaWxpcHMiLCJ1bmlxdWVpZCI6IjAwOjE3Ojg4OjAxOjAwOmJmOjdmOjVhLTBiIiwic3d2ZXJzaW9uIjoiNS4yMy4xLjEzNDUyIn0sIjIiOnsic3RhdGUiOnsib24iOnRydWUsImJyaSI6MjU0LCJodWUiOjEzMTA3LCJzYXQiOjUxLCJlZmZlY3QiOiJub25lIiwieHkiOlswLjQxMjIsMC4zODU5XSwiY3QiOjI5NiwiYWxlcnQiOiJub25lIiwiY29sb3Jtb2RlIjoiaHMiLCJyZWFjaGFibGUiOnRydWV9LCJ0eXBlIjoiRXh0ZW5kZWQgY29sb3IgbGlnaHQiLCJuYW1lIjoiTGl2aW5nIFJvb20gUmlnaHQgTGFtcCIsIm1vZGVsaWQiOiJMQ1QwMDEiLCJtYW51ZmFjdHVyZXJuYW1lIjoiUGhpbGlwcyIsInVuaXF1ZWlkIjoiMDA6MTc6ODg6MDE6MDA6YmY6MWM6YzktMGIiLCJzd3ZlcnNpb24iOiI1LjIzLjEuMTM0NTIifSwiNCI6eyJzdGF0ZSI6eyJvbiI6dHJ1ZSwiYnJpIjoyNTQsImh1ZSI6MTMxMDcsInNhdCI6NTEsImVmZmVjdCI6Im5vbmUiLCJ4eSI6WzAuNDU2OSwwLjQxMjRdLCJhbGVydCI6Im5vbmUiLCJjb2xvcm1vZGUiOiJocyIsInJlYWNoYWJsZSI6dHJ1ZX0sInR5cGUiOiJDb2xvciBsaWdodCIsIm5hbWUiOiJMaXZpbmcgUm9vbSBUViBMZWZ0IExhbXAiLCJtb2RlbGlkIjoiTExDMDA3IiwibWFudWZhY3R1cmVybmFtZSI6IlBoaWxpcHMiLCJ1bmlxdWVpZCI6IjAwOjE3Ojg4OjAxOjAwOjFhOjk5OmY0LTBiIiwic3d2ZXJzaW9uIjoiNC42LjAuODI3NCJ9LCI1Ijp7InN0YXRlIjp7Im9uIjpmYWxzZSwiYnJpIjoyNTQsImh1ZSI6MzUzNDYsInNhdCI6MTc2LCJlZmZlY3QiOiJub25lIiwieHkiOlswLjMyNDIsMC4zMjQ1...[TRUNCATED]
a677c908-1c40-4ed1-b614-60cca12d4b4b 12:20:42 AM: debug Device data: (192.168.254.237:80) - reporting data: (192.168.254.237:80).
b0a9c521-4876-4404-93c9-d5ad6fa4eec8 12:20:42 AM: trace [uuid:38323636-4558-4dda-9188-cda0e6e8824a:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e6e8824a, networkAddress:C0A8FEF5, ssdpNTS:null, deviceAddress:0050, mac:5CCF7FE8824A, devicetype:04, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:38323636-4558-4dda-9188-cda0e6954719:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e6954719, networkAddress:C0A8FEFC, ssdpNTS:null, devicetype:04, mac:5CCF7F954719, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:4dd31a38-693c-aa71-7751-0d7589ea5233::urn:schemas-upnp-org:device:Basic:1:[ssdpUSN:uuid:4dd31a38-693c-aa71-7751-0d7589ea5233::urn:schemas-upnp-org:device:Basic:1, networkAddress:C0A8FE52, ssdpNTS:null, devicetype:04, mac:3CCD93830ACF, deviceAddress:07AA, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:2f402f80-da50-11e1-9b23-0017882f03cf:[ssdpUSN:uuid:2f402f80-da50-11e1-9b23-0017882f03cf, networkAddress:C0A8FEF4, ssdpNTS:null, serialNumber:0017882f03cf, mac:0017882F03CF, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:basic:1, stringCount:04, lastActivity:1489094441702, verified:true, name:Philips hue (2F03CF), devicetype:04, idNumber:2F03CF], uuid:38323636-4558-4dda-9188-cda0e695d55b:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e695d55b, networkAddress:C0A8FEED, ssdpNTS:null, devicetype:04, mac:5CCF7F95D55B, deviceAddress:0050, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-org:device:Basic:1, stringCount:04], uuid:38323636-4558-4dda-9188-cda0e620a75a:[ssdpUSN:uuid:38323636-4558-4dda-9188-cda0e620a75a, networkAddress:C0A8FEFB, ssdpNTS:null, deviceAddress:0050, mac:5CCF7F20A75A, devicetype:04, hub:cb80270e-0b67-4a03-99eb-97252bcc639d, ssdpPath:/description.xml, ssdpTerm:urn:schemas-upnp-or...[TRUNCATED]I think I have found the suspected smart app. the “input color missing” log shows up when a motion is detected by the “lighting director” smart app. but this app does not have anything to do with color. it just turns on/off lights and dimms them.
so why the missing color issue occurs ?
and what about the other logs such as:
"debug Bridge with 5CCF7FE8824A not found"
"debug Device (5CCF7FE8824A) was already found in state with ip = 192.168.254.245:80."Before looking into the invalid color issue let’s address the bridge logs. All of the code that generates those log entries is from the Stock Hue (Connect). Unless I’m mistaken, the Hue Advanced (Connect) SmartApp is not actually finding the bridge as a child device. Could you go into the IDE>My Devices select your Hue Bridge and post a screenshot of the device details page?
so ? do you have any findings ?
So the device that you’re seeing in those logs is not the same as the Hue Advanced Bridge you posted a screenshot of. The device in your log has Device Network Id 5CCF7FE8824A but the device in your screenshot has DNI 0017882F03CF. Could you look for the device with DNI 5CCF7FE8824A and post a screenshot of that? I’m guessing you somehow have two Hue bridges associated with Hue Advanced (Connect).
ok. I got that. it is a sonoff wifi switch and it has no relation with Hue or Hue advanced.
sorry to bother you about that.
now back to my original problem;
I think I have found the suspected smart app. the “input color missing” log shows up when a motion is detected by the “lighting director” smart app. but this app does not have anything to do with color. it just turns on/off lights and dimms them.
so why the missing color issue occurs ?
and I saw this error additionally :
12:05:40 AM: warn groovyx.net.http.HttpResponseException: Forbidden
Well basically some SmartApp is trying to set a color that can’t be set. You have to figure out which SmartApp that is and then we can troubleshoot how it’s sending the color and why you’re seeing the error. To be honest though, if everything is functioning correctly I wouldn’t worry about it.