[SOLVED] Community Rocks!

[baldog]

That explains things! Hopefully he’ll get to me soon

[matt1]

I’m in the same boat. Had an issue with getting a phone to show as a device. Emailed support 1/18 and 1/25. Still nothing.
Completely unacceptable customer service.

[baldog]

Yeah it’s not great! I’ll see if anything happens over the next few days before I return the hub and power smart things back on.

[okellyro]

What’s the problem? Link to any posts?

[2ac16mo]

You might pose your support request here.....many users offer excellent tips and advice.

[baldog]

I've done two posts about it. I think its a bug more than anything though

Semi complicated if this then that rule

That's definitely pink, but it's also off. Did "Current States" report "switch: off" at the time of capture? If done in your rule, you should be turning the bulb on before capture and so it should be on, but I guess it wouldn't hurt to insert a small delay--or a large one when for the purposes of testing so you have time to check the state before the rule captures and then changes it to red--just to be sure it doesn't say this.

Lights go red on contact change

If that first screenshot was indeed created after only manipulating the bulb using the Hubitat device page, I'm not sure how you got there. The bulb is reporting that it's a slightly unsaturated, white-ish green or yellow, not white. To set a Hue bulb accurately to a shade of white, use Set Color Temperature and put in your desired value. I'd suggest around 2700 to 3000 (units are Kelvin, but don't type that) for a warm white. You should see "colorMode: CT" instead of "colorMode: RGB" after that…

[bertabcd1234]

Did you never get that to actually work? There are some suggestions and troubleshooting steps in one or both of those threads that it doesn't seem like you've tried yet (e.g., checking what color mode actually gets saved) as far as I can tell.

[baldog]

nope never got it working in fact the hub is now collecting dust!! The current state reports that the light is red when it is turned off.

[bertabcd1234]

That would be normal. The switch attribute tells you whether the bulb is on or off; the color name attribute (and the actual underlying attributes that go into this: color mode, hue, etc.) will all retain their last values.

[baldog]

looking at the evnt log i can see the state captured when the bulb is on and it returns to that state on close. However when the bulb is off I cant see it restoring that state before it turns off

[baldog]

event log

app:1342020-02-05 03:29:06.653 pm infoAction: END-IF

app:1342020-02-05 03:29:06.649 pm infoAction: END-IF

app:1342020-02-05 03:29:06.588 pm infoAction: Off: Office lamp

app:1342020-02-05 03:29:06.558 pm infoDelay Over: Delay 0:00:00.3

app:1342020-02-05 03:29:06.155 pm infoAction: Delay 0:00:00.3

app:1342020-02-05 03:29:06.087 pm infoAction: Restore: Office lamp

app:1342020-02-05 03:29:06.080 pm infoAction: IF (Variable Was on(false) = false(T) [TRUE]) THEN

app:1342020-02-05 03:29:05.956 pm infoDelay Over: Delay 0:00:03

dev:92020-02-05 03:29:03.446 pm infoGroup Office saturation was set to 100%

dev:92020-02-05 03:29:03.443 pm infoGroup Office hue was set to 100%

dev:92020-02-05 03:29:03.440 pm infoGroup Office level was set to 50%

dev:92020-02-05 03:29:03.437 pm infoGroup Office was turned off

dev:42020-02-05 03:29:02.895 pm infoOffice lamp was turned off

app:1342020-02-05 03:29:02.791 pm infoAction: Delay 0:00:03

app:1342020-02-05 03:29:02.718 pm infoAction: Restore: Office lamp

app:1342020-02-05 03:29:02.715 pm infoAction: ELSE (do actions)

app:1342020-02-05 03:29:02.712 pm infoAction: Set color: Office lamp ->Red ->Level: 50 (skipped)

app:1342020-02-05 03:29:02.705 pm infoAction: Delay 0:00:00.5 (skipped)

app:1342020-02-05 03:29:02.701 pm infoAction: Capture: Office lamp (skipped)

app:1342020-02-05 03:29:02.694 pm infoAction: On: Office lamp (skipped)

app:1342020-02-05 03:29:02.688 pm infoAction: END-IF (skipped)

app:1342020-02-05 03:29:02.684 pm infoAction: Set Was on to false (skipped)

app:1342020-02-05 03:29:02.679 pm infoAction: ELSE (skipped)

