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 - totallymaxed

Pages: 1 2 3 [4] 5 6 ... 291
Users / Re: Internet radio and audio in Dianemo
« on: June 11, 2013, 01:46:21 pm »
Hi Posed,
Yeah I have an rti multi channel amp and a virtualised soundcard. So the Dianemo can't be without the Logitech media server, so this means at least a squeeze slave software client must be installed for each zone?


Yes you need a Squeezeslave & Squeezebox player for each audio zone on the RTI. See the RTI section on the Dianemo Wiki page for details;

and you should also see this section too;

and then this one for Internet Radio;

All the best


Users / Re: HDMI Matrix
« on: June 11, 2013, 01:37:21 pm »
Such devices are part of scenarios, and in the case of LinuxMCE, would be configured as the result of hooking pipes together.

I'm not sure if Dianemo still actively uses the pipe model, or if they've eschewed this for manual configuration.


Dianemo supports the pipe model. But we also have media_config which is a text file that allows you to create pipe type connections between devices and can be edited by any text editor.

All the best


Users / Re: HDMI Matrix
« on: June 08, 2013, 06:43:54 pm »
Hi Andrew,

I'm also wanting to write a device for an HDMI Matrix.  I've had a look at the Wiki and it looks to be a fairly simple job.  So I don't go off on a tangent, it'd be great to see one of the devices you mentioned.  I've had a quick look in the source and can't see them.

How do you surfaces the devices controls in the UI?  Or is it solely triggered from scenarios?  An example of this would also be very handy.

I look forward to your response.


Here is the source for the DCEwhisperer device for the HDAnywhere 4x8 v2 Matrix;


shopt -s extglob

. /usr/pluto/bin/
. /usr/pluto/bin/


## Mandatory functions
        local Q R
        local SerialPort
        local IPAddress

        SerialPort=$(GetDeviceData "$DevNo" "$DEVICEDATA_COM_Port_on_PC")
        SerialPort=$(TranslateSerialPort "$SerialPort")

        ## Device connection generics
        DeviceConnection_Type=serial # choices: none, serial, inet, custom
        ## Connection parameters
        # type=serial:
        DeviceConnection_BaudRate=600 ## yes, really: 600 baud
        DeviceConnection_Parity=N81 # choices: N81, E81, O81
        # type=inet:
        DeviceConnection_Protocol=TCP4 # choices: TCP4, TCP6, UDP4, UDP6
        DeviceConnection_Endpoint="$IPAddress:23" # Address:Port
        # type=custom:

        ## What to do when the device is lost
        DeviceConnection_OnDisconnect=reconnect # choices: disable, reconnect

        ## Device protocol generics
        DeviceProtocol_Type=stream # choices: line, stream
        # type=line:
        DeviceProtocol_Separator=$'\r' # must match encoding

        DeviceProtocol_Encoding=hex # choices: none, enc, hex
        DeviceProtocol_AutoAppendSeparator=no # choices: yes, no
        DeviceProtocol_Delay=.2 # delay between commands (seconds)

        local Q R
        Q="SELECT PK_Device FROM Device WHERE FK_Device_ControlledVia=$DevNo AND FK_DeviceTemplate=$DEVICETEMPLATE_
        R=$(RunSQL "$Q")

        local ZoneDevice Zone
        for ZoneDevice in $R; do
                Zone=$(GetDeviceData "$ZoneDevice" "$DEVICEDATA_Port")
                if [[ -z "$Zone" ]]; then
                export -n "Child_$ZoneDevice=$Zone"
        local Data="$1"
        Data=$(builtin echo "$Data" | tr -d '\r')
        echo "Device said: $Data"
## Unknown command handlers
        local From="$1" To="$2" Type="$3" Cmd="$4"
        local Zone
        local VarZone

        if [[ "$Type" != 1 ]]; then
                ReplyToDCE "UNHANDLED" ""

        if [[ -n "${!VarZone}" ]]; then
                case "$Cmd" in
                        966) RouteMediaPath "$Zone" "$Parm_219" ;;
                        91) InputSelect "$Zone" "$Parm_71" ;;
                ReplyToDCE "UNHANDLED" ""

        ReplyToDCE "OK" ""
        local From="$1" To="$2" Type="$3" Cmd="$4"
        ReplyToDCE "UNHANDLED" ""
