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

Pages: [1] 2 3 ... 7
1
I added Manually the zstick for testing, this is the error I get

Code: [Select]
== FRESH START ==
1 02/09/16 20:05:16 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:05:16 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:05:16 267 (spawning-device) Starting... 1
1 02/09/16 20:05:16 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:05:16.758 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
05 02/09/16 20:05:16.758 The router must be reloaded before this device is fully functional <0xb6e83700>
05 02/09/16 20:05:16.759 void ClientSocket::Disconnect() on this socket: 0x946a610 (m_Socket: 5) <0xb6e83700>
05 02/09/16 20:05:16.811 Connection for client socket reported NEED RELOAD IP=::ffff:127.0.0.1, device 267 last error 2 <0xb6e83700>
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:05:16.858 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 20:06:55.412 Got a reload command from 0  <0xb5affb40>
05 02/09/16 20:06:55.664 void ClientSocket::Disconnect() on this socket: 0x946af18 (m_Socket: 6) <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveData 0x946a378 failed, bytes left -1 start: 10000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e83700>
05 02/09/16 20:06:55.665 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e83700>
01 02/09/16 20:06:55.665 Lost connection device: 267 <0xb6e83700>
05 02/09/16 20:06:55.665 Handshake failed. Retrying in 5 seconds <0xb6e83700>
05 02/09/16 20:07:01.672 Connect() failed, Error Code 111 (Connection refused)) <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 268 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
05 02/09/16 20:07:04.735 Creating child 269 <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e83700>
05 02/09/16 20:07:04.735 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e83700>
01 02/09/16 20:07:04.790 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result /dev/ttyUSB0 <0xb6e83700>
05 02/09/16 20:13:09.968 Got a reload command from 0  <0xb46ffb40>
== ATTEMPT FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) 2017 Dev: 267; Already Running list: 15,33,
== FRESH START ==
1 02/09/16 20:41:31 /usr/pluto/bin/Spawn_Device.sh 267 (spawning-device) device: 267 ip: localhost cmd_line: ZWave
0 02/09/16 20:41:31 267 (spawning-device) Entering 267
========== NEW LOG SECTION ==========
1 02/09/16 20:41:31 267 (spawning-device) Starting... 1
1 02/09/16 20:41:31 267 (spawning-device) Found /usr/pluto/bin/ZWave
05 02/09/16 20:41:31.558 Creating child 268 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 20:41:31.559 Creating child 269 <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 20:41:31.559 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 20:41:31.619 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
2016-02-09 20:41:31.620 Info, Reading /etc/openzwave/options.xml for Options
05 02/09/16 21:07:11.236 Got a reload command from 0  <0xb5affb40>
05 02/09/16 21:07:11.488 void ClientSocket::Disconnect() on this socket: 0x9699ef8 (m_Socket: 6) <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveData 0x969f2c0 failed, bytes left 0 start: 30000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 4 Event Dev #267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Event Dev #267 <0xb6e9c700>
01 02/09/16 21:07:11.489 Lost connection device: 267 <0xb6e9c700>
05 02/09/16 21:07:11.489 Handshake failed. Retrying in 5 seconds <0xb6e9c700>
05 02/09/16 21:07:17.495 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:18.496 Connect() failed, Error Code 111 (Connection refused)) <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 268 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1820 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
05 02/09/16 21:07:21.560 Creating child 269 <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom event handler for.  It will not fire events. <0xb6e9c700>
05 02/09/16 21:07:21.560 Note: Device manager has attached a device of type 1922 that this has no custom handler for.  This is normal for IR. <0xb6e9c700>
01 02/09/16 21:07:21.613 TranslateSerialUSB pci0000:00/0000:00:1a.0+1.6.2 result  <0xb6e9c700>


What is this connection refused?

Regards,

TP

2
Installation issues / Re: 12.04 Aeon Z-stick (Zwave) is not detected by PnP
« on: February 10, 2016, 01:19:18 am »
PnpQueue::Process_Detect_Stage_Confirm_Possible_DT queue 7850 already unknown <0x8b9adb40>

^^ This line here indicates that the device is found in the Unknown Devices table.  Which means it has been told to Not be used and don't ever ask me again.  Hence why it is not adding the device.  Find the device in the webadmin -> advanced -> unknown devices list and remove it.  It should add itself the next time it is detected.

J.

Hi Phenigma,

Im Having more or less the same issue but in my case there is nothing under unknown devices.  How the issue was caused.  I wanted to do a fresh start of the zwave config, because I messed up one of my motion sensors and I was unable to remove it.  I used webadmin and removed zwave device, pull the stick out, reset the stick and the minimote and plug the zstick back again but it does not get detected by PNP.  Linux is detecting it and setting as ttyusb0

157645.840518] usb 1-1.6.2: cp210x converter now attached to ttyUSB0

But nothing happens later, there is no pnpqueue on the log registered neither. 
Any hints?

TP

3
Users / Re: Aeon Labs Z-Wave Multisensor
« on: October 19, 2015, 03:02:29 pm »
Thanks Phenigma and Rebelkiller,

