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

Pages: [1] 2 3 ... 30
1
Users / Re: CT100 ZWave Thermostat Fahrenheit vs Celcius
« on: November 29, 2014, 04:18:46 pm »
Hi.

You might need to reboot or do "sudo killall ZWave", due to the way the driver works. It's one of those things I've been trying to find a good solution for...

Br,
Sambuca

2
Users / Re: CT100 ZWave Thermostat Fahrenheit vs Celcius
« on: November 17, 2014, 08:50:35 am »
There is nothing in the template that decides what unit the temperature is interpreted as. All my devices works as expected (I also use Celsius) and I don't recall having to do anything special.  But I do think some devices has a configuration setting to toggle the unit it interprets values as - you should read the manual for your device.

br,
sambuca

3
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« on: October 18, 2014, 11:30:12 am »
Hi davegravy,

As RayBe said, the log messages you posted are only informational, and can be disregarded in cases like this.

The Aeon stick can be a bit difficult, and there are a few reports around the net that it can lock up and require a power-cycle to bring back (unplug and replug the stick will do). I have also experienced this. This problem seem to happen on other zwave stacks beside OpenZWave also.
I'm not concluding that this is your problem, but if things lock up, please try to unplug it and replug the stick.

If you have communications problem where a node is considered dead, you should use the new Advanced ZWave page (under Automation in the web-admin) to troubleshoot the issue.
See the wiki page for more information about it.
If a node is dead, the node will have a red color in that page. To bring back a single dead node, use the "Test node" command on the node.

br,
sambuca

4
My guess is a combination of a lock-up of the stick (some Aeon sticks will lock up and have to be un/replugged to resume normal operation), and mismatch between the port configured and the actual port. (Re-plugging a device might assign it a new port as well).

br,
sambuca

5
Users / Re: zwave network lockups/delays
« on: August 22, 2014, 11:22:20 am »
It is probably some HTML/CSS problem that appears in chrome. You could try to use a different browser.

6
Users / Re: zwave network lockups/delays
« on: August 15, 2014, 09:27:35 am »
The delay are usually caused by two things - network problems or a device that does not respond to a command (firmware bug or incomplete OpenZWave configuration for that device).

Heal network will run for a long time if you have many devices, which it looks like you have, so that would be expected. I don't know how long, as I have never tried, and I don't have the same number of devices either. If it does not stop, I would reboot.

I would recommend using heal node instead, as this runs much faster, on just the nodes that are having problems.

br,
sambuca

7
Users / Re: zwave network lockups/delays
« on: June 13, 2014, 07:35:43 am »
ZWave is designed to route messages between the devices, so if one device is unplugged or there is a temporary radio communication problem, you will get a failed transmission. By default, a failed transmission will cause the ZWave driver to delay, to allow the network time to re-route the message. If the message is still failed, it will try to re-send it, and once again cause a delay if it fails. This delay can be tuned up or down, but experience has shown that some USB sticks require a high delay(30-40s) or they will lock up and need to be unplugged and replugged.

The best way to avoid this is to make sure your devices all know about their neighbour devices, so that they are well connected. (The messages are routed through a device's known neighbours). If you use LMCE 1204, there is the new Advanced ZWave page (in the Automation menu) that will display this clearly and provide commands to fix such problems (Heal Node / Heal Network).

Adding more devices between the usb controller and the problematic device can also help better routing to that device.

regards,
sambuca

8
Users / Re: Many minor issues
« on: May 30, 2014, 11:40:16 am »
2. It might well be missing translations.. I never seen any problems using english.

3. It is a bit slow to start up,  but I can't say I've seen delays. I'm using it primarily on an old HTC Desire HD. It could be bad network reception as well.. Although, sometimes it seems to not register screen touches, but I'm not sure whether it's my fingers or something with qOrbiter.

5. I don't think the "new" squeezebox radio is branded as such, but it looks almost the same.

And, by the way, I use 1204, I don't know if there are any changes from 1004 to 1204 affecting your problems, but newer drivers etc. might help playback issues.

br,
sambuca

9
Users / Re: Many minor issues
« on: May 29, 2014, 10:08:41 pm »
Hello and welcome  :)

