When The Lights Out

[Egisto Chancellor]

AndI've noticed that when the lights turn off, The Darwin clownfish seems freely around the whole tank, but as soon as the lights go back on, the clownfish goes right back into the top left corner facing downards.

Unfortunately, yep. Sometimes a pair will swim around, sometimes they'll find a host anemone, and sometimes they just swim in a corner. If you turn off the flow, sometimes they start swimming around again (until you turn the pumps back on). They'll be absolutely fine like this, but it is a little annoying. Sometimes their behavior changes in a different tank.

My clownfish are corner egg layers, no coral (or a giant BTA) interests them. The bigger one is the female and she's probably at the stage where she's looking for where to lay eggs. This lasted months for me until the egg laying finally happened. Now mama clown is all over the tank while the male is the guardian of the spot.

Table of Contents Title 46.2. Motor Vehicles Subtitle III. Operation Chapter 10. Motor Vehicle and Equipment Safety Article 3. Lights and Turn Signals 46.2-1030. When lights to be lighted; number of lights to be lighted at any time; use of warning lights

A. Every vehicle in operation on a highway in the Commonwealth shall display lighted headlights and illuminating devices as required by this article (i) from sunset to sunrise; (ii) during any other time when, because of rain, smoke, fog, snow, sleet, insufficient light, or other unfavorable atmospheric conditions, visibility is reduced to a degree whereby persons or vehicles on the highway are not clearly discernible at a distance of 500 feet; and (iii) whenever windshield wipers are in use as a result of fog, rain, sleet, or snow. The provisions of this subsection, however, shall not apply to instances when windshield wipers are used intermittently in misting rain, sleet, or snow.

B. Not more than four lights used to provide general illumination ahead of the vehicle, including at least two headlights and any other combination of fog lights or other auxiliary lights approved by the Superintendent, shall be lighted at any time. However, motorcycles may be equipped with and use not more than five approved lights in order to provide general illumination ahead of the motorcycle. These limitations shall not preclude the display of warning lights authorized in 46.2-1020 through 46.2-1027, or other lights as may be authorized by the Superintendent.

C. Vehicles equipped with warning lights authorized in 46.2-1020 through 46.2-1027 shall display lighted warning lights as authorized in such sections at all times when responding to emergency calls, responding to traffic incidents, responding to metropolitan transit-related incidents, towing disabled vehicles, or constructing, repairing, and maintaining public highways or utilities on or along public highways, except that amber lights on vehicles designed with a ramp on wheels and a hydraulic lift with a capacity to haul or tow another vehicle, commonly referred to as "rollbacks," need not be lit while the vehicle is in motion unless it is actually towing a vehicle.

D. The failure to display lighted headlights and illuminating devices under the conditions set forth in clause (iii) of subsection A shall not constitute negligence per se, nor shall violation of clause (iii) of subsection A constitute a defense to any claim for personal injury or recovery of medical expenses for injuries sustained in a motor vehicle accident.

F. No citation for a violation of clause (iii) of subsection A shall be issued unless the officer issuing such citation has cause to stop or arrest the driver of such motor vehicle for the violation of some other provision of this Code or local ordinance relating to the operation, ownership, or maintenance of a motor vehicle or any criminal statute. No law-enforcement officer shall stop a motor vehicle for a violation of this section, except that a law-enforcement officer may stop a vehicle if it displays no lighted headlights during the time periods set forth in subsection A. No evidence discovered or obtained as the result of a stop in violation of this subsection, including evidence discovered or obtained with the operator's consent, shall be admissible in any trial, hearing, or other proceeding.

Hi All,

I'm new to the Hubitat world. I have been using ISY994i with an all Insteon system for a few years. With the imminent demise (seemingly) of Insteon, I decided it was time for something more open, and Z-wave looked good to me. After that, I settled on Hubitat, since it looked like it might be similar in capabilites to ISY994i. So far I'm impressed with how much easier some things are.

But, I'm stuck trying to program something that I feel should be pretty basic. I have one light switch controlling one light, and a Z-wave motion sensor. I want to add motion sensing to the light (easy), but also have an override via the switch, whereas, if you turn on the light via the switch, it should stay on until switched off. This is a typical scenario for a porch light. Once manually turned off, motion sensing would resume.

I have done this with a basement light. What I ended up doing is using a switch that had double taps. Those double taps turn on a virtual switch using one rule. Double tap up turns on the virtual switch, and double tap off turns it off.

Then use that virtual switch in the Motion Lighting app "additional switches to keep on" or whatever that exact setting is called. If the virtual switch is on, lights stay on. If virtual switch is off, the Motion Lighting works like normal.

Excuse the 2 screenshots, I have not figured out how to grab a multi page rule. I believe this might be what you're looking for. This rule controls a bathroom vanity light with motion from a Hue sensor but the rule has a timer that is not wanted at certain times. Turning on the light from the switch disables the rule so the light stays on when needed.

Thanks for all the quick replies guys! Let me digest all this and see if I can get it to work. It seems like the Rule Machine is the way most of you are doing this. I'm actually a bit surprised this isn't built into the Motion app, since this seems to me like a pretty "standard" feature for a motion light.

It is, but the ML app from what I have experienced expects a second switch to do the override. If you use the same switch for normal operation and for the override you probably will be in a logic loop of some type.

That is why I used the double tap as it acts like a different device. You also could use an entirely different switch or even a button remote to accomplish this. The second rule I mention is to convert a button press (double tap on most devices is a button) into a switch because at the time I set this up ML did not have the button press disable feature just to the right and one row up on the outline in my second picture below.

I think I did try that and there was some use case where it didn't work like I wanted to. Maybe I need to go back and try it again. Same as with the button to disable, there are new and improved options since I set things up. It works, and I rarely play with automations once they are working like I want them to.

I tried that, and it didn't work. But then I noticed pretty much nothing was working. I stripped out all the override stuff, back to a dead simple motion circuit (what I started with). Still not working. Something is amiss. I may delete the rule completely and start over. Out of time for tonight though...

So, I got the setup working again by deleting it and setting up again. Just basic motion sensing. Then I turned on the "Don't turn off if already on" switch. I turned on the light manually, but after a time, the light still went off on its own. So, I'm not sure what this switch does, but I don't see different behavior with it on.

I'll try playing with the Rule Machine.

So, in my implementation above, there is an issue, which is this: since I am using the light-on status to inhibit the motion, the light will always go off after the predetermined time, in this case 1 minute. It won't retrigger since the light is on, which inhibits retriggering. It's only after the light goes out that it can retrigger. Not ideal.

I came up with another solution that I like better, where the motion sensor works normally, except when a global variable is set. I used a "hub variable", and set it when the switches on button is pressed, and clear it when the off button is pressed.

So, I got the setup working again by deleting it and setting up again. Just basic motion sensing. Then I turned on the "Don't turn off if already on" switch. I turned on the light manually, but after a time, the light still went off on its own. So, I'm not sure what this switch does, but I don't see different behavior with it on.

No, I can't explain it. I don't really understand what this option does. Based on it's name, it sounds like once the light is on (even if from motion), it would never go off, but that's probably not what you would want. Unfortunately I don't have time to go back and debug this, since I have something working now.

3a8082e126