Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - mhorst

Pages: 1 [2] 3 4 5
16
Users / Re: more than one Internet Radio Streams behind a "group button" ??
« on: December 23, 2011, 03:30:00 pm »
Thanks, it helped. I now have a working set of internet radio stations :)

One issue: sometimes after I modify the playlist and try to play it, it doesn't work and the DCERouter log shows "Play playlist  in entertain area  but nothing to handle it". I'm not sure what causes it.
At first I thought some of the URLs I added were faulty, but when I reduced the list back to a set of URLs that I had tested before, it still did not work.
As a test I put a real mp3 file at the top of the playlist (containing 1 second of silence), and since then it hasn't occurred, but I haven't done much editing since that either.

By the way, I found a way to give those entries the name I want, instead of the filename.
On the DCERouter, I added Redirect entries to the file /var/www/.htaccess, i.e. I added a line:
Code: [Select]
Redirect /Radio2 http://shoutcast.omroep.nl:8102This way playing http://192.168.80.1/Radio2 redirects to the actual URL, and I get the entry "Radio2" in my playlist, instead of "shoutcast.omroep.nl:8102".

17
Users / Re: Help choosing thermostat tech
« on: December 18, 2011, 09:58:05 pm »
I think the Z-wave solution is the easiest, but in case you want another (wired) option: http://wiki.linuxmce.org/index.php/Proliphix_NT_series_thermostat

18
Users / Re: more than one Internet Radio Streams behind a "group button" ??
« on: December 18, 2011, 09:51:30 pm »
Bump.

Anybody got this working on 0810? The method on the wiki works fine. But I am unable to create a playlist with a list of internet radio stations. As soon as the file is not found (i.e. I change the meta-data from an actual file to an URL), the playlist refuses to start.

19
Users / Re: Temperature display in orbiter?
« on: November 20, 2011, 08:03:54 pm »
I have a thermostat connected to my system (Proliphix, not Insteon though).
The current temperature is already visible in my weborbiter on next to the thermostat icon the floorplan.

Or do you want it at some other place in the web orbiter?

20
Installation issues / Re: LG LCD Template
« on: September 11, 2011, 04:45:32 pm »
It's been a while, but I finally found the reason why my volume commands sometimes work and sometimes not;
If the TV is already on while the MD starts, the volume works. If the TV is off while the MD starts the volume commands do not work (but everything else does).

I checked the ruby code in the template. During intialization, in the InitVolume function, it does something clever. It tries to retrieve the current volume from the TV, even turning the TV on and off again if necessary.
My guess is that my TV (an 26LV5500) doesn't like that, gets into some strange internal state, and no longer responds to volume commands after it has been quickly turned on and off again.

I placed the line "@volume = 10" at the start of the InitVolume function. That way the function assumes the volume has been retrieved successfully, and doesn't send any commands to the TV. This works, but I'll see if I can find out which part of the InitVolume function is actually causing the problem.

For now it looks like a problem with my TV's software, not with the template.

21
Installation issues / Re: LG LCD Template
« on: June 19, 2011, 04:06:01 pm »
You're welcome.

I'm still playing around a bit. Although the On/Off command is not visible in the webadmin when I select "Send a command to device", after running the setup wizard on the MD, my orbiter is capable of turning the TV on and off.
I can then also use the volume commands to control my TV. So that works nicely.

I'm still having a bit of trouble to get the thing working right after a reboot though. Last time the On/Off command worked, but the volume commands didn't. I think that means the com port is now OK after a reboot.
I played a bit with minicom and noticed the volume commands got an error; turned out that the TV thought it was muted and then volume commands give an error. After unmuting it via minicom and resetting the device it started working again.
Maybe I should add an unmute command to the template before a volume change. I'm not sure how the TV got muted (or if it really was; forgot tot test), but there is only one bit difference between the command to turn the TV on and to mute it. So maybe it's just my connection.

22
Installation issues / Re: LG LCD Template
« on: June 16, 2011, 10:01:09 pm »
I added it manually by selecting advanced -> configuration -> devices.
Selecting my MD.
Then create  child device.
Pick the 2126 template.

