CommandFusion: iPhone control with customizable interface

[Fiasco]

Worked on this theme a bit more tongiht.

[derGoNzO]

Hi!

I also tryed this wonderful plugin with EG on my iPod touch. I only can say this is absolute fantastic!! Never seen before such a great app!
So, enough praise for this moment

I want to control my home (all equipped with the ELV FS20 System). So I have the FS20 PCS USB device and the plugin installed in EG.
I already made a gui and the simply on/off function works fine!
So now I also want to dimm the lights by a slider in the gui and here is my problem.

When I looked in your example gui I noticed how you made it with the vol level change but I have no idea how to do this for my own!?
I think I need a python skript is this right?
Can somebody help me or must I learn python first to do this?

Other question, is it possible to give an replay from the device whitch light is still on and/or on which dimm state?

Next problem for me is the page limit, on page for one room would be fine but If this really works for me I┬┤m thinking about to buy a single licence of this great software....

So thanks for any replay and sorry for my bad english

[CommandFusion]

derGoNzO: Does FS20 have an Ethernet protocol? Eg. TCP or UDP? If so, you can directly control it without using EventGhost as a middleman (save you learning Python).
Otherwise, you have to follow what I have done in the plugin example to parse analog slider commands and send that value on to the FS20 system.

I could only find info in German about FS20, so makes it very hard to help you unfortunately.

Yes it is possible to show feedback data from your systems on iViewer. You need to send back the digital state for button states, analog values for sliders/gauges, and serial values for text strings.

[derGoNzO]

No, the device is ja HID device. No Ethernet protocol.
I also tryed it with the analog change slider but I didn┬┤t know how to couple it with the dimm instruction for the FS20 PCS....maybe you could add the plugin into EG (add Plugins ->external Devices -> FS20 PCS)!?
The plugin and the Event-instructions are still in english. So maybe you could give me a hint.....

Otherwise I have to ask in the FS20 PCS forum.

Thanks for your answer!

[CommandFusion]

Create a macro triggered by a CommandFusion AnalogChange event, then create a python script event and add the following:

eg.Plugins.FS20PCS.Dim(0, (float(eg.event.payload)/65535) * 16)

You might need to do some rounding in there, but otherwise should work.

This scales the analog value from the slider to a range of 0-16 (as required by the FS20 dim values). So it won't scale perfectly because you cant set the exact dim percentage.
Got the info from here (page 4):
http://www.elv-downloads.de/Assets/Prod ... 916_UM.pdf

0 is the address, not sure exactly what you should put here, but that was the default address (1111-1111-1111 or something).

I got the command definition by creating an event to set the dim level to 50% then copy the event and paste into a text editor (as documented in the Python Scripting help built into EventGhost help contents). You can manually create an event, enter the correct address and any dim level, then copy/paste the item in the macro to a text editor to see what unit address values you should use.

[derGoNzO]

Thanks, great! I will try this as soon I┬┤m at home this evening!

The Code is a combination from the "House-Code" (the mastercode for the complete home-control in the FS20 system) and the single address from a actuator, for example a dimming module:

1234 5678 - 1111

First eight digits are the House-code, last four the the single address

Report follows....

[derGoNzO]

0 is the address, not sure exactly what you should put here, but that was the default address (1111-1111-1111 or something).

I got the command definition by creating an event to set the dim level to 50% then copy the event and paste into a text editor (as documented in the Python Scripting help built into EventGhost help contents). You can manually create an event, enter the correct address and any dim level, then copy/paste the item in the macro to a text editor to see what unit address values you should use.

Okay, I just noticed that the address is not typed in clear type...

For example the address: 1234 1234 - 1111 is going to: FS20PCS.Dim(1776384, x)

Anyway, with the info from you to copy the event to an editor, I got the right address.

So I have an error now with the python script:

Code: Select all

CommandFusion.AnalogChange_5 '20817'
   Deckenleuchten dimmen
      eg.Plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
         Fehler in Befehl: "eg.Plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)"
         Traceback (most recent call last) (1387):
           File "<string>", line 1, in <module>
           File "D:\EventGhost\eg\__init__.py", line 52, in __getattr__
         AttributeError: 'eg' object has not attribute 'Plugins'

Any idea!?

[Bartman]

it is eg.plugins with a lower p

The address is a 32 Bit integer. The first byte is useless, the next two are the house code and the last is the device address. It is easy to get if you use hexadecimal

11 => 0
12 => 1
13 => 2
14 => 3
21 => 4
22 => 5
23 => 6
24 => 7
31 => 8
32 => 9
33 => A
34 => B
41 => C
42 => D
43 => E
44 => F

so 1234 1234 - 1111 gets x1B1B00

And the dim value has to be an int too

[derGoNzO]

Great, it works!

But a little problem left, the dimming is not "real-time" it takes time.
The analog change value is submitting every event, so this takes time....about 2 events per second:

Code: Select all

   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '49344'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '49729'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '50115'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '50500'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '50886'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)
CommandFusion.AnalogChange_5 '50886'
   Deckenleuchten dimmen
      eg.plugins.FS20PCS.Dim(3101425, (float(eg.event.payload)/65535) * 16)

and so on.
Can I accelerate that?

[Bartman]

The plugin waits for the answer from the device.
It could be rewritten so EG can go on, but the the execution of the next command had to be delayed in background because the device itself can only deal with one command at a time. This would result in some dimming after you stop moving the slider.

Does the slider have 65536 steps? This will probably result in many equal commands to the device resulting in more blocking than necessary.

[derGoNzO]

Yes, exact. The commands are delayed in the background! So when I slide from zero to full, the command works about 1 min.

The slider have 65536 steps, but this can┬┤t changed in the gui designer.

Are there for the dimming command really only the 16 steps?

If so, maybe the python script can be modified, so that the command only goes out if the slider change is in the rage of one of the 16 steps!?
You know what I mean?
But then dimming is more like stepping

[Bartman]

Yes, exact. The commands are delayed in the background! So when I slide from zero to full, the command works about 1 min.

With 16 steps it would be down to a few seconds.

Are there for the dimming command really only the 16 steps?

Jep. Thats all the FS20 system supports. Still a lot better than many other system only support up/down dimming.

[derGoNzO]

Are there for the dimming command really only the 16 steps?

If so, maybe the python script can be modified, so that the command only goes out if the slider change is in the rage of one of the 16 steps!?
You know what I mean?
But then dimming is more like stepping

[Bartman]

For smooth dimming you have to use the timed action. Dim to value xx in yyy seconds.
Even repeating a dim down commands looks really stepped.

edit:
Even the timed actions look like stepping.

[derGoNzO]

hmpf, I thought it would be easier...
So no way to solve this?