As for the lockups: I’ve identified a variety of causes since 2.0b4. These are fixed in 2.0b5. If the problems persist after that release, let me know and I’ll let you know what I need.

I’ve received other reports about the blinking behavior as well. I’m looking into the issue.

Barring any major catastrophes, 2.0b5 should be available later today.

-Anyway, back to the lock-up: If I kill the program and restart it, it will sometimes work just fine for another day or so. I’ll try to get some logs for you.

-I’m also seeing an issue where (only at certain times) adjusting the brightness of an Insteon Lamplinc using its configuration page causes the brightness to continually bounce around between different levels until I quit the program. Again, this only happens sometimes, so I’ll be checking the logs for some clue as to why.

-The time input field (eg in the scheduled action setup) should either respect the system-wide time format or offer a clicky method of setting the time. I had to find a picture in your blog to see that it was expecting “hh:mm XM” (12 hour only). Ideally, you would just have smarter code validating that field’s input. 19:00, 19.00, 19h00, 7:00 pm, 7:00p, 7pm, etc could all be valid inputs. At the very least, the error dialog should explain what the field was expecting.