I then filled in the "COM port on PC" data, it has a drop down box and in my case it only has one value.

Seems to work, though it looks like not all volume change commands are processed or some are processed double.
Also, I cannot seem to find the On and Off commands.

I had some problems in getting my USB to serial port adapter working. When rebooting it doesn't work.
I then use minicom to talk to my TV, once that works I quit minicom and restart the router.
The device then does works (with the caveats described above).
So I need to figure out a way to put the com port settings that are done by minicom in some config file somewhere.
Anyway, that's a problem with my hardware, not with the TV template.

23
Users / Re: ZOTAC ZBOX HD-ID11-U
« on: June 12, 2011, 01:34:46 pm »
Got mine working, thought I'd share.

The instructions from jondecker76 work to get the network card up and running. Though the steps have to be modified to take the new the kernel version number into account.

Getting the HDMI sound working was a bit more problematic.
I updated the ALSA drivers to 1.0.23 as shown in http://monespaceperso.org/blog-en/2010/04/17/upgrade-alsa-1-0-23-on-ubuntu-karmic-koala-9-10/ (It says its for 9.10, but it also works on 8.10)

Then I added a sound.conf file in /etc/modprobe.d with "options snd-hda-intel enable_msi=0 probe_mask=0xffff,0xfff2" in it.
In /etc/asound.conf I added:
Code: [Select]
pcm.!default {
  type hw
  card NVidia
  device 3
}
ctl.!default {
  type hw
  card NVidia
}
Unfortunately /usr/pluto/bin/SetupAudioVideo.sh keeps undoing my changes to asound.conf, so I edited that file and commented out any lines containing asound.conf. (Not a nice work-around, I know, I'll see if I can make a cleaner fix.)

After that alsamixer showed the HDMI output as the only default output. I unmuted it and ran "alsactl store" to save the mixer settings.

HDMI sound is now working, and is the default output, so I didn't need to change any other settings (in mythtv for example).

@nite_man: It does have a fan. It hasn't bothered me so far, but I'll see what happens once I get the unit installed in a less noisier environment (i.e. my bedroom).
@sigg3.net: I'm using 2Gb of RAM. No problems so far, but I haven't done extensive testing yet.

24
Users / Re: Door bell question
« on: April 17, 2011, 07:14:24 pm »
Hello,

If you mean the 05443, then no. It seems that this device does not send an event when it is pressed.
(See also http://forum.linuxmce.org/index.php?topic=11581.0.)


25
Users / Re: Duwi 05443 z-wave wall mounted transmitter problems
« on: April 03, 2011, 01:53:07 pm »
Ah, a missing c_str(). Thanks, that helped.

I did some research, the fact that I don't get events from the module seems to be a problem with the module itself.
Other home automation systems seem to have the same problem (http://www.domoticaforum.eu/viewtopic.php?f=26&t=4757&start=0&hilit=wandzender+event (in dutch)).
The work-around is to associate the module with another device and then use events from that device.

I don't like that work-around since it would mean my LinuxMCE house mode is directly linked to the status of one of my devices.
I.e. some device would have to be either always on or always off when I'm at home. Or I would have to get a separate z-wave module that is not connected to any real device and use that, but that seems like a waste of money.

BTW I updated the wiki page http://wiki.linuxmce.org/index.php/Düwi_Popp_ZW_WS_05443 with the English manual for this module.
I havent added the problem with the events to the page yet, since Valent added there that the module works without caveats. I PM-ed him, hoping he can tell me if he has the event problem too, or found a way around it.

26
Users / Duwi 05443 z-wave wall mounted transmitter problems
« on: March 30, 2011, 10:22:47 pm »
I'm slowly expanding my z-wave home automation. I bought a wall-mounted transmitter with the intention of placing it next to my front door and using it to  change my house mode when leaving/entering the house.

I managed to include it with my Aeon labs usb stick (press the button on the stick and then press and hold the include button on the transmitter for 2seconds). After that I inserted the usb stick back into my core and did a quick reload of the router.

Unfortunately the ZWave device then crashed:

Code: [Select]
========== NEW LOG SECTION ==========
1 03/30/11 20:03:08 80 (spawning-device) Starting... 50
1 03/30/11 20:03:08 80 (spawning-device) Found /usr/pluto/bin/ZWave
01 03/30/11 20:03:08.755 TranslateSerialUSB pci0000:00/0000:00:0b.0+1 result /dev/ttyUSB0 <0xb71806c0>
36 03/30/11 20:03:08.756 Initialization... <0xb71806c0>
36 03/30/11 20:03:08.756 Open serial port /dev/ttyUSB0 <0xb71806c0>
36 03/30/11 20:03:08.778 Get version <0xb71806c0>
36 03/30/11 20:03:08.778 Get home/node id <0xb71806c0>
36 03/30/11 20:03:08.778 Get capabilities <0xb71806c0>
36 03/30/11 20:03:08.778 Get SUC node id <0xb71806c0>
36 03/30/11 20:03:08.778 Get init data <0xb71806c0>
05 03/30/11 20:03:08.780 Creating child 81 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 82 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 83 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
05 03/30/11 20:03:08.781 Creating child 89 <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb71806c0>
05 03/30/11 20:03:08.781 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb71806c0>
36 03/30/11 20:03:08.778 receiveFunction started <0xb717fb90>
40 03/30/11 20:03:08.891 Sending job 0x88c4d20 (cb 0) - 0x1 0x3 0x0 0x15 0xe9 (#####) <0xb717fb90>
41 03/30/11 20:03:08.896 0x1 0x10 0x1 0x15 0x5a 0x2d 0x57 0x61 0x76 0x65 0x20 0x32 0x2e 0x37 0x38 0x0 0x1 0x9b (####Z-Wave 2.78###) <0xb717fb90>
36 03/30/11 20:03:08.896 Got reply to ZW_VERSION: <0xb717fb90>
01 03/30/11 20:03:08.896 ZWave Version: 2.78 <0xb717fb90>
40 03/30/11 20:03:08.999 Sending job 0x88c53f0 (cb 0) - 0x1 0x3 0x0 0x20 0xdc (### #) <0xb717fb90>
41 03/30/11 20:03:09.004 0x1 0x8 0x1 0x20 0x11 0x11 0x11 0x5d 0x1 0x9b (### ###]##) <0xb717fb90>
36 03/30/11 20:03:09.004 Got reply to ZW_MEMORY_GET_ID: <0xb717fb90>
01 03/30/11 20:03:09.004 Home id: 0x1111115d, our node id: 1 <0xb717fb90>
40 03/30/11 20:03:09.107 Sending job 0x88c5610 (cb 0) - 0x1 0x3 0x0 0x7 0xfb (#####) <0xb717fb90>
41 03/30/11 20:03:09.116 0x1 0x2b 0x1 0x7 0x3 0x7 0x0 0x0 0x0 0x1 0x0 0x1 0xfe 0x80 0xfe 0x88 0xf 0x0 0x0 0x0 0xfb 0x97 0x7f 0x82 0x7 0x0 0x0 0x80 0x0 0x80 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x47 (#+##########################################G) <0xb717fb90>
36 03/30/11 20:03:09.116 Got reply to FUNC_ID_SERIAL_API_GET_CAPABILITIES: <0xb717fb90>
01 03/30/11 20:03:09.116 SerAppV:3,r7,Manf 0,Typ 1,Prod 1 <0xb717fb90>
40 03/30/11 20:03:09.219 Sending job 0x88c5830 (cb 0) - 0x1 0x3 0x0 0x56 0xaa (###V#) <0xb717fb90>
41 03/30/11 20:03:09.226 0x1 0x4 0x1 0x56 0x1 0xad (###V##) <0xb717fb90>
05 03/30/11 20:03:09.227 Got reply to GET_SUC_NODE_ID, node: 1 <0xb717fb90>
40 03/30/11 20:03:09.327 Sending job 0x88c5a50 (cb 0) - 0x1 0x3 0x0 0x2 0xfe (#####) <0xb717fb90>
41 03/30/11 20:03:09.379 0x1 0x25 0x1 0x2 0x5 0x8 0x1d 0x81 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x3 0x1 0x4b (#%#K) <0xb717fb90>
36 03/30/11 20:03:09.380 Got reply to FUNC_ID_SERIAL_API_GET_INIT_DATA: <0xb717fb90>
40 03/30/11 20:03:09.483 Sending job 0x88f1198 (cb 0) - 0x1 0x4 0x0 0x41 0x1 0xbb (###A##) <0xb717fb90>
41 03/30/11 20:03:09.488 0x1 0x9 0x1 0x41 0x92 0x16 0x0 0x2 0x2 0x1 0x33 (###A######3) <0xb717fb90>
36 03/30/11 20:03:09.488 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.488 ***FOUND NODE: 1 <0xb717fb90>
36 03/30/11 20:03:09.488 listening node <0xb717fb90>
36 03/30/11 20:03:09.488 BASIC TYPE: Static Controller <0xb717fb90>
36 03/30/11 20:03:09.489 GENERIC TYPE: Static Controller <0xb717fb90>
36 03/30/11 20:03:09.489 SPECIFIC TYPE: 0x1 <0xb717fb90>
36 03/30/11 20:03:09.492 No device capabilities for node: 1 <0xb717fb90>
36 03/30/11 20:03:09.492 Requesting node info from node 1 <0xb717fb90>
40 03/30/11 20:03:09.591 Sending job 0x88f13b8 (cb 0) - 0x1 0x4 0x0 0x41 0x8 0xb2 (###A##) <0xb717fb90>
41 03/30/11 20:03:09.595 0x1 0x9 0x1 0x41 0xd2 0x9c 0x0 0x4 0x11 0x3 0xee (###A#######) <0xb717fb90>
36 03/30/11 20:03:09.596 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.596 ***FOUND NODE: 8 <0xb717fb90>
36 03/30/11 20:03:09.596 listening node <0xb717fb90>
36 03/30/11 20:03:09.596 optional functionality <0xb717fb90>
36 03/30/11 20:03:09.596 BASIC TYPE: Routing Slave <0xb717fb90>
36 03/30/11 20:03:09.597 GENERIC TYPE: Multilevel Switch <0xb717fb90>
36 03/30/11 20:03:09.597 SPECIFIC TYPE: 0x3 <0xb717fb90>
36 03/30/11 20:03:09.600 Device capabilities: 114,134,130,135,117,112,133,39,37,38 <0xb717fb90>
40 03/30/11 20:03:09.700 Sending job 0x88f15d8 (cb 0) - 0x1 0x4 0x0 0x41 0x11 0xab (###A##) <0xb717fb90>
41 03/30/11 20:03:09.703 0x1 0x9 0x1 0x41 0x12 0x96 0x0 0x1 0x1 0x1 0x33 (###A######3) <0xb717fb90>
36 03/30/11 20:03:09.704 Got reply to FUNC_ID_ZW_GET_NODE_PROTOCOL_INFO: <0xb717fb90>
36 03/30/11 20:03:09.704 ***FOUND NODE: 17 <0xb717fb90>
36 03/30/11 20:03:09.704 sleeping node <0xb717fb90>
36 03/30/11 20:03:09.704 optional functionality <0xb717fb90>
36 03/30/11 20:03:09.704 BASIC TYPE: Controller <0xb717fb90>
36 03/30/11 20:03:09.705 GENERIC TYPE: Generic Controller <0xb717fb90>
36 03/30/11 20:03:09.705 SPECIFIC TYPE: 0x1 <0xb717fb90>
05 03/30/11 20:03:09.705 ZWave::InternalIDToDevice() No device found for id 17 <0xb717fb90>
Return code: 132
3 03/30/11 20:03:09 80 (spawning-device) Device died... count=50/50 dev=80
Wed Mar 30 20:03:09 CEST 2011 died
3 03/30/11 20:03:19 80 (spawning-device) Aborting restart of device 80...

I have no idea why the crash occurs. If a node id is not found the InternalIDToDevice function returns NULL, but as far as I can see all the clients of the function handle that case.

Anyway, after some fiddling around I got the idea to manually add a child device to my zwave device with the correct node id.
This helped, the zwave device is now starting again. The template I used is "ZWave Controller".

Now I'm still trying to figure out how to make LinuxMCE respond when I press the switch. So far no events are generated and since the switch has the z-wave capabilities 114 (manufacturer specific), 128 (battery) and 133 (association) that doesn't really suprise me.
I could associate the switch with another device and then respond to the status changed events from that device, but that seems pretty inelegant.

27
Users / Re: Düwi 05436 z-wave blinds controller recognized as dimmer?
« on: February 05, 2011, 11:18:06 pm »
Thanks, I'll give it a try once the package is updated.

EDIT: I tried it out, it works! Thanks.

28
Users / Re: Düwi 05436 z-wave blinds controller recognized as dimmer?
« on: February 03, 2011, 07:31:54 pm »
Ok, here's the log:

Code: [Select]
========== NEW LOG SECTION ==========
1 02/02/11 21:17:39 80 (spawning-device) Starting... 1
1 02/02/11 21:17:39 80 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/02/11 21:17:47.955 Creating child 81 <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb72456c0>
05 02/02/11 21:17:47.956 Creating child 82 <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb72456c0>
05 02/02/11 21:17:47.956 Creating child 83 <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1945 that this has no custom event handler for.  It will not fire events. <0xb72456c0>
05 02/02/11 21:17:47.956 Note: Device manager has attached a device of type 1945 that this has no custom handler for.  This is normal for IR. <0xb72456c0>
05 02/02/11 21:17:47.961 Creating child 89 <0xb72456c0>
05 02/02/11 21:17:47.961 Note: Device manager has attached a device of type 38 that this has no custom event handler for.  It will not fire events. <0xb72456c0>
05 02/02/11 21:17:47.961 Note: Device manager has attached a device of type 38 that this has no custom handler for.  This is normal for IR. <0xb72456c0>
05 02/02/11 21:17:48.107 Got reply to ZW_MEMORY_GET_ID, Home id: 0x1111115d, our node id: 1 <0xb7244b90>
05 02/02/11 21:17:48.343 Got reply to GET_SUC_NODE_ID, node: 1 <0xb7244b90>
05 02/02/11 21:17:48.705 Finished building node list: <0xb7244b90>
05 02/02/11 21:17:48.705 Node: 1 basic: 0x2 generic: 0x2 specific: 0x1 pluto: 1945 <0xb7244b90>
05 02/02/11 21:17:48.705 Node: 8 basic: 0x4 generic: 0x11 specific: 0x3 pluto: 38 <0xb7244b90>
05 02/02/11 22:37:59.623 No callback received: await_callback: 218 timer: 31 <0xb7244b90>
05 02/03/11 3:06:19.598 ERROR: callback id is invalid! <0xb7244b90>
05 02/03/11 7:54:23.004 Going to rotate logs... <0xb6242b90>
05 02/03/11 8:21:12.572 Going to rotate logs... <0xb6242b90>
05 02/03/11 8:37:12.907 Error: ZW_SEND failed, removing job after three tries <0xb7244b90>
05 02/03/11 17:47:12.059 Error: ZW_SEND failed, removing job after three tries <0xb7244b90>

Ok, device 89 is my blind control device. My guess is that it is the Node 8 mentioned in the log.
I looked it up, basic 0x4 means "Routing Slave", generic 0x11 "Multilevel switch", and specifix 0x3 means "Multiposition motor". That sounds allright, so I guess the Düwi module is presenting itself correctly.
Somehow LinuxMCE connects template #38: "Light switch (Dimmable)" to this presentation.

I did some more experimenting. It turns out that my first assessment of how setting the dimming level affects the motor is incorrect. Yesterday I tried it by changing the level in steps of 25%. Today I tried it by steps of 1% and it turned out that the motor actually only moves a short distance then.

It turns out that the controller can be calibrated for the time it takes to lower or raise the blind. I didn't do that yet, since the whole setup is on my kitchen table, and the factory default is two minutes. So 1% dimming level change corresponds to a movement of 1.2 seconds, and a 25% level corresponds to a 30 second movement.

Ah well, a case of RTFM I guess. (In my defense the one I got with the module was in German, it became a lot clearer once I downloaded the English version :) )

Setting a new dimming level while the motor is moving immediately takes effect, reversing the direction if necessary. I don't know why I didn't notice that yesterday.
Only the 0% dimming level seems to have a special meaning (keep going down for 2 minutes regardless of the current setting).
Oh and the 99% and 100% dimming level seem to be the same (maybe some kind of round-off thing).

The manual also specifies how I can change the behavior of the module such that a press on the up or down button results in immediate movement in that direction regardless of whether the blind was already moving or not. I haven't tried that since I can now perfectly control the blinds using the "Set Level" command to open or close them, and I like the current behavior for my physical buttons.

That LinuxMCE detects the module as a dimmable light switch is therefore only a cosmetic issue in the webadmin, since I can give it the "Blinds" icon on the floorplan, and it behaves as expected when the dimming level is set.

29
Users / Re: Düwi 05436 z-wave blinds controller recognized as dimmer?
« on: February 03, 2011, 02:23:17 pm »
Ok, I'll post my log when I get home tonight.

By the way, let me know if I can do some useful experiments. The whole setup currently contains only one z-wave module.
So I don't mind resetting the zwave stuff, it's not like I'll ruin a careful setup containing many modules and scenarios :)

30
Users / Düwi 05436 z-wave blinds controller recognized as dimmer?
« on: February 02, 2011, 10:26:41 pm »
I just got my first piece of Z-wave home automation; an Aeon Labs USB stick and a Düwi blinds controller.
Getting things working was a breeze: press the button on the usb stick, press first the top button on the Düwi three times and then the bottom three times, insert the USB stick in my DCERouter, and everything is configured automatically.  ;D

Only one thing bothers me a bit: the blinds controller was recognized as a dimmer. No big deal; it still works, the On command corresponds to pressing the Up button on the module and the Off command corresponds to pressing the Down button.
Similarly setting a dimming level higher than the current level corresponds to the Up button and a lower dimming level corresponds to the Down button.
The Up and Down buttons on the module raise and lower the blinds respectively for 2 minutes, or until the end stop of the blinds has been reached, or until the button for the opposite direction is pressed.

So I can control it, it just looks a bit weird to setting a dimming level in my Orbiter, since that dimming level does not correspond to the level of the blinds at all.
Also, I cannot send it an Open or Close command, I have to send it On or Off and the effect of those commands depends on whether the blinds are already moving when the command is received. So to be sure to open or close it I have to send it the same command twice.

So, no big deal, but I was wondering what is going on.

Maybe the Düwi blinds module cannot be distinguished from a Düwi dimmer?
The wiki suggest that both the dimmer and blinds module are the same (http://wiki.linuxmce.org/index.php/D%C3%BCwi_ZW_ESJ_05436)
But the Düwi website has two distinct product numbers for the dimmer (05433) and blinds (05436) module.
Then again, the capabilities field in the webadmin shows "114,134,130,135,117,112,133,39,37,38" for my blinds module, and I found that 38 and 39 means that it is a binary & multi-level switch so I can see why LinuxMCE handles it as a dimmer.

Also, does LinuxMCE even have a device template for a blinds controller? So far I wasn't able to find it.
Or is there some way to fake it such that I can make "Open" and "Close" commands appear in the Orbiter? I guess I could make a scenario to do that, but then I wouldn't be able to put it on the floorplan.

Anyways, I don't think its a big deal. I'm just curious :)

Pages: 1 [2] 3 4 5