Ill get a pair of Fibaro Multisensors FGMS which are easy to get via amazon and start doing test.
Since I had nothing to loose, I tried to update the firmware of one of the aeon sensors.  It got killed!, it just blinks and that's it!.. So how to I remove it?.  Manually remove, do I have to do anything else on the controller?.  I kept the other sensor untouched as reference point and for torture purposes... There most be a way to make them speak to lmce!!!

Cheers,

T

4
Users / Re: Need some dedicated testers.
« on: October 17, 2015, 02:33:25 pm »
Good to have you back.. no need for apologies.. I wish we could do more than complain  :D!!. Feedback is given with the best interest .. im sure must of us have plenty things to do in the outside world.   thanks for all your effort. Keep up posted on what else we can do to make your life more difficult ahhahahahahha!...

Cheers,
T

5
Users / Re: Aeon Labs Z-Wave Multisensor
« on: October 15, 2015, 06:24:56 am »
I finally removed the Aeon device completely from my home.

My observations:
- temperate is measured in F not C
- temperature values are far away from "reality" (x/1)
- luminance level is ok (x/2)
- motion detection is ok (x)
- humidity values shown in log, but not in lmce (x/3)
- device fires brightness level changes (1 lux!) too frequently what leads to unresponsive mesh network
- in battery mode it is nearly unusable
- use of usb power makes it more responsive

Thanks for the feedback Rebelkiller!..., I guess thats a nice way to say ... don't waist your time!! hahahahaah.
Are you using a better zwave sensor with at least movement, temp and luminance?  One you could recommend?

6
Users / Re: Aeon Labs Z-Wave Multisensor
« on: October 12, 2015, 06:21:35 am »
Hello to all,

Ok I have finally reach to a better test.  I deleted the sensor from using the remote.  Reload the sensor again. 
lmce detected:
Temperature as instance 1 (23/1)
Brightness (23/2)
 and two generic sensor
Generic 23 (suppose is motion)
Generic 23/3 Could this be humidity?

I had to press the button at the sensor in order to make it alive, before that, it was posting no values.
So at the zwave advance, under values it started posting values as the picture attached.
This sensor has motion, temp, luminescence and humidity.  Temp is totally off is there a way to calibrate or to shift values.
How can I let LMCE battery values?
Ill continue testing and keep all posted

T

7
Users / Re: Aeon Labs Z-Wave Multisensor
« on: October 06, 2015, 05:35:45 am »
hi tompin2,

Are you using 1004 or 1204 ?

In 1204 the zwave has changed a lot so I would think the device mostly works out of the box.

br,
sambuca

Hi Sambuca,

Im using 1204... so far it seems to be detected but I get no values, there must be something Im missing.
Follow log of main zwave controller (zstick), are here.

05   10/05/15 22:22:24.968       * Device id = 22, dt = 1813 (Generic Sensor), main label = Sensor, pk_parent = 182 <0xb6e23700>
05   10/05/15 22:22:24.968        -> Already mapped to device, PK_Device=206 <0xb6e23700>
05   10/05/15 22:22:24.968       * Device id = 22/1, dt = 1744 (Temperature Sensor), main label = Temperature, pk_parent = 181 <0xb6e23700>
05   10/05/15 22:22:24.968       * Device id = 22/2, dt = 1745 (Brightness Sensor), main label = Luminance, pk_parent = 181 <0xb6e23700>
05   10/05/15 22:22:24.968       * Device id = 22/3, dt = 1813 (Generic Sensor), main label = , pk_parent = 0 <0xb6e23700>

Values under advance zwave

Values
Index   Label   Value   Units   Genre   PK_Device   Polled
0   Sensor   False      user   206   
0   Battery Level   100   %   user   206   
1   Minimum Wake-up Interval   0   Seconds   system   206   
2   Maximum Wake-up Interval   0   Seconds   system   206   
3   Default Wake-up Interval   0   Seconds   system   206   
4   Wake-up Interval Step   0   Seconds   system   206   
0   Wake-up Interval          0   Seconds   system   206   
0   Library Version   Unknown                      system   206   
1   Protocol Version   Unknown                      system   206   
2   Application Version   Unknown              system   206   
1   Temperature                    0.0           user   207   
3   Luminance                            0.0             user   208   
5   Relative Humidity             0.0              user   209   

Any hints?

8
Users / Re: Need some dedicated testers.
« on: October 05, 2015, 02:30:32 am »
I think after the updates I put yesterday, qorbiter is broken. I didn't have it in any room anymore, so I uninstalled it, deleted the linuxmce-folder from the tablet rebooted an reinstalled it, but it won't work. I got a screenshot for your viewing pleasure
Dear All, It happened the same to me.  I was testing with a Samsung S6, no linuxmce folder either, neither the create a new orbiter option.  What it did worked was the finding a previous created orbiter.
I did also tryed on a Samsung tab2 which worked fine before the update, after the update same as maverick.  It seems to me that the issue is at the lmce server side.
I had as reference point a Samsung s4 without doing any updates on the android app and the same results.

LMCE version: 2.0.0.46.15090731351
qorbiter qt5a1-gl

