For the curious: you do not need any of this to change a bulb.
Back to devices.
At a glance
| Item | What we found |
|---|---|
| Bulbs | Four of the same Zigbee full-colour model, outdoors: a lamppost, a back porch, a front porch and a laundry room porch |
| Colour | Full colour, with a colour temperature from 2202 K to 7042 K |
| Schedule | On at sunset, off at sunrise |
| Months | Deep warm amber most of the year, orange in October, green in December |
| After a power cut | They come back on |
The schedule is one mechanism and three rows
The mechanism takes the months it covers and the colour it uses. The year is split across three rows, and every month appears exactly once per bulb, so exactly one row turns the lamps on at any sunset. A check fails if a month is named twice or left out. A holiday colour is a new row, not new code.
Why a white is not an RGB colour
The default row names a colour temperature, not an RGB value. The warmest amber these bulbs make is a colour temperature, and the bulbs do a better job with it than with an RGB approximation. The other two rows are RGB: a pumpkin orange and a green.
One we tried and took back
We once set one bulb to a bright violet for the month. It was reverted to orange the same evening because it was hard to look at in real use. Splitting out a bulb is a few lines of data, and so is undoing it.
Sun times depend on the house’s settings
A house’s elevation setting had been left at zero on a property well above sea level, so every sun time was 3 to 4 minutes off all year. A question from the owner found it. Nothing in our checks had looked at the house’s own settings; now they do.
Ask your assistant
Change the porch bulbs to green for the holidays.
Your assistant changes a row of data. No release, no restart.