HouseBot

You can create a script device that has properties that you set for the variables you would have passed to the script. The device script is always running and picks up work to do (dim a light, etc) from a device property and then looks at other device properties for other settings (which light, how ...

Not in a big hurry - I've lived without it for this long... I would be happy to be a beta tester. Give me a heads up when it might be time to go purchase some hardware. My first toe in the water is just to be able to use HouseBot to control my landscape lighting transformers based on turning on at S...

I'm thinking about getting started with Insteon - I have no lighting controls now.

Would the PLM product be the best place to start (once there is a driver)?

Yes, I agree.

I disabled the hibernation for the very reasons you mention - just thought I would throw that out in case it was the cause of other user's issues.

I noticed this message appearing when the HouseBot machine was awakening from hibernation. Not sure if this is the only case, but that is the only time I have seen it.

I ran into a situation like you describe with a task taking a while to execute. What I found was that I had a couple of script devices that were always running and sleeping 10 milliseconds during every poll of a property that would tell the scripts that there was something to do. It seems that this ...

I've done the same thing you suggested to be able to point dynamically to different data. Unfortunately, I don't think that gets around the problem of having to change the script if you want to make more than one script device of the same type - you still have to hard code the name of the NULLDevice...

If you could reference the underlying device implicitly from a script, then you could have reusable scripts for script devices. Currently (I think), all property reference from within a script must specifically reference a device/property pair. This forces a script to be associated with single devic...

I would like to see a Ticker control that would allow you to scroll the contents of a device property across the screen. Maybe an AlphaList could be the source property and the control could scroll multiple messages with pause in between. This would be really nice to allow scrolling news headlines a...

Have you seen the Apple TV or MCE interface? I'm doing something similar - it works quite well for a 10 ft interface. I navigate using the arrow and select buttons on my remote which talks to the IR transceiver. A script picks up the code inputs and moves the selection on a series of AlphaLists. The...

I have an interface that doesn't use touch or mouse input. I drive it completely from script that gets its commands via the UIRT. I would like to be able to turn off vertical scroll bars on controls (you can already disable horizontal ones). They don't mean anything in this context and they keep me ...

I mentioned this in another thread...

It would be real nice to have an optional device property that could be associated with each control that would hide/show a control on the SW remote based on the value of that property.

Yes, that will work, but becomes unmanagable if there are very many sets of controls that might be optional. The number of permutations gets too high. This would seem to be a nice enhancement request - an optional device property associated with controls that would indicate whether they were enabled...

I'm not sure that this was the same problem.

I opened the database with Access and could see that there was a task referencing a property that didn't exist. It didn't show up in the HB UI, but it was in the database. Not sure how it happened, but I deleted the task and recreated it and that fixed it.

I have some controls that I would like to have appear / disappear from a panel depending on the state of various devices. Is this possible? Also, it would be real nice to be able to turn of vertical scroll bars on list controls. I'm driving the whole UI from a remote so the scroll bar isn't needed a...