[RELEASE] Event Engine - Automate your world with easy to use Cogs. Rev up complex automations with just a few clicks!

@bptworld - thanks for the quick response. When I ran HPM to grab the update, I noticed I still had the old Cog. So I had to delete all my event rules then delete the old Cog so that 3.4.1 took effect. It's not working as expected. See my notes in the log screen capture.


I would need to see the debug log from the app.

i installed the event engine but i didnt find the lighting effects.

What are you trying to do?

I was looking for the lighting effects app. which is integrated into , in theory.

It is integrated, not in theory but in reality. If you told me what you were looking to do, I could have told you where to look. But half the fun is figuring things out on your own I guess.

3 Likes

I am using a humidity sensor in my bathroom. The fan is controlled by a broadlink device. The broadlink device is sending RF cmd to the fan. I have built out the cog as fellows

indent preformatted text by 4 spaces

Event Engine Cog (3.4.3) - Master Bathroom - Fan (Paused) (958)
Conditions

  • Cog will fire when ALL Condition are true (Using AND)
  • By Humidity Setpoints: [MBA - Amosphere] - setpoint Low: 70, setpoint High: 100, inBetween: NA
  • Setpoint Options: Rolling Average: false - Use Whole Numbers: true - ResetTime: NA - Direction: NA - Min Change: NA
    Actions
  • Switches to turn On: [MBA-Fan]
  • Reverse High: false - Reverse Low: true - Reverse Not Between: NA
  • Delay Between Actions: 1000

But the fan seems to be cycling on and off. Now the ON cmd is the same as the OFF cmd. My thought is if the humidity flux in the range the cog fire each time? Is there a way to only send the cmd once its is stays in the range?

I'll look into it. Thanks

Thanks

New version on GitHub...

3.4.4 - 01/22/22 - Added App Debounce Option, Added Custom Colors Option, Fixed typo in Switches In Sequence

3 Likes

Hi Bryan,

A bit before Christmas, Hubitat implemented a native Lifx driver in Hubitat. I have been using Rob's driver before that and even if there were some problems with it, Event Engine worked well with all of the Lifx strips and lamps. So I switched to Hubitats version but Event Engine doesn't work well with the lights. I get blinding thite light during the night and the strips cycle White,Blue,Red when turning ON or OFF.

Is there a way to make this work ?