I have a few comments:
1. Do you by any chance have 50Hz TV transmissions? I suspect that the default setup of LMCE is to have 60Hz framerate, and I in some cases had to manually correct this to match it to the TV transmissions. (even after selecting 50Hz in the AV wizard - at least you should verify the framerate- I think it should be written in the xorg.log) Not sure if that still applies in 1004...

2. The titanium skins are the best afaik, and use V2 Normal Horizontal as UI.

3,4,5: I would use the new qOrbiter for android (phone or tablet). It is not complete, but I find the qOrbiter phone skin to work very well for a day to day remote, including media browsing. You might have a different usage pattern, but give it a try and report back what is missing for your use.
Also, I would use qOrbiter instead of remote controls, but that is my preference.
Logitech still sells a modified/rebranded Squeezebox Radio afaik, and this works well with LMCE (I have two).

br,
sambuca


10
In short, yes.

But it might take a while (perhaps 30 sec) because this is normally done by polling all the devices. Not all ZWave devices support sending state changes back to the controller.

br,
sambuca

11
Users / Re: Energy Monitor configuration?
« on: March 18, 2014, 07:35:38 am »
I'm not sure there are much documentation unfortunately. If there are any, it should be in the wiki.

But look in the lmce_datalog database, there are only a handful of tables there, so it should be fairly easy to see the connections.
The query you posted also references the main pluto_main database, more specifically, the Device and Device_DeviceData tables. It does this to look for devices with the "Energy Consumption" device data. (This coupled with the on/off state, as mentioned, is used to calculate total energy usage for that device.)

br,
sambuca

12
Users / Re: Energy Monitor configuration?
« on: March 16, 2014, 11:56:37 am »
If I remember correctly, the energy monitor uses state changes on devices coupled with the user-defined energy usage of said devices to calculate the energy usage. It is not equipped to show anything useful for devices that report exact energy usage.
So for your case, the energy device does not report any state changes, thus no data and you get an error.

If you feel up to it, we would appreciate someone digging into the code (its all in php) and try to get it to support both ways. (For instance, if no state changes are found, look for reported energy usage instead)

br,
sambuca

13
Feature requests & roadmap / Re: Android audio media director
« on: February 28, 2014, 08:43:56 am »
Not out of the box, no.

Qorbiter is the new orbiter software, and has nothing to do with the other media director capabilities (like playback). On a standard MD other pieces of software will take care of the playback, with the orbiter simply acting as a controller/remote. How this will be for qOrbiter I'm unsure about. I know some built-in media playback has been discussed for qOrbiter, but if that is going to be the way, I don't know.

Other possibilities for android are DLNA or the "standard" android media player (standard as in every manufacturer are free to add their own...) Anyway, for it to be a complete MD (at least for playing audio) we need some way to control playback from the LinuxMCE.

br,
sambuca

14
Users / Re: Z-Wave USB Dongle
« on: January 08, 2014, 05:03:14 pm »
Maybe the usb ID of this dongle is not autodetected..?
Look at the output from the "lsusb" command and see if that id exists in the ZWave device template.

br,
sambuca

15
Installation issues / Re: Toshiba RAS-13 IR Codes
« on: November 24, 2013, 07:47:00 pm »
The IR code for this Toshiba air-con are generated by a LMCE GSD device. This means that there are ruby code that generates the IR code. When I first made this, I used an USB-UIRT to receive the IR signal and decode its meaning, then creating a program that generates equal IR code based on the commands from LMCE.

It has been a long time since I made this, so I can't really help except point to the Ruby code in the LMCE device template.

br,
sambuca

Pages: [1] 2 3 ... 30