LinuxMCE - User contributions [en]

Open Zwave

2013-10-14T21:53:14Z

Kezza:

[[Category: Automation]]
[[Category: RF Control]]
[[Category: ZWave]]
[[Category: Programmer's Guide]]
[[Category: Documentation]]

== Overview ==
The support from LinuxMCE system is represented by an executable '''ZWave''' (it's placed in /usr/pluto/bin) which is the device implementation and a '''DeviceTemplate (1754)''' which is used to create LinuxMCE Devices for ZWave.
There are high speed (4x 40kbps) and standard speed Z-Wave devices.

As of LinuxMCE 1204 the driver will be based on [http://code.google.com/p/open-zwave/ Open-Zwave]

This page is intended as a placeholder for notes and documentation on how to setup and configure the Z-Wave network with Open-Zwave.

For information about what hardware to get look at [[Z-Wave Getting Started]], or check out the [[:Category:ZWave|Z-Wave Wiki Category]].

== Configuring and setting up ==
For configuration and settings we will use the ZWave master control device to send specific commands to the ZWave devices you want to change.
To do that we will first need to open to the '''Send command to device''' popup-screen:

* Go to '''Advanced -> Configuration -> Devices''' this shows the device tree on the left
* Click the top level '''Zwave''' device with "Device Template #: 1754"'''
* Click '''Send command to device''' button for the popup-screen to appear

From the drop-down menu, different commands can be chosen for different actions:
* Adding a new device to the zwave network:
** Select '''Add Node'''
* Stop adding a new device:
** Select '''Add Node'''
** Set '''48 Value (int)''' to 5
* Remove a Device
** Select '''Remove Node'''
** Set '''48 Value (int)''' to -<node_you_want_to_remove> e.g. '''-7''' to remove node 7

== How to install and use ZWave ==

== Setting associations ==

== Tweak advanced ZWave settings ==

== Update node information ==
You can request a manual update of the node information (command classes). To do this open the advanced page of the main ZWave device and send command to device. Send a "Resync node" command with the node id of the node you want to update the information from.

It should normally not be necessary to do this, as the node information is updated at the first reload after it was added. However, it can be useful if for some reason the node information was not correctly set or if you have replaced a node which may have other command classes.

== Implementation ==

QOrbiter

2011-12-16T21:40:24Z

Kezza:

{{versioninfo}}
[[category:QML]]
[[category:QOrbiter]]
qOrbiter is a new LinuxMCE orbiter designed to run on a multitude of devices as well as provide flexible skinning options to make it truly one's own. The purpose of this document now is for documentation of the app moving forward, followed by it being a reference for creating ones own skin

=Concept=
The concept of this document is to provide those wishing to create new skins the needed access to LinuxMCE data through properties and context objects. While I will not be discussing what they are here, they are discussed in the scope of QML documentation which is a pre-requisite to skinning and working with Qorbiter.

So, for example lets take the context property "deviceid". This property is added to the QML engine at runtime so that it can be used to provide the current device id of the orbiter. So in effect, this is a macro or keyword if you will that enables access to the underlying LinuxMCE data. As is one of the goals, no programming is required. One of the goals of this document is to outline all of these properties for easy reference in making a new skin.

=Context Properties=

The format is PropertyName: the type of data it provides.
==General==
*'''srouterip''' : string of the router ip. Default is "dcerouter"

*'''deviceid''' : string representation of device number
*'''style''' : reference the the current style that is set

==User==
*'''currentUser''': the current orbiter user - Initially set from the configuration file 'config.xml' but changes as the user is changed.
*'''userList''': listmodel of all users. Can be dropped into a component to use to select rooms. There is also a component: UserListComponent.qml
This component is totally skinnable and at its core contains a listmodel of all the users. In addition, it sets the current user whenever clicked.

==Location==
*'''currentroom''': the current room / ea
*'''roomList''': list of ea's rooms
*'''component''': RoomSelector.qml
Selects and set the current room and changes listmodels accordingly

=Home Screen=
This specific section covers the home screen. It is unique in that it contains most of the ui elements used to access the rest of the home automation system. for that reason, the concept has not been abandoned and instead made more dynamic. This section will attempt to explain the underlying models and functions for UI designers.

==List Models==
These are prepared in c++ and provided to the QML. If you are creating a skin, you will use these variables to call certain arrays
of objects like scenarios, or userlists. This makes it easier for the designer, as they information will be populated and they only need to fill in the variable.

===currentRoomLights===
This provides by room scenario list for lights. you will need to use your own delegate. a default is provided. 

'''Populated Data Roles''' - Please note: These names are subject to change to fall in line with their specific component names 
*names[NameRole] = "username";
*names[LabelRole] = "label";
*names[ParamRole] = "params";
*names[CommandRole] = "command";
*names[GotoRole] = "gotoscreen";
*names[ImageRole] = "image";

===currentRoomMedia===
This provides by room scenario list for media. you will need to use your own delegate 
'''Populated Data Roles''' - Please note: These names are subject to change to fall in line with their specific component names 
*names[NameRole] = "username";
*names[LabelRole] = "label";
*names[ParamRole] = "params";
*names[CommandRole] = "command";
*names[GotoRole] = "gotoscreen";
*names[ImageRole] = "image";

===currentRoomClimate===
provides by room scenario list for climate. you will need to use your own delegate

===currentRoomTelecom===
provides by room scenario list for telecom. you will need to use your own delegate

===currentRoomSecurity===
provides by room scenario list for security. you will need to use your own delegate

=Data Grids=
Datagrids will encompass these specific views and more to come. Currently, they are very basic and dont accept any styling but this will change over time.

*File List
*Device Arrays
*Lists

==Media Grids==
*'''gmediatype''' : current grid mediatype (to show context based images or who knows )
*'''fileformatmodel''' : fileformat listmodel connected to grid filtering mechanism
*'''mediatypefilter''' : mediatype list model connected to grid filtering mechanims

=Colors & Styling=
Colors such as background and button colors should be set in the style file of the qml skin. See 'Style.qml' for reference on setting up property aliases.

Examples include:

property color stageBG: "slategray"

Qualified color references include:
*SVG named colors [http://www.december.com/html/spec/colorsvg.html Reference]
*Web color notation #112233

==Skins==
skinsList: listmodel of skins found for the build
One should always check the official doc's to see what methods are supported for setting properties.

To start making your own, you have to create at least 2 files inside a new sub-directory of the QML-directory.
The below steps are the minimum steps that have to be taken to get started on your own skin.
#in Qt Creator, in the source-tree, right-click on 'QML'
#In the contextmenu select add new
#choose the template 'QML' -> QML File
#name it 'main'
#for Path, click on choose, in the new window select 'new folder' give it the name of your new skin (in lower case letters, otherwise it wont work!) and click on 'choose'
#click continue and then done
#in Qt Creator, in the source-tree, right-click on 'QML'
#In the contextmenu select add new
#choose the template 'QML' -> QML File
#name it 'Style'
#for Path, click on choose, in the new window select the folder you created in step 5.
#click continue and then done
#in sources -> qorbitermanager.cpp find tskinModel->addSkin and add a new entry for your skin using the directory name.
You can now fill main and style files with the content of the same files found in the QML/desktop/default directory.
Or another pair of main.qml and Style.qml set.
After this is done you can alter the Style.qml to you likings and your skin can be selected from the styles-menu inside qOrbiter

==Images==
Images can be loaded in multiple ways and will be discussed here in the future. All that is required is to use the indicated format for local vs remote loading of images
*Local: '''source: "../../../img/icons/kmix.png"'''
*Datagrid: '''source:"image://datagridimg/"+id'''
*File Details Screen Shot or Album cover: '''source: "image://filedetailsprovider/"+filedetailsclass.screenshot'''
Please note more will become available as they are connected to QML.

Rain8

2011-12-11T07:38:46Z

Kezza:

{{versioninfo|1004Status=Working|1004UpdatedDate=11 December 2011|1004UpdatedBy=[[User:Kezza|Kezza]]}}

[[Category: Hardware]]
[[Category: Automation]]
[[File:Rain8.gif]]

* [http://www.wgldesigns.com/rain8pc.html Rain8 product page]
''Rain8net - Computer Sprinkler Controller for 8 to over 2000 valves. The Rain8net is a modular 8-zone sprinkler controller module that can be controlled over the Internet by any computer or other control device. It is capable of driving standard 24VAC irrigation valves directly.''

=To setup=

[[File:Rain8_WebAdminScreenshot.png|right|500px]]
1. From Irrigation Devices, add Rain8 device '''(template ID 2183)'''

2. Add a Standard Irrigation Sprinkler device '''(template ID 1780)''' for each valve/zone

3. You should now be able to test commands from the device screen and add to scenarios to control from orbiters

Rain8

2011-12-11T07:33:21Z

Kezza: Created page with "{{versioninfo|1004Status=Working|1004UpdatedDate=11 December 2011|1004UpdatedBy=Kezza}} Category: Hardware Category: Automation File:Rain8.gif =To se..."

{{versioninfo|1004Status=Working|1004UpdatedDate=11 December 2011|1004UpdatedBy=[[User:Kezza|Kezza]]}}

[[Category: Hardware]]
[[Category: Automation]]
[[File:Rain8.gif]]

=To setup=

[[File:Rain8_WebAdminScreenshot.png|right|500px]]
1. From Irrigation Devices, add Rain8 device '''(template ID 2183)'''

2. Add a Standard Irrigation Sprinkler device '''(template ID 1780)''' for each valve/zone

3. You should now be able to test commands from the device screen and add to scenarios to control from orbiters

* [http://www.wgldesigns.com/rain8pc.html Rain8 product page]

File:Rain8 WebAdminScreenshot.png

2011-12-11T07:23:55Z

Kezza:

2010-09-15T23:47:59Z

Kezza: Removing all content from page

Talk:Insteon PLM Ruby Code 355

2010-09-15T03:43:52Z

Kezza: Removing all content from page

2010-05-04T10:01:17Z

Kezza:

{{versioninfo}}
[[Category: Video]]
[[Category: TV Cards]]

The KWorld KW-DVB-T 399U is a dual tuner DVB-T usb stick.

== 0710 ==

With an updated V4L DVB library it works very nicely in LinuxMCE-0710. The URL below points to a tar file that contains several libs (its pretty big at 58mb ;-) ). **I would not suggest installing any of the other debs included in this tar as they could seriously damage your normal LinuxMCE installation**

[http://dianemo.com/updates/0008_VDR+V4L.tar]

Download it and then extract it to a directory and look in the sub-directory called V4l2 for the lib called 'v4l2-modules-2.6.22-14-generic_0+20090324-2_i386.deb' and install it on your system from the kde desktop or using apt-get.

This may seem obvious (from looking at the filename), but this deb will only install on the 32 bit version (i386) of LMCE.

Once installed please reboot your Core and attach the KW-DVB-T 399U to a usb port...it will be autodetected. Now attach an aerial feed and your done.

== 0810 Beta2 ==

As with 0710, we need to update the V4L libraries and also the firmware for this tuner. Andrew from [http://www.dianemo.co.uk/ Convergent Home Technologies] very kindly pointed me in the right direction with the following message...

''"The attached Deb's are built using DKMS (which you will probably have to install on 0710/0810 machines) to enable these Deb's to build themselves for any Kernel using DKMS. These Deb's purely install updated V4L modules and firmware enabling the 399U DVB-T and 2104 DVB-S tuners to be detected and configured automatically (amongst others) - they do not install anything to do with vdr/MythTV at all.''
''Install the v4l2-firmware_0+hg20090324-1_all.deb first - if you get no errors then install the v4l2-modules-source_0+hg20090324-1_all.deb. If you do get some errors with the Firmware Deb then just install the Modules Deb.''
''Either way after installing the Deb's attach your tuner and reboot...and your done :-)"''

'''DROP ME A LINE IF YOU WANT THESE ATTACHMENTS, AND I WILL FORWARD THEM TO YOU - axemanmajor -AT- hotmail.com'''

(***If you'd like a copy of the v4l2-modules-source_0+hgnnnnnnn_all.deb package then please PM me on the LinuxMCE Forum and I will make the latest debs available to you - Andrew @ Convergent Home Technologies***)

In my experience, the v4l2-firmware deb did not install, as it conflicted with "linux-firmware". If this happens to you, don't worry, just carry on with the installation the v4l2-modules deb.

Andrew's message indicates that this shouldn't cause you any problems, but in my case the tuners were not recognised. So what you need to do is download the latest firmware file from [http://www.otit.fi/~crope/v4l-dvb/af9015/af9015_firmware_cutter/firmware_files/ here] (this page is also accessible from the [http://www.linuxtv.org/wiki/index.php/DVB-T_USB_Devices DVB-T USB tuner comparison page] on the LinuxTV site), and place it in...
/lib/firmware
...on your core.

It was at this point that I plugged in my tuners for the first time. I then connected the aerial feed and rebooted the core as per Andrew's instructions. Once the core has booted, run "MythTV Setup" from the "Computing" section (accessible from the onscreen orbiter) and continue with the [[MythTV|MythTV setup process]].