Here is a log (Hubitat Log) of what I can see: (EE log at the end)
I included only one "Zone" for simplicity (Hubitat now creates devices for each zone of a strip and lifx uses 8 zones per 1 meter strip

dev:52452022-01-25 10:30:19.793 infoMarches switch is on

dev:52762022-01-25 10:30:19.523 infoMarches - Zone 1 level is 35%

dev:52762022-01-25 10:30:19.521 infoMarches - Zone 1 switch is on

dev:52762022-01-25 10:30:19.518 infoMarches - Zone 1 colorName is Cyan

dev:52762022-01-25 10:30:19.516 infoMarches - Zone 1 colorMode is RGB

dev:52762022-01-25 10:30:19.512 infoMarches - Zone 1 colorTemperature is 2800°K

dev:52762022-01-25 10:30:19.504 infoMarches - Zone 1 saturation is 19

dev:52762022-01-25 10:30:19.502 infoMarches - Zone 1 hue is 52

dev:52452022-01-25 10:30:19.196 infoMarches color is #485759

dev:52452022-01-25 10:30:19.193 infoMarches level is 35%

dev:35862022-01-25 10:30:19.104 infoCongélateur du Sous-Sol power is 61.709 W

dev:52452022-01-25 10:30:17.308 errorgroovy.lang.MissingMethodException: No signature of method: LifxStrip.setColorTemperature() is applicable for argument types: (java.lang.String) values: [3000] Possible solutions: setColorTemperature(java.lang.Number), setColorTemperature(java.lang.Number, java.lang.Number), setColorTemperature(java.lang.Number, java.lang.Number, java.lang.Number) on line 5631 (method setColorTemperature)

And here is the Event Engine log :

app:62382022-01-25 10:42:44.564 trace*

app:62382022-01-25 10:42:44.562 trace********************* End - startTheProcess (3.4.4) - Éclairage - Marche - appStatus: active *********************

app:62382022-01-25 10:42:44.526 debugIn startTheProcess - Reverse - Will warn 10 seconds before Reverse

app:62382022-01-25 10:42:44.523 debugIn startTheProcess - Reverse-sdTimePerMode - No Match

app:62382022-01-25 10:42:44.521 debugIn startTheProcess - Reverse-sdTimePerMode - theMode: Projecteur - theTime: 15 - theTimeType: true

app:62382022-01-25 10:42:44.518 debugIn startTheProcess - Reverse-sdTimePerMode - No Match

app:62382022-01-25 10:42:44.516 debugIn startTheProcess - Reverse-sdTimePerMode - theMode: Réveil - theTime: 15 - theTimeType: true

app:62382022-01-25 10:42:44.514 debugIn startTheProcess - Reverse-sdTimePerMode - No Match

app:62382022-01-25 10:42:44.511 debugIn startTheProcess - Reverse-sdTimePerMode - theMode: Nuit - theTime: 15 - theTimeType: true

app:62382022-01-25 10:42:44.509 debugIn startTheProcess - Reverse-sdTimePerMode - No Match

app:62382022-01-25 10:42:44.506 debugIn startTheProcess - Reverse-sdTimePerMode - theMode: Soir - theTime: 15 - theTimeType: true

app:62382022-01-25 10:42:44.503 debugIn startTheProcess - Reverse - Delay is set for 15 minute(s) (theDelay: 15)

app:62382022-01-25 10:42:44.500 debugIn startTheProcess - Reverse-sdTimePerMode - currentMode: Jour - modeCheck: true - timeTo: 15 - theTimeType: true

app:62382022-01-25 10:42:44.497 debugIn startTheProcess - Reverse-sdTimePerMode - theMode: Jour - theTime: 15 - theTimeType: true

app:62382022-01-25 10:42:44.495 debugIn startTheProcess - Reverse-sdTimePerMode

app:62382022-01-25 10:42:44.492 debugIn startTheProcess - SETTING UP DELAY REVERSE

app:62382022-01-25 10:42:44.490 debugIn checkingWhatToDo - ********** whatToDo: reverse **********

app:62382022-01-25 10:42:44.487 debugIn checkingWhatToDo - Reverse

app:62382022-01-25 10:42:44.484 warnIn checkingWhatToDo - everythingOK: false

app:62382022-01-25 10:42:44.481 warnIn checkingWhatToDo - USING OR - totalMatch: 0 - totalMatchHelper: 0 - setpointOK: false - transitionOK: false - securityOK: false

app:62382022-01-25 10:42:44.479 debugIn checkingWhatToDo (3.4.4)

app:62382022-01-25 10:42:44.476 debugIn startTheProcess - NOT using transitions - Setting value based on triggerAndOr: true

app:62382022-01-25 10:42:44.474 debugIn startTheProcess - NOT using Setpoint Devices - Setting value based on triggerAndOr: true

app:62382022-01-25 10:42:44.472 debugIn startTheProcess - NOT using Security Keypad - Setting value based on triggerAndOr: true

app:62382022-01-25 10:42:44.469 debugIn deviceHandler - (condition) - MOTION - OR - count: 2 - totalMatch: 0 - totalConditions: 2

app:62382022-01-25 10:42:44.467 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-25 10:42:44.464 debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 2 - typeAO: true

app:62382022-01-25 10:42:44.462 debugIn deviceHandler - Adding to deviceTrue2: 2

app:62382022-01-25 10:42:44.460 debugIn deviceHandler - Working 2: inactive and Current Value: inactive

app:62382022-01-25 10:42:44.457 debugIn deviceHandler - Checking: MS Escalier - motion - Testing Current Value - inactive

app:62382022-01-25 10:42:44.455 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-25 10:42:44.453 debugIn deviceHandler - Working 2: inactive and Current Value: inactive

app:62382022-01-25 10:42:44.450 debugIn deviceHandler - Checking: MS Marche - motion - Testing Current Value - inactive

app:62382022-01-25 10:42:44.448 debugIn deviceHandler (3.4.4) - MOTION - data: condition

app:62382022-01-25 10:42:44.445 debugIn deviceHandler - (condition) - CONTACT - OR - count: 1 - totalMatch: 0 - totalConditions: 1

app:62382022-01-25 10:42:44.443 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-25 10:42:44.440 debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 1 - typeAO: true

app:62382022-01-25 10:42:44.438 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-25 10:42:44.436 debugIn deviceHandler - Working 2: closed and Current Value: closed

app:62382022-01-25 10:42:44.434 debugIn deviceHandler - Checking: Porte Vestibule - contact - Testing Current Value - closed

app:62382022-01-25 10:42:44.431 debugIn deviceHandler (3.4.4) - CONTACT - data: condition

app:62382022-01-25 10:42:44.429 debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: true - snRestric: null

app:62382022-01-25 10:42:44.427 debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true - snMatch: true

app:62382022-01-25 10:42:44.424 debugIn safetyNetHandler - Safety Net NOT being used - snMatch: true

app:62382022-01-25 10:42:44.422 debugIn hsmStatusHandler - NOT being used.

app:62382022-01-25 10:42:44.420 debugIn hsmAlertHandler - NOT being used.

app:62382022-01-25 10:42:44.418 debugIn modeHandler - modeMatch PASSED - modeMatch: true

app:62382022-01-25 10:42:44.415 debugIn modeHandler - Mode NOT being used - modeMatch: true

app:62382022-01-25 10:42:44.413 debugIn modeHandler (3.4.4)

app:62382022-01-25 10:42:44.411 debugIn dayOfTheWeekHandler - daysMatch PASSED - daysMatch: true

app:62382022-01-25 10:42:44.409 debugIn dayOfTheWeek (3.4.4)

app:62382022-01-25 10:42:44.407 debug********** In checkSunHandler - timeBetweenSun: true **********

app:62382022-01-25 10:42:44.404 debugIn checkSunHandler - sunrise/sunset NOT being used - timeBetweenSun: true

app:62382022-01-25 10:42:44.402 debug********** In checkSunHandler (3.4.4) - timeDaysType: - **********

app:62382022-01-25 10:42:44.400 debugIn startTheProcess - whoHappened: MS Marche - whatHappened: inactive - whoText: MS Marche: motion is inactive

app:62382022-01-25 10:42:44.394 trace******************** Start - startTheProcess (3.4.4) - Éclairage - Marche - appStatus: active ********************

app:62382022-01-25 10:42:44.392 trace*

Thank-you !

Couple of thoughts....

  1. Hubitat doesn't offer a Virtual Lifx Device so I have no way of testing.
  2. Please provide a screenshot of the debug log of EE using the strip, must show what it was doing before the error.
  3. Please provide a screenshot off how you have the light setup in EE.
  4. A screenshot of the device page (including the commands and attributes) might help too since I've never seen what a Lifx bulb can do or looks like.

Thanks

New version on GitHub...

Minor changes.

1 Like

I'm reinstalling Rob's driver to test the difference, I'll let you know after testing

Thank-you

Here is the log with the debug enabled: (using Rob's lifx driver)

The thing I noted is that when using Hubitat's built-in driver, the burst of light happens once when there is a change from pure white to color and color to white (I mostly use red for night and projector mode, 2700 White for morning and evening and 3000K for Day mode.

app:62382022-01-26 13:55:33.972 trace********************* End - startTheProcess (3.4.5) - Éclairage - Marche - appStatus: active *********************

app:62382022-01-26 13:55:33.913 debugIn switchesPerModeActionHandler - currentMode: Jour - modeCheck: false

app:62382022-01-26 13:55:33.910 debugIn switchesPerModeActionHandler - currentMode: Jour - modeCheck: false

app:62382022-01-26 13:55:33.908 debugIn switchesPerModeActionHandler - currentMode: Jour - modeCheck: false

app:62382022-01-26 13:55:33.905 debugIn switchesPerModeActionHandler - currentMode: Jour - modeCheck: false

app:62382022-01-26 13:55:33.435 debugIn setLevelandColorHandler - switchesPerMode - setColorTemp - Marches, setColorTemp(3000)

app:62382022-01-26 13:55:33.432 debugIn setLevelandColorHandler - switchesPerMode - setColor - OLD STATUS - oldStatus: Marches - off::51.17::19.0::12.0::3000::null

app:62382022-01-26 13:55:33.430 debugIn setLevelandColorHandler - alreadyThere: false

app:62382022-01-26 13:55:33.427 debugIn setLevelandColorHandler - switchesPerMode - Working on: Marches

app:62382022-01-26 13:55:33.425 debugIn setLevelandColorHandler - theMap: [:]

app:62382022-01-26 13:55:33.422 debugIn setLevelandColorHandler - 1 - hue: null - saturation: null - onLevel: 35

app:62382022-01-26 13:55:33.420 debugIn setLevelandColorHandler - fromWhere: switchesPerMode, color: NA - onLevel: 35

app:62382022-01-26 13:55:33.418 debugIn switchesPerModeActionHandler - MATCH - Sending: Marches

app:62382022-01-26 13:55:33.415 debugIn switchesPerModeActionHandler - Comparing cleanOne: Marches - itThree: Marches

app:62382022-01-26 13:55:33.413 debugIn switchesPerModeActionHandler - currentMode: Jour - modeCheck: true

app:62382022-01-26 13:55:33.410 debugIn switchesPerModeActionHandler - (3.4.5)

app:62382022-01-26 13:55:33.408 debugIn startTheProcess - actionType: [aSwitchesPerMode] - Wed Jan 26 13:55:33 EST 2022

app:62382022-01-26 13:55:33.405 debugIn certainTimeHasPassedHandler - state.certainTimeHasPassed: true

app:62382022-01-26 13:55:33.403 debugIn certainTimeHasPassedHandler (3.4.5)

app:62382022-01-26 13:55:33.401 debugIn startTheProcess - HERE WE GO! - whatToDo: run

app:62382022-01-26 13:55:33.398 debugIn startTheProcess - appStatus: inactive

app:62382022-01-26 13:55:33.396 debugIn checkingWhatToDo - ********** whatToDo: run **********

app:62382022-01-26 13:55:33.394 debugIn checkingWhatToDo - Run

app:62382022-01-26 13:55:33.391 debugIn checkingWhatToDo - everythingOK: true

app:62382022-01-26 13:55:33.389 warnIn checkingWhatToDo - USING OR - totalMatch: 1 - totalMatchHelper: 0 - setpointOK: false - transitionOK: false - securityOK: false

app:62382022-01-26 13:55:33.387 debugIn checkingWhatToDo (3.4.5)

app:62382022-01-26 13:55:33.384 debugIn startTheProcess - NOT using transitions - Setting value based on triggerAndOr: true

app:62382022-01-26 13:55:33.382 debugIn startTheProcess - NOT using Setpoint Devices - Setting value based on triggerAndOr: true

app:62382022-01-26 13:55:33.380 debugIn startTheProcess - NOT using Security Keypad - Setting value based on triggerAndOr: true

app:62382022-01-26 13:55:33.377 debugIn deviceHandler - (condition) - MOTION - OR - count: 2 - totalMatch: 1 - totalConditions: 2

app:62382022-01-26 13:55:33.375 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-26 13:55:33.372 debugIn deviceHandler - (condition) - type: true - deviceMatch: 1 - theCount: 2 - typeAO: true

app:62382022-01-26 13:55:33.370 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-26 13:55:33.368 debugIn deviceHandler - Working 2: inactive and Current Value: inactive

app:62382022-01-26 13:55:33.365 debugIn deviceHandler - Checking: MS Escalier - motion - Testing Current Value - inactive

app:62382022-01-26 13:55:33.363 debugIn deviceHandler - Adding to deviceTrue1: 1

app:62382022-01-26 13:55:33.361 debugIn deviceHandler - Working 1: active and Current Value: active

app:62382022-01-26 13:55:33.358 debugIn deviceHandler - Checking: MS Marche - motion - Testing Current Value - active

app:62382022-01-26 13:55:33.356 debugIn deviceHandler (3.4.5) - MOTION - data: condition

app:62382022-01-26 13:55:33.354 debugIn deviceHandler - (condition) - CONTACT - OR - count: 1 - totalMatch: 0 - totalConditions: 1

app:62382022-01-26 13:55:33.309 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-26 13:55:33.307 debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 1 - typeAO: true

app:62382022-01-26 13:55:33.305 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-26 13:55:33.303 debugIn deviceHandler - Working 2: closed and Current Value: closed

app:62382022-01-26 13:55:33.300 debugIn deviceHandler - Checking: Porte Vestibule - contact - Testing Current Value - closed

app:62382022-01-26 13:55:33.298 debugIn deviceHandler (3.4.5) - CONTACT - data: condition

app:62382022-01-26 13:55:33.296 debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: true - snRestric: null

app:62382022-01-26 13:55:33.293 debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true - snMatch: true

app:62382022-01-26 13:55:33.291 debugIn safetyNetHandler - Safety Net NOT being used - snMatch: true

app:62382022-01-26 13:55:33.289 debugIn hsmStatusHandler - NOT being used.

app:62382022-01-26 13:55:33.286 debugIn hsmAlertHandler - NOT being used.

app:62382022-01-26 13:55:33.284 debugIn modeHandler - modeMatch PASSED - modeMatch: true

app:62382022-01-26 13:55:33.282 debugIn modeHandler - Mode NOT being used - modeMatch: true

app:62382022-01-26 13:55:33.280 debugIn modeHandler (3.4.5)

app:62382022-01-26 13:55:33.278 debugIn dayOfTheWeekHandler - daysMatch PASSED - daysMatch: true

app:62382022-01-26 13:55:33.275 debugIn dayOfTheWeek (3.4.5)

app:62382022-01-26 13:55:33.273 debug********** In checkSunHandler - timeBetweenSun: true **********

app:62382022-01-26 13:55:33.271 debugIn checkSunHandler - sunrise/sunset NOT being used - timeBetweenSun: true

app:62382022-01-26 13:55:33.269 debug********** In checkSunHandler (3.4.5) - timeDaysType: - **********

app:62382022-01-26 13:55:33.266 debugIn startTheProcess - whoHappened: MS Marche - whatHappened: active - whoText: MS Marche: motion is active

app:62382022-01-26 13:55:33.261 trace******************** Start - startTheProcess (3.4.5) - Éclairage - Marche - appStatus: inactive ********************

app:62382022-01-26 13:55:33.259 trace*

app:58452022-01-26 13:55:33.220 infoÉclairage - Aquarium is Paused or Disabled

dev:52352022-01-26 13:55:33.126 infoMS Salon: motion is active

app:58452022-01-26 13:55:33.104 infoÉclairage - Aquarium is Paused or Disabled

app:62382022-01-26 13:55:33.081 debugIn startTheProcess - Starting - appStatus: inactive

dev:4812022-01-26 13:55:33.045 infoMS Marche: motion is active

app:62382022-01-26 13:55:31.013 trace*

app:62382022-01-26 13:55:31.011 trace********************* End - startTheProcess (3.4.5) - Éclairage - Marche - appStatus: inactive *********************

app:62382022-01-26 13:55:30.943 debugIn switchesPerModeReverseActionHandler - oldMap: [:]

app:62382022-01-26 13:55:30.939 debugIn switchesPerModeReverseActionHandler - Removing Marches from oldMap.

app:62382022-01-26 13:55:30.726 debugIn switchesPerModeReverseActionHandler - setColor - Turning light off (Marches)

app:62382022-01-26 13:55:30.481 debugIn switchesPerModeReverseActionHandler - setColor - Reversing Light: Marches - oldStatus: on - theValue: [hue:null, saturation:null, level:null] - trueReverse: true

app:62382022-01-26 13:55:30.478 debugIn switchesPerModeReverseActionHandler - Using setColor

app:62382022-01-26 13:55:30.472 errorjava.lang.NumberFormatException: For input string: "51.95" on line 4368

app:62382022-01-26 13:55:30.468 debugIn switchesPerModeReverseActionHandler - Working on Marches

app:62382022-01-26 13:55:30.464 debugIn startTheProcess - GOING IN REVERSE - appStatus: inactive

app:62382022-01-26 13:55:30.462 debugIn checkingWhatToDo - ********** whatToDo: reverse **********

app:62382022-01-26 13:55:30.458 debugIn checkingWhatToDo - Reverse

app:62382022-01-26 13:55:30.456 warnIn checkingWhatToDo - everythingOK: false

app:62382022-01-26 13:55:30.453 warnIn checkingWhatToDo - USING OR - totalMatch: 0 - totalMatchHelper: 0 - setpointOK: false - transitionOK: false - securityOK: false

app:62382022-01-26 13:55:30.450 debugIn checkingWhatToDo (3.4.5)

app:62382022-01-26 13:55:30.448 debugIn startTheProcess - NOT using transitions - Setting value based on triggerAndOr: true

app:62382022-01-26 13:55:30.446 debugIn startTheProcess - NOT using Setpoint Devices - Setting value based on triggerAndOr: true

app:62382022-01-26 13:55:30.443 debugIn startTheProcess - NOT using Security Keypad - Setting value based on triggerAndOr: true

dev:12182022-01-26 13:55:30.440 errororg.codehaus.groovy.runtime.metaclass.MethodSelectionException: Could not find which method setLevel() to invoke from this list: public java.lang.Object user_driver_codahq_hubitat_HS_WD200__Dimmer_20200118_min10_1089#setLevel(java.lang.Object) public java.lang.Object user_driver_codahq_hubitat_HS_WD200__Dimmer_20200118_min10_1089#setLevel(java.lang.Object, java.lang.Object) on line 4434 (method setLevel)

app:62382022-01-26 13:55:30.431 debugIn deviceHandler - (condition) - MOTION - OR - count: 2 - totalMatch: 0 - totalConditions: 2

app:62382022-01-26 13:55:30.428 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-26 13:55:30.426 debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 2 - typeAO: true

app:62382022-01-26 13:55:30.423 debugIn deviceHandler - Adding to deviceTrue2: 2

app:62382022-01-26 13:55:30.421 debugIn deviceHandler - Working 2: inactive and Current Value: inactive

app:62382022-01-26 13:55:30.418 debugIn deviceHandler - Checking: MS Escalier - motion - Testing Current Value - inactive

app:62382022-01-26 13:55:30.416 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-26 13:55:30.361 debugIn deviceHandler - Working 2: inactive and Current Value: inactive

app:62382022-01-26 13:55:30.358 debugIn deviceHandler - Checking: MS Marche - motion - Testing Current Value - inactive

app:62382022-01-26 13:55:30.355 debugIn deviceHandler (3.4.5) - MOTION - data: condition

app:62382022-01-26 13:55:30.353 debugIn deviceHandler - (condition) - CONTACT - OR - count: 1 - totalMatch: 0 - totalConditions: 1

app:62382022-01-26 13:55:30.350 debugIn deviceHandler - (condition) - Using OR

app:62382022-01-26 13:55:30.347 debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 1 - typeAO: true

app:62382022-01-26 13:55:30.344 debugIn deviceHandler - Adding to deviceTrue2: 1

app:62382022-01-26 13:55:30.342 debugIn deviceHandler - Working 2: closed and Current Value: closed

app:62382022-01-26 13:55:30.339 debugIn deviceHandler - Checking: Porte Vestibule - contact - Testing Current Value - closed

app:62382022-01-26 13:55:30.336 debugIn deviceHandler (3.4.5) - CONTACT - data: condition

app:62382022-01-26 13:55:30.333 debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: true - snRestric: null

app:62382022-01-26 13:55:30.330 debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true - snMatch: true

app:62382022-01-26 13:55:30.327 debugIn safetyNetHandler - Safety Net NOT being used - snMatch: true

app:62382022-01-26 13:55:30.325 debugIn hsmStatusHandler - NOT being used.

app:62382022-01-26 13:55:30.308 debugIn hsmAlertHandler - NOT being used.

app:62382022-01-26 13:55:30.306 debugIn modeHandler - modeMatch PASSED - modeMatch: true

app:62382022-01-26 13:55:30.303 debugIn modeHandler - Mode NOT being used - modeMatch: true

app:62382022-01-26 13:55:30.301 debugIn modeHandler (3.4.5)

app:62382022-01-26 13:55:30.296 debugIn dayOfTheWeekHandler - daysMatch PASSED - daysMatch: true

app:62382022-01-26 13:55:30.293 debugIn dayOfTheWeek (3.4.5)

app:62382022-01-26 13:55:30.290 debug********** In checkSunHandler - timeBetweenSun: true **********

app:62382022-01-26 13:55:30.287 debugIn checkSunHandler - sunrise/sunset NOT being used - timeBetweenSun: true

app:62382022-01-26 13:55:30.285 debug********** In checkSunHandler (3.4.5) - timeDaysType: - **********

app:62382022-01-26 13:55:30.281 debugIn startTheProcess - whoHappened: MS Escalier - whatHappened: inactive - whoText:

app:62382022-01-26 13:55:30.275 trace******************** Start - startTheProcess (3.4.5) - Éclairage - Marche - appStatus: inactive ********************

app:62382022-01-26 13:55:30.272 trace*

app:51222022-01-26 13:55:30.213 errorjava.lang.NumberFormatException: For input string: "null" on line 4368

app:62382022-01-26 13:55:30.105 debugIn startTheProcess - Starting - appStatus: inactive

Sooo....

You supplied #2... How about 3 and 4?

Screenshot of New Built In Lifx Device:

Screenshot of older Rod Driver Device:

1 Like

Bad news - The errors aren't making much sense and without the Lifx strip to test with, it would be nearly impossible to fix.

Good News - I just ordered a Lifx strip. Hopefully have time this weekend to dig into it. :grin:

Stay turned! lol

1 Like

:flushed: I wasn't expecting you to buy some strips !

You'll enjoy them, these lights are bright and colorful. I think the problem is when switching from color to whites. There's something that Hubitat is doing different and it might have to do with the way they optimissed them. When controlling groups of strips, there is much less popcorning.

Thanks again for all of your great work, I love EE and would not want to go back to Motion Lighting.

Yannick

1 Like

Crazy person, in such a wonderful way. :wink:

2 Likes

Download the Hubitat app