Getting Inovollie BSZ Switch to Function on Hubitat C8 Pro

Get Help Apps
1

I’m having trouble getting my Room Lighting automations to only activate at night.

I’ve set the automation to restrict activation between Sunset → Sunrise, but the app keeps warning that the configuration “does not make sense,” and the lights still try to activate during the day unless I manually turn them on.

I’m trying to prevent any daylight activation and have the automation fire only at night based on motion.

Can someone confirm the correct way to set the time restriction in Room Lighting so that daytime activation is fully blocked?

2

It would probably be more helpful to share a screenshot of what you have now because some settings are dependent on others, but in general, this sounds like what you want:

Screenshot of Room Lighting with "Limit activation under these conditions" set "To only between two times" of sunset and sunrise
Screenshot of Room Lighting with "Limit activation under these conditions" set "To only between two times" of sunset and sunrise740×405 13.5 KB

2 Likes
3

Here’s what I have:

Screenshot (3)
Screenshot (3)1920×1080 270 KB

4

You are using Rule Machine, not Room Lighting. Were you using Room Lighting, as claimed in your original post? While your rule could work, I don’t see the problem you mentioned in your original post here. So knowing exactly what you’re doing (and where you see the message you mentioned) would help narrow down the problem.

5

Thanks for the follow‑up — and yes, you’re correct. I’m currently using Rule Machine. I originally tried setting this up in the Room Lighting app, but I couldn’t get the automation to trigger reliably. Since I’m still new to all of this and learning as I go, I switched over to Rule Machine to see if that would give me more control over the mmWave presence behavior and the vacancy delay.

Here’s what my Rule Machine setup looks like right now:

Required Expression:
– Time between Sunset and Sunrise (TRUE at night)

Trigger:
– BSZ Office presence changed

Actions:
– Set level to 60%
– Wait for Expression: targetCount = 0 (with a 4‑minute timeout)
– Set level to 0%

The issue I mentioned in my original post happens when the presence sensor reports rapid state changes. When that happens, the rule keeps firing, restarts the wait, or cancels the off sequence. That’s the behavior I’m trying to understand and fix.

I appreciate your help and patience while I work through this. Please let me know if you need any other details.

Thanks