Hi, not sure exactly if you refer to this, but in case you've missed it:
Web admin/lmce-admin -> Advanced -> Network -> Firewall rules.

Yep, it is impressive.
It would be so convenient to just speak to LMCE instead of, well, the usual methods.
I'd implement this in some form if I just could. 
/Kooma

This is asked quite often, and the routine answer seems to be: for new installations go with the KNX/EIB, for retrofitting the Z-wave gang. See for example http://forum.linuxmce.org/index.php/topic,12141.0.html and others. For most other systems, please pay attention to the reliability. It just doesn't make any sense to play with stuff that you cannot rely on. Waveman, I have had my share of problems with that. Still in the process of getting rid of the rest modules.

Powering up/down the whole house, sound wild, and requires some high amp relays. So you don't have anything that should be left on all the time?

/Kooma

Oh yeah it looks like it's shooting as fast as it can. I do have the same thing happening, only if there's any timed events occuring between 00:00 and 01:00 a:m... Don't understand what's going on, but found out about the malfunction. Works just perfect besides that.

Had the same issue with Nokia E-series phones.
Use Opera Mobile, it works great.

I know nothing, but, could we integrate the data logger here. I'm thinking that at some point the data logger could log any selected events/data/etc to a database. This database could serve as a more versatile means for each case, like 1-wire data.

DragonK, you've proceeded very well, looking forward using your design.

I also felt the frame being the only downside to your design. Not that it takes up some area but the sharp corners, there's something there. They, somehow, don't go with the round buttons optimally.

Have you tried rounding the corners of the frame? Might not look as  good as it does now, but might be worth testing?

Timed event between 00:00 and 00:59 cause this and one gets out of this crazy loop by reloading the router.
Tried to see the relevant timed event source code but can't spot the error source.

I'm having a bit similar situation here with the Selexit dongle. Everything works perfect, except when using timed events to control lights, sometimes an excessive repetition of the command is broadcasted. It occurs about once every millisecond. Reloading the router gets things back to normal. The system may work several days OK yet sometimes this erroneous function takes place within a day.


The DCE router log shows (this goes on until reloading):

Code:

08      10/27/10 0:30:01.565            Received Message from 12 (Event Plug-in / ) to 503 (Lights (dim) - MH / ), type 1 id 193 Command:Off, retry none, parameters: <0x9f7fab90>
08      10/27/10 0:30:01.565              Parameter 97(PK_Pipe):  <0x9f7fab90>
08      10/27/10 0:30:01.566            Received Message from 12 (Event Plug-in / ) to 503 (Lights (dim) - MH / ), type 1 id 193 Command:Off, retry none, parameters: <0x9f7fab90>
08      10/27/10 0:30:01.566              Parameter 97(PK_Pipe):  <0x9f7fab90>
08      10/27/10 0:30:01.568            Received Message from 12 (Event Plug-in / ) to 503 (Lights (dim) - MH / ), type 1 id 193 Command:Off, retry none, parameters: <0x9f7fab90>

I hope this helps in finding out what is going on.

/Kooma

(davegravy, your wife likes to sleep late?)

Okay, automated lights off function was fantastic for the three days it worked. Slept better, not only because it was dark but also the room temperature did not rise that much cause I wasn't burning the lights all night.

I have few 12 V halogens for the bedroom, connected to a conventional transformer. I suppose this is the reason why the ACT plug in lamp-module just died last night. It was used only for these few days

Has anyone tried to fix those modules? It must be the output stage that died..

Sleepless nights... it turned out that the ACT module is fine. The thing is that something messes up the control of this particular module during the night. I cannot turn it on with a remote (hand-held or an orbiter). Only after reloading the router things get back to normal.

I know that answer to this problem lies in the logs somewhere. DCERouter log is 200 pgs long... so using grep might be in place.

Any ideas what to look for? And at this point, I'm just using events, not any scripts for this.

Thanks for your help!

This might not be the best news (Spotify crashes into Apple on way to U.S.)
http://news.cnet.com/8301-31001_3-20018971-261.html?tag=mncol;1n

purps, could you please contact the manufacturer and let them know what happened?
Just got my first unit this week, that's why a bit curious about what happened and what is the reason..

Okay, does not do good for the reputation of the manufacturer.. Just to make sure, what kind of load you were driving with the dimmer? Was it below the power limit (300W)?

Yes, there is a fuse and I was quite positive that it would had been blown, but it wasn't. Checked that in the night instead of sleeping..

Not a big deal, but still decided to ask the ACT for advice on probable parts to replace. Got this idea since I know that some others have broken plug-in units, too.   

USB is taken care of within the server. Not an expert, but I see no reason why these wouldn't work with the LMCE.

I have one of those servers, could try it with the LMCE next weekend.