I hope this info is helpful
Willing to test any update with both of the systems.

Cheers,
T

9
Hi Phenigma,

You are absolutely right!! Thanks for the response!!!, let me correct that right away.  The problem is solved now I just did not have time to update.
I have no idea (probably for my continuous never ending learning curve on linux) why but I went to KDE desktop and open the package manager as root and it did show several more packages that needed upgrade, that did not where shown at the console using apt-get.  Upgrade them all and problem solved.  I did had to do apt-get install on one that the package manager didn't wanted to do it but apt-get did the trick.
System up and running!

Cheers,
T

10
Dear All,

After doing update/upgrade/disklessTBZ  and today I'm getting a issue with two packages.
The weird thing is that no computer within 192.168.80 network can access outside but the core.  Core is ok

Code: [Select]
sudo dpkg --configure -a gives this
Setting up lmce-diskless-tools (2.0.0.46.15091031356) ...
/var/lib/dpkg/info/lmce-diskless-tools.postinst: line 48: /usr/pluto/bin/UpdateDebCache.sh: No such file or directory
dpkg: error processing lmce-diskless-tools (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of pluto-newmdinteractor:
 pluto-newmdinteractor depends on lmce-diskless-tools (>= 2.0.0.46); however:
  Package lmce-diskless-tools is not configured yet.
 pluto-newmdinteractor depends on lmce-diskless-tools (<< 2.0.0.47); however:
  Package lmce-diskless-tools is not configured yet.
dpkg: error processing pluto-newmdinteractor (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 lmce-diskless-tools
 pluto-newmdinteractor

It appears that there is a bug in diskless tools.  But also newmdirector has issues.    Any ideas?


11
Installation issues / Re: LMCE google chrome and netflix - SOLVED!
« on: May 24, 2015, 07:55:37 pm »
And it is called.... http://wiki.linuxmce.org/index.php/Adding_new_computing_apps

:)
Hello to all, for future references, this was my output, It may help others.

WM_CLASS(STRING) = "Google-chrome-stable ()", "Google-chrome-stable"

So the class_instance.class_Name for LMCE will be:

Google-chrome-stable.Google-chrome-stable. (this is what will be needed on webadmin)


Cheers,

T

12
Installation issues / Re: LMCE google chrome and netflix - SOLVED!
« on: May 14, 2015, 06:10:19 am »
Thanks Phenigma and Posde for your patients!
I guess I should go more often to the wiki  ;D!...
Phenigma, my apologies of not adding this info: 
Linux version 1204 consistently updated via apt-get update/ upgrade
Core Running on Dell T20, testing MD is a zotac ZBOX
Keep all posted

Cheers,

T

13
Users / Re: Need some dedicated testers.
« on: May 14, 2015, 05:58:05 am »
Hi Golgoj4,

It worked perfectly!!!!.  Please, let me know how can I help more.  Really appreciated your dedicated time!.

Cheers,

T

14
Feature requests & roadmap / Re: Integration of streaming sites?
« on: May 11, 2015, 11:15:39 pm »
Hello to all,

My two cents on Netflix!.  I Installed Google Chrome and I was able to get Netflix running Perfectly.  I Started a Post not long ago sharing how to do it. Just a few tricks on video acceleration for chrome and nvidia and running as root.
I was able to run it without any issues on a Zotac Zbox I use as MD.

 http://forum.linuxmce.org/index.php?topic=14056.msg101567#msg101567

The only thing I don't know how to do is to make LMCE start Chrome instead of Firefox.

Cheers,

T

15
Users / Re: Need some dedicated testers.
« on: May 10, 2015, 09:52:32 pm »
Im very sorry for being so MIA as of late. Work, Life, etc has left me with little time to keep folks up to date on the happenings of development.

*Last month has been spent converting from networks skins (problematic on multiple levels) to an new way of doing things. Basically, users wont half to be part techie to update their skins. Skins will be in the application from now on.

That means that if you have recently grabbed Qorbiter for android, you should already have them on your device. I am working on the remote screens now before I make it the default.

There is a setting which will allow you to choose if you want the internal vs external.
https://www.youtube.com/watch?v=nLY8r7uR4YI This video shows how to change back and forth.

Maverick: mythtv screen isnt in there yet, but the live tv screen is. That means that when i get back from my biz trip, I can enable the mythtv screen as its basically the same as the livetv.

Thanks again to you intrepid users who are so patient. It really is helpful even if it seems like nobody is listening to your issues / responding.


And now for this
https://www.youtube.com/watch?v=nh3CsehIgIY
*note the ios version is using the internal skins.


-Langston

Hi,  I din't seem to work for me which version is the one you are using on that youtube video?, it looks different than mine.  Im using the one I get from the webadmin.  If I download the one is on your link, I get the white background and that's it!. 
Version from my webadmin : qt5a1-gl, but is says debug at the installer.  Yours is the same, but after it says loading, I get a white screen and that's it!
The debug version does not show that skin option, can I change it manually at the xml?

Cheers,

T

Pages: [1] 2 3 ... 7