Author Topic: [Solved] Input switches  (Read 2296 times)

brononius

  • Guru
  • ****
  • Posts: 424
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: Input switches
« Reply #15 on: January 01, 2012, 02:40:59 pm »
I've just created a GA in ETS, and added the button in it. Nothing more.
A bit similar like i did for my standalone groups (=the groups who work without the server involvement).

For the eibd.log, this is generate once i push the button.
So its data coming from the button towards the server...

When i add now a light into this 'ETS' group, it lights up once i push the button.
So the configuration is working without a server involvement.


I was thinking that there isn't data coming in from the EIB bus. But since i can read the status of the lights, i suppose this is fine?
When a light is flipped on, DCErouter.log starts generating some log files as well.


ps what do you mean with the GA definition? Are their special settings for the groups to take care off?
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE

brononius

  • Guru
  • ****
  • Posts: 424
  • Trying to keep it simple and centralized...
    • View Profile
    • OnIrIa - linuxMCE blog
Re: Input switches
« Reply #16 on: August 13, 2012, 08:35:31 pm »
With linuxMCE 1004 and the default eibd template, the input buttons works.
Just select the doorbell template, and i'm on my way...
Version: linuxMCE 1404, running virtual on ESXi

Orbiters: ASUS eeePAD, Nexus 5, Huwai, web
Automation: EIB technology, KNX IP ROUTER 750
Phones: Cisco 7912-7940-7960
Camera's: Foscam POE