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 ... 31
1
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« on: January 23, 2015, 09:46:33 am »
Yes, it should try to revive dead nodes automatically now, but it is kind of an experiment really.
If it improves things, great, but it could also introduce additional delays.

br,
sambuca

2
Users / Re: ZWave sensor values ??
« on: January 18, 2015, 10:13:06 pm »
This cannot be done at the moment unfortunately. It will need some coding to get the other values into the event system. At the moment, none of those values are actually stored anywhere so we would have to think about how to solve this best.

br,
sambuca

3
Users / Re: double entries
« on: January 07, 2015, 08:22:40 pm »
You will find Logging levels in Wizard - Basic Info -> Installation.

Can you check that the file is only added to LMCE once? This is not the same as it appearing in the orbiter once, as the orbiter display is by the Title attribute. Maybe if there are multiple titles on a file, it might appear more than once in the orbiter.
But these assumptions must be verified by what you find in the web-admin.

4
Users / Re: double entries
« on: January 07, 2015, 07:41:02 pm »
It would help determine if this is a bug if you could provide the UpdateMedia log for the resynchronization. Ideally with log level 10 (LV_STATUS) enabled.

It might also be useful to see what attributes the file(s) actually have using the media file sync.

br,
sambuca

5
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« on: January 06, 2015, 09:01:13 am »
You can add a node manually using the description you wrote or from the Advanced ZWave page (under the Automation menu in the web-admin). There is no need to know the port/channel number, these are assigned by the controller when you add a new device.

br, sambuca

6
Users / Re: [12.04] OpenZWave Aeon ZStick Issue
« on: January 01, 2015, 09:23:36 pm »
tompin2,

when the lockup happens, try to unplug and replug the usb dongle - that is the simples way I have found to fix the problem once it has occured.

To prevent it from happening in the first place, a good zwave network and a powered usb hub, as phenigma also mentioned, is the key. (one or the other might do it for you - I did both and have not had any major problem since). See our zwave page for information about troubleshooting the zwave network.

br,
sambuca

7
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

8
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

9
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

10
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

11
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.

12
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

13
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

14
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

15
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


Pages: [1] 2 3 ... 31