## Hooks
        ## User configuration code

## Command functions
# Parameters come as environment variables of this form: Parm_<Number>

        Log "One thousand!! $Parm_999"
        SendToDevice "$Parm_999"
## User functions

        local Zone="$1" MediaPath="$2"
        local Path Type Input

        if [[ -z "$Zone" ]]; then

        Log "Route media path zone $Zone: MediaPath=$MediaPath"
        MediaPath="${MediaPath//:/ }"

        for Path in $MediaPath; do
                if [[ "$Type" != IN ]]; then
                InputSelect "$Zone" "$Input"
## The algorithm for computing the checksum is unknown
## These values have been extracted from the almost useless documentation received
## Otherwise, the commands are structured enough to be able to programatically build them
declare -a HardcodedChecksums=(
        AE FB 3F 51
        4C 19 DD B3
        12 47 83 ED
        91 C4 00 63
        local Zone="$1" Input="$2"

        Log "Input Select for zone $Zone: $Input"

        if [[ -z "$Zone" || ! "$Zone" =~ ^[1234]$ || ! "$Input" =~ ^[1234]$ ]]; then

        local HexZone HexInput
        local Checksum
        local HardcodedChecksumsIndex

        HexZone=$(builtin printf "%02X" "$Zone")
        HexInput=$(builtin printf "%02X" "$Input")
        HardcodedChecksumsIndex=$(( (Input - 1) * 4 + (Zone - 1) ))
        local Cmd="BABABFC603${HexZone}${HexInput}${Checksum}"     

        ## Send twice, for reliability
        SendToDevice "$Cmd"
        SendToDevice "$Cmd"

        ## The 03 after BABABFC6 appears to be a "select input" command
        ## There are two other commands in the documentation: 04 - "select previous input", 05 - "select next input
        ## The structure thus appears to be:
        ## BABABFC6 - 4 bytes that don't change
        ## CC - one byte representing the command (03 - "select input", 04 - "select previous input", 05 - "select
        ## OO - the output the command operates on
        ## PP - the input to be selected (for command 03), or 00 (for commands 04 and 05)
        ## KK - a checksum - algoritm unknown (see note on hardcoded values above)
## Start eveything up
. /usr/pluto/bin/ "$@"

Users / Re: Dianemo S and X10 CM15A
« on: May 28, 2013, 04:09:40 pm »

sorry for the delay, I was away for a couple of weeks. I just ran the latest updates and I can confirm the problem is still there.

I've enabled Remote Assistance now, please take a look and let me know how I can assist (I'll email you the access code).

Thanks !

Hi Alex,

Sorry it was a long holiday weekend here and I've only just caught up with my messages. It looks like we may have broken something in this package through some changes we made in another package related to serial devices. We're working on a fix - please leave your Remote Assistance on and we will test the fix on your system asap.



Marketplace / New Dianemo Site
« on: May 28, 2013, 03:53:46 pm »
We have a shiny new web site up now which hopefully will be hardened against any known exploits... for now at least.

Thanks for your patience.


Users / Re: Dianemo S and X10 CM15A
« on: May 09, 2013, 01:16:07 pm »

There are not many (if any) Dianemo users with X10 installations so its possible that the CM15A device has a problem that's not been noticed. We'll look at this asap if you make sure Remote Assistance is on.

All the best


Developers / Re: Building Dynamic Orbiters with JSON/AJAX/HTML5
« on: May 08, 2013, 05:15:13 pm »
some progress on the ago control side. We've settled onto a MVC approach via ember js and jquery. It also supports templates and other nice things. Gumby is used for the appearance. Communication is done viai JSON-RPC. Getting the inventory (aka device list and stuff™), sending commands and receiving live status updates works fine so far. Still a lot of work to do but hey this is brand new, very hot, and will receive a lot love over the next weeks and months.

Hari - did the bug Uplink reported that caused Ago to crash when a device was placed in a 'room' get fixed?


Is the dianemo website down? I'm unable to access. Thanks.