app:1342020-02-05 03:29:02.675 pm infoAction: Set Was on to true (skipped)

app:1342020-02-05 03:29:02.669 pm infoAction: IF (Office lamp(on) is on(T) [TRUE]) THEN (skipped)

app:1342020-02-05 03:29:02.633 pm infoAction: IF (Bi Fold Door open(F) [FALSE]) THEN (skipping)

app:1342020-02-05 03:29:02.559 pm infoDoor Open Test Triggered

app:1342020-02-05 03:29:02.545 pm infoDoor Open Test: Bi Fold Door contact closed

dev:112020-02-05 03:29:02.337 pm infoBi Fold Door: contact is closed

dev:42020-02-05 03:28:03.802 pm infoOffice lamp saturation was set to 100%

dev:42020-02-05 03:28:03.785 pm infoOffice lamp hue was set to 100%

dev:42020-02-05 03:28:03.778 pm infoOffice lamp level was set to 50%

app:1342020-02-05 03:28:03.765 pm infoAction: END-IF

app:1342020-02-05 03:28:03.761 pm infoAction: END-IF (skipped)

app:1342020-02-05 03:28:03.756 pm infoAction: Off: Office lamp (skipped)

app:1342020-02-05 03:28:03.748 pm infoAction: Delay 0:00:00.3 (skipped)

app:1342020-02-05 03:28:03.743 pm infoAction: Restore: Office lamp (skipped)

app:1342020-02-05 03:28:03.738 pm infoAction: IF (Variable Was on(false) = false(T) [TRUE]) THEN (skipped)

app:1342020-02-05 03:28:03.611 pm infoAction: Delay 0:00:03 (skipped)

app:1342020-02-05 03:28:03.607 pm infoAction: Restore: Office lamp (skipped)

app:1342020-02-05 03:28:03.599 pm infoAction: ELSE (skipping)

app:1342020-02-05 03:28:03.513 pm infoAction: Set color: Office lamp ->Red ->Level: 50

app:1342020-02-05 03:28:03.475 pm infoDelay Over: Delay 0:00:00.5

dev:42020-02-05 03:28:02.930 pm infoOffice lamp was turned on

[bertabcd1234]

Did you cut off anything in the logs? It looks like something might be missing. (When you open the contact sensor, you should see a line for Action: IF (Bi Fold Door open(T) [TRUE]) THEN, similar to what you see when it's closed but without the skipping. This should be one of the first lines in the log. Your logs appear to start right after the On: Office Lamp action. If this is really the whole thing, something is wrong with the earlier parts of the rule and they are not running (or at least not getting logged) for some reason.

Checking what RM actually saves, as you did here, would also be a good idea to pinpoint whether it's the capture or restore that seems to be problematic. Also, free to insert delays between actions when you're testing, more than you'd use in real life, if that makes it easier to troubleshoot and see what is happening when.

[baldog]

it is there i missed it!

app:1342020-02-05 03:29:06.653 pm infoAction: END-IF

app:1342020-02-05 03:29:06.649 pm infoAction: END-IF

app:1342020-02-05 03:29:06.588 pm infoAction: Off: Office lamp

app:1342020-02-05 03:29:06.558 pm infoDelay Over: Delay 0:00:00.3

app:1342020-02-05 03:29:06.155 pm infoAction: Delay 0:00:00.3

app:1342020-02-05 03:29:06.087 pm infoAction: Restore: Office lamp

app:1342020-02-05 03:29:06.080 pm infoAction: IF (Variable Was on(false) = false(T) [TRUE]) THEN

app:1342020-02-05 03:29:05.956 pm infoDelay Over: Delay 0:00:03

dev:92020-02-05 03:29:03.446 pm infoGroup Office saturation was set to 100%

dev:92020-02-05 03:29:03.443 pm infoGroup Office hue was set to 100%

dev:92020-02-05 03:29:03.440 pm infoGroup Office level was set to 50%

dev:92020-02-05 03:29:03.437 pm infoGroup Office was turned off

dev:42020-02-05 03:29:02.895 pm infoOffice lamp was turned off

app:1342020-02-05 03:29:02.791 pm infoAction: Delay 0:00:03

app:1342020-02-05 03:29:02.718 pm infoAction: Restore: Office lamp

app:1342020-02-05 03:29:02.715 pm infoAction: ELSE (do actions)

app:1342020-02-05 03:29:02.712 pm infoAction: Set color: Office lamp ->Red ->Level: 50 (skipped)

app:1342020-02-05 03:29:02.705 pm infoAction: Delay 0:00:00.5 (skipped)

app:1342020-02-05 03:29:02.701 pm infoAction: Capture: Office lamp (skipped)

app:1342020-02-05 03:29:02.694 pm infoAction: On: Office lamp (skipped)

app:1342020-02-05 03:29:02.688 pm infoAction: END-IF (skipped)

app:1342020-02-05 03:29:02.684 pm infoAction: Set Was on to false (skipped)

app:1342020-02-05 03:29:02.679 pm infoAction: ELSE (skipped)

app:1342020-02-05 03:29:02.675 pm infoAction: Set Was on to true (skipped)

app:1342020-02-05 03:29:02.669 pm infoAction: IF (Office lamp(on) is on(T) [TRUE]) THEN (skipped)

app:1342020-02-05 03:29:02.633 pm infoAction: IF (Bi Fold Door open(F) [FALSE]) THEN (skipping)

app:1342020-02-05 03:29:02.559 pm infoDoor Open Test Triggered

[bertabcd1234]

What triggered your rule? If it was the contact sensor opening, the second (from bottom) log entry looks a bit odd, since if the sensor was opened, you should see something like:

Action: IF (Bi Fold Door open(T) [TRUE]) THEN

I'm guessing the logs still aren't complete, assuming you've verified the contact sensor sends the correct data.

[baldog]

It was the contact sensor change state. I can put the full log up again if you would like me to?

[PPz]

Even I agree to your comment and I'm still a happy HE customer, Support is part of the deal.

HE is not open source and skilled forum users, from @bertabcd1234 to @zarthan (without forgetting @Ryan780) and many others are ready to help us.
But because new users are coming days after days, help/support messages can be lost in the message flow. And @bobbyD can be drowned with them.

I don't need real full support here (we're all DIYers) and forum helpers are very patient and skilled. But I understand that you (we) expect some replies. But what can you (we) do if your (our) question is not read by others ?