Yes it is - apologies for the downtime. We're working on it.



Developers / Re: Lightpack
« on: May 01, 2013, 01:40:55 pm »
Didn't someone announce this kickstarter elsewhere here? atmolight is working with TV playback for VDR users already.

Yep here ;-),13227.0.html


Users / Re: Dianemo S: Logitech Media Server and tags problems
« on: April 23, 2013, 12:11:05 pm »
Yes it only applies to audio. Video still uses UpdateMedia.

All the best


Users / Re: Dianemo S: Logitech Media Server and tags problems
« on: April 18, 2013, 02:23:22 pm »

I'm not sure to what extent this also applies for LMCE, but I'm having a lot of problems under Dianemo S that currently switched to Logitech Media Server as internal music system...

First of all, the main problem is that my collection is not properly tagged and I'm waiting for option to use it via Folder structure... But that's another story... I'm trying to tag my collection as much as possible correctly, but have problems...

I've tagged few folders with mp3, wav and flac files. Then I tried to use LMS to rescan library and encountered following problems :
1. LMS behaves strange when you do only "scan for new and changed" media files. It finds all files, but when it should end scan it waits there forever... I have to abort scan. What I've learned is that it's recomendable to do full rescan each time...

2. if I scan only specific folder then all tag data seem to appear correctly on LMS (I'm not doing anything on Dianemo yet)... But when I do rescan of whole library (all folders) then my data from specific folder don't appear anymore... There are few errors about incorrect tag values on some files, but I guess this shouldn't interfere with files that are correctly tagged... But obviously something is wrong...

Anyone with same or similar problems ? Any advice ?

Thanks in advance,



All audio library scanning of meta data is now done by LMS. Most users are using iTunes alongside LMS to purchase or rip audio tracks - but in fact you can use anything that correctly adds the id3 data to your audio tracks. Feedback to date seems very positive to date.

It could be that your id3 tag data is causing this problem - can you send us (Uplink or myself) some id3 data from a few tracks for us to look at?

All the best


Users / Re: Driveway Sensor
« on: April 18, 2013, 02:13:18 pm »
I have been pleasantly surprised by the prices as well.  I am definitely going with the buried induction sensor.  It seems to be the only device that will not be interfered with by snow and other weather events.  :)

Thanks guys.


Induction sensors are definitely the way to go on this as any other method can be accidentally triggered and cause false positives.

All the best


We have released an update today that adds a new page to Web Admin that will list the details of all the UPnP devices that are detectable on your Dianemo systems LAN. This means that you can discover, identify and configure UPnP devices now without requiring any external UPnP discovery tools. All that's required now is a Web Browser and Web Admin.

You can find the UPnP Devices page in Web Admin here;

Advanced->Configuration->UPnP Devices

There is also an enhanced and updated Wiki section here to help you use UPnP Devices to configure devices on your system here;

As usual please run your Updater script to update your system with the latest Dianemo & Ubuntu updates.

All the best


Marketplace / Update Available - ZWave Device binary updated
« on: April 06, 2013, 12:44:07 am »
We have released an updated ZWave device binary this evening.

Today we discovered a bug in the ZWave device. A very old bug that's been there for a long time. This bug caused commands sent to multiple sleeping devices to be dispatched when a sleeping device woke up, even if the messages weren't meant for it. Those extraneous messages would time out, obviously, and get lost, so their intended target never received them. If three of these timeouts happened in a row then the ZWave DCE device would think that the USB dongle had a problem, so it would soft-reset it. This would cause all pending undelivered messages to get lost.

As usual pleased run the updater script to download and install this update on your System.

All the best


Installation issues / Re: Squeezeslaves on Core (Dianemo S)
« on: April 05, 2013, 03:23:11 pm »
I think I know what the problem is;

You did not virtualise your sound card before using it. I'll virtualise one of your cards for you and re-test it...

Right I've virtualised one of your USB soundcards (see your Web admin for my changes that follow the Dianemo wiki section on virtualising soundcards). OK now tested and now your Squeezeslave does not die and looks to be working in LMS.

All the best


Pages: 1 2 3 [4] 5 6 ... 291