I think that a forum is complementary to support, not a substitute for it.

Anyway, this is not particular to HE. When you buy stuff on Aliexpress, be prepared for unsolved questions

[april.brandt]

@PPz

I think that a forum is complementary to support, not a substitute for it.

I get it, but Bobby being solo right now, he has to "pick his battles" so to speak. He's doing his best to keep up. If I looked at a question and know that the forum could help answer that, I'd move on to something that can't be answered in the forum. Like a dead hub or corrupt database, hub registration being difficult. It's unfortunate that there aren't 25 support people kissing our asses to keep everyone happy, but I have never reached out to support unless I thought database or equipmnet was the issue. Even then it was just to ask them to have a look. Considering HE is still young and their business decisions need to be sound in order to be successful, this forum has to pick up some of that load. There are a lot of great minds here. I'd personally rather ask here because the answers are instantaneous. And almost everyone is fun. I'm an instant gratification kind of person, so I need interaction. I find that here. Keep in mind this is my humble opinion on this topic. I'm not a developer, I don't know code. I'm just a girl with some good ideas. But, I'll help when I can.

[epj3]

@baldog

power smart things back on.

Look, I get your frustration. But you posted this at the exact same time that this thread was posted on Reddit. I guess each person is free to choose their battles.

Major Outage For Smartthings Users In North America

[JasonJoel]

@april.brandt

I get it, but Bobby being solo right now, he has to "pick his battles" so to speak. He's doing his best to keep up.

If Bobby is actually "on his own" (I've never seen that actually confirmed by Hubitat), that is still Hubitat's fault not the customer's.

It isn't unreasonable for customers to expect a "reasonable" turnaround time on support requests. And yes, I fully understand "reasonable" is a subjective measure.

I think expecting customers to be understanding when support is understaffed is a little unrealistic, though.

While I think Bobby does a GREAT job, I empathize with paying customers requests going into the great bit bucket in the sky...

[greg4]

I too have had a support issue fade away into this blackhole. It's really frustrating particularly when there is a lack of communication. I hate to pester @bobbyD when I know he is probably underwater but sometimes if you just don't make noise about something it gets lost in the mix. Either way the support capacity is something that needs fixing.