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

Pages: [1] 2 3 ... 14
1
Users / Re: An interesting set-up
« on: October 30, 2012, 08:59:37 pm »
Are you talking about physical security where the core will be located or network security?  I'll be completely honest with you I think this would be unnecessarily complicated (and i'm a "go big or go home" kind of guy).  When I had my second house I thought of doing the same thing but then I figured for the price of a zwave dongle and a capable pc for a core it would just make sense to have two separate systems.  The site to site tunnel allowed for accessing media at either locations but that is separate of Lmce. 

My opinions aside, you can achieve this.  You will need a zwave dongle at each location.  For some reason i'm of the impression that you can only have one dongle per system but it could be one per MD or core (someone enlighten us on that one). If it's one dongle per md or core then you can control lighting at location B from location A provided that there is a dongle at location A and B.  Your security system will also have to be IP based.  You'll need a keypad or some other interface for the sensors at each location.  With current internet packages and VPN technology what it is today speed and reliability wont be a huge problem or a deal breaker. 

Now for the tricky part.  If you have advanced networking skills, which you're probably lacking since you asked this question (no offense), you'll have to setup a site to site tunnel to essentially put both locations on the same network.  I say the "same network" but that's not really what you're doing since it's 1: a very bad idea, 2: difficult to keep straight, and 3: unsupported and/or disallowed on most routers. 
You'll need 2 "advanced" routers (one for each location), Disable the firewall on the core, and a few routes and rules.

Code: [Select]
(assuming cable connections but will work with any type of connection)
Location A

ISP <---> Cable Modem <--192.168.1.2 Router A <---192.168.2.2 Core <---192.168.80.0 LMCE Network A

Location B

ISP <---> Cable Modem <--192.168.3.2 Router B <---192.168.80.0 LMCE Network B

Steps
1: The core will have to be configured to broadcast DHCP offers on all interfaces. 
2: A VPN tunnel will have to be created between Routers A and B. (configuring how the routers handle internet VS Lan traffic is a whole other conversion with various perks, repercussions, and challenges)
3: Router B will have to be configured to relay DHCP requests through the VPN tunnel to router A, Router A will then have to Relay these Requests to the Core. 
4: Router A will have to be configured to relay the DHCP Offers back to Router B VIA the tunnel, then Router B has to relay that offer to the requesting client. 
5: Typically, LMCE Network A and LMCE network B will be two separate IP ranges.  Because of the nature of LMCE, changing the IP range  has negative repercussions.  So you'll have to keep these two networks with the same IP range which means you'll need some fancy rules on router A and B to make sure traffic makes it where it needs to go.  I've never had to do this (because it's a really bad idea and would be a pain to actually get it to work(in this way)) but I would imagine you'll spit the ip range down the middle.  Since Lmce already does this you'll be splitting it twice (or else you'll be creating a custom rule on each router for each device on your network). For LMCE devices you'll spit that range in half, one half for each location. Then create a rule so router B knows that devices in the first part of the range are at Router A and vise verse.  Then you'll do the same for the non LME devices IP range.  LMCE isn't smart enough (no offense devs) to know that you split the range in this way so you'll have to reassign devices manually as you add them to the system. (Good luck with steps 3 - 5, I've seen this trip up some seasoned Network admins)
6: you'll have to make the core Vlan aware and configure Vlans on the core for the external interface.  You'll need a vlan for the 192.168.80.0 range on the second network.
7: you'll have to create Vlans on the routers as well to match the core.  (steps 6 and 7 should be higher in the process, before setting up dhcp)
8:You'll have to also create custom rules on the core, after all the core is a router among other things.  It'll have to know that MD 1(192.168.80.2) is at ETH2 but MD 2 (192.168.80.15) is at ETH1.. or better yet Eth1.1.
9: Cross your figures and hope it all works. (as far as firewall rules, leave all firewall options disabled for the tunnel or allow all traffic (any, any rules)).

Are you still with me?  UNNECESSARILY COMPLICATED!

To simplify step 5, give LMCE network B a different IP range.  The routers will have to tag DHCP requests and the Core will have to be configured to give different IP configurations for the tagged requests.  You'll still have to create rules and routes but they'll be simpler and more industry standard (meaning they'll "just work").  You'll clear up a lot of network related issues but you may experience LMCE specific issues.

Either way good luck getting support from the community, and did I mention unnecessarily complicated? If not... unnecessarily complicated! 

Good luck

2
Users / Re: Linux MCE beating as the heart of whole house automation
« on: September 28, 2012, 04:08:52 am »
If there is a spec available and I get remote access via SSH to a system where it is hooked up to the serial, and a slave to press buttons on request, I can write a proper C++ device for it.

I'm currently using Dianemo.  How would that work?  Would you be able to use it for Lmce also?

Also, I swapped out my panel because my house is currently staged for sale.  The Caddx is at a storage facility about an hour away.  I should be heading in that direction this weekend, if I don't it'll be next weekend.  I have to grab a few things and I've been putting it on the back burner.  I'll grab the panel, a keypad and a couple sensors and set it up on my work bench.  I'll PM you once it's connected.  I'll even paypal you once it's all working properly.   

3
Users / Re: Linux MCE beating as the heart of whole house automation
« on: September 26, 2012, 08:47:06 pm »
klovell,

according to jamo the Caddx NX-8E is working. He marked the wiki article as working in 1004. You might want to open a new thread detailing what your problems are, and maybe jamo can help you get things sorted out.

I'm going to have to do that.  This is the only part left to the system of my dreams that either isn't working or I don't have a work around for.  As soon as I get free time. 

4
Users / Re: Linux MCE beating as the heart of whole house automation
« on: September 26, 2012, 08:39:29 pm »
I have said this over and over again. If you want proper integration with LinuxMCE, you'll need to write a driver. I can't write one, because I don't have the hardware. If you want support for this Caddx panel, write a driver.

-Thom

There is already a template for it but it doesn't work.  Are you saying there are templates in the database with no drivers?  Why the heck are templates allowed into the production database that everyone gets if all associated pieces have not been implemented?  If that's the case they should at least carry some kind of description so people know they're not fully implemented.

5
Users / Re: Linux MCE beating as the heart of whole house automation
« on: September 26, 2012, 08:24:18 pm »
Well, thanks for sharing your experience with us. I'm glad you did!
I don't know if it is something you did wrong or if it's the instructions that were the problem. Can you elaborate on the steps you took?

On the other hand, I'm sure people are actually running this (it's listed as compatible). Anyone care to give us simple instructions we can actually follow and make it work?


It is listed as compatible and there is a template for it.  Lmce or Dianemo just doesn't seem to want to communicate with it.  There are no logs (that I can see) so it's very difficult for someone like myself to trouble shoot.

As far as the steps I took, I literally followed the instructions in the wiki verbatim.  When that failed I went on a google rampage and found additional setting not in the wiki that needs to be configured in the panel itself.  I also found a cool little windows utility to connect to the panel.  When the new panel setting failed to start communications between the panel and Lmce/Dianemo, I installed the windows utility on my laptop and was actually able to control the panel from windows.  That pretty much confirmed it for me that it wasn't the panel or it's settings.  I reached out for help but never got any.  My assumption to why it's listed as compatible is because the panel has a standard serial port, the protocol sheet is widely available, and it'll talk to anything plugged into the serial port.  Like I said, I was specifically told this one will work so I didn't bother to research it (shame on me), but after the fact I did some forum searches and I found that no one actually claimed to have this panel working, then I saw in the wiki "still trying to get this working...". 


 

6
Users / Re: Linux MCE beating as the heart of whole house automation
« on: September 26, 2012, 06:39:54 pm »
Well, turns out a friend of mine has a distributor license for security installation, so today I took a trip to the store, and they seem to have everything. They especially seemed to have a lot of those red boxes (I think it's Honeywell). They did not have the NX-8E in stock but thy can have it in the store from the warehouse in 24hrs. I'd like to purchase it since it's the one on the wiki (unless I can do the same thing with the content of the red boxes in a plug and play fashion). In order to pick the right package (the counter people did not seem to now much about the products - they just knew where to pull them from) I have a few questions:

* The Caddx NX-8E wiki page states: "--still trying to get the alarm panel to work so if anyone has LinuxMCE configuration help, please include it here.--"
Should I safely buy this panel?
* What is the difference between a zone and a partition (the manual was not clear)? How do you use them in your implementations?
* There are accessories such as a relay output (NX-506E) that go with these panels. Which accessories should I ask for?
* The GC100 on homeseer.com site that look different than the pictures on the wiki. Does anyone know is it's because it's an older model, or is it a totally different device? It's from the same mfr.

I was explicitly told I could get the Caddx NX-8E as it will integrate right in...It did not!  Fortunately that is a bad ass panel with tons of options so I've been using it as a stand alone with central monitoring but it would be nice to one day be able to control it from an orbiter.  If you want plug and play skip the Caddx.

To answer your other question about if a panel is even needed, I think it's 200% needed.  I personally wouldn't do the GC100 thing, I would use MCE (in my case Dianemo) as a supplement to the panel.  Have the Panel talk to the monitoring station the way it was intended and MCE provide additional information to you or automation as desired.  Buy spare sensors and keep extra batteries on hand if you go wireless, heck I even bought a spare keypad.  I think most people grossly discount security.  CO, fire, and most criminals do not discriminate.  I don't understand how someone could spend hundreds of thousands of dollars, euros, yen.. what ever on a house and not protect it properly.   

7
Users / Re: LIFX lightbulb
« on: September 25, 2012, 10:34:06 pm »
ethernet is still with us…

-Thom

Yes but wireless has not been advancing with backwards compatibility in mind the way Ethernet has due to it's hub like nature.  There are wireless device from 10 years ago that you can't use on a modern AP with modern clients, well... not without sacrifices.  Plus there's been talks for years about digitalizing wireless communication. 

I wouldn't be surprised if before these bulbs die they either becomes uncontrollable or they limit your wifi upgrade options.  However, I'll cross that bridge when I get to it, they're still wicked cool.

8
Users / Re: Multiple Web Orbiters.
« on: September 24, 2012, 08:00:30 pm »
This is a blind folded shot in the dark, but those having this issue, did you create each orbiter as a child of the core?  

I had this problem a long time ago and it was because the obsessive organizer in me decided it would be a good idea to create all my generic orbiters under one generic web device.  Visually it looks better in the device tree, unfortunately it doesn't work.  The symptoms were exactly the same until it stopped working all together.

Also, unless I misunderstood what was said in the second post, some screens change on all orbiters for a given room.  So if you're watching a video in the family room all orbiters for the family room will show the remote screen.  You can change any single orbiter to a different screen without affecting the others after the fact, but at the start of the video all orbiters will go to the remote (I think this can be changed in the settings per orbiter.. I THINK).


Edit: This was misleading...(You can change only one orbiter to a different screen without affecting the others after the fact, but at the start of the video all orbiters will go to the remote (I think this can be changed in the settings per orbiter.. I THINK).)

9
That's actually good. Put the IP address and MAC address in the device's fields in web admin, reload, and try again while the player is on.

It's quite interesting, as now I did a port scan on that same IP and came up with the ports I reported earlier. I assume the player is off now. But that also means the network doesn't go off, but goes into some mode I haven't seen before. For both of the ports I mentioned, when I try an HTTP connection I get a UPnP-like envelope back with an error - that's how I know it's your blu-ray player and not something else.

Edit: I just realised that this didn't work last time either, which makes it really interesting. I'd like to look at the UPnP services on your player while it's on. What time will you be available at home?

When I port scan the unit when it's off I see no ports open. 

Code: [Select]
dcerouter_31461:~# nmap 192.168.80.159

Starting Nmap 5.21 ( http://nmap.org ) at 2012-09-13 15:32 EDT
Nmap scan report for 192.168.80.159
Host is up (0.0015s latency).
All 1000 scanned ports on 192.168.80.159 are closed
MAC Address: 54:53:ED:DA:51:00 (Unknown)

I was looking for a reason to leave work early tomorrow anyway... sooo, thank you!  I should be able to make it home by 11:00 Am my time I believe that's 4:00PM your time... correct?   does that work for you? How will we do this just turn the blu-ray on at 11:00AM, do you want me to email you, how do you want to coordinate this?

Thanks

10
Okay, I ran the script and the bluray player didn't show up until I turned it on.  It spit out extra information when I went to the registration part of the menu but it was completely gone once powered off.  If it helps the output is below.
Code: [Select]
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000003-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000000-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'
uuid:00000003-0000-1010-8000-5453edda5100::upnp:rootdevice
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000003-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'

I got the first two lines just after turning it on, and the second two by going to the registration menu (not the actual registration process, just selecting the menu).

I did a port scan with the player on and I see ports 50001 and 50002 open not 22222 and 54400.
Code: [Select]
Nmap scan report for 192.168.80.159
Host is up (0.00049s latency).
Not shown: 998 closed ports
PORT      STATE SERVICE
50001/tcp open  unknown
50002/tcp open  iiimsf
MAC Address: 54:53:ED:DA:51:00 (Unknown)

Maybe the codes are different for the unit you programmed with vs my unit.  Maybe it's a UK/US thing... I don't know just throwing it out there.  I checked the manuals and online for codes but came up dry.  I don't mind contacting tech support but can you tell me what exactly i'll be asking for?  I'm assuming the initial registration communications is different than control commands.  If there is another way let me know.  I don't mind being a test dummy if it turns out you need two or more device template to cover all the Sony's.

Okay, I have 2 problems.  I just got off the phone with Sony and It turns out that the player disconnects from the network when it is powered off.   From what they're saying there is no way to power it on using an IP signal (IR or power button only).  I'm sure it's a software thing and a firmware hack changing a 0 to a 1 would fix that but I wouldn't even know where to start. 

Second problem, and I didn't get a 100% answer on this one, but the rep was fairly certain that the IP/IR codes are different for the US version and other territories.  He warns that he is not overly familiar with the non US, or to be specific the UK models.  I only see one version of the media remote so I want to doubt that theory but since the NC can see the blue-ray (when it's on) and the expected ports are open I can't think of any other reason why this isn't working.   

11
I think ours (which mysteriously disappeared and got replaced with a Samsung unit that I haven't written code for yet) was a off the shelf unit from Tesco or something, so nothing special about it. The discovery protocol is UPnP on that unit, and on everything that the app can control, so I'm intrigued that it doesn't reply to my UPnP searches.

Just to check the theory that it might not show up unless you put it in registration mode - our unit was always showing - there's a script I put on your system (in the root account) that does a UPnP search and shows the devices found, then sits there monitoring the UPnP trafic. You can run it like so: python UPnP_test.py and you can close it with Control+C. Please run that after you put your player in registration mode and see if it shows up. You can run it before you do that too, so you can see what the output looks like and have something to compare with.

Okay, I ran the script and the bluray player didn't show up until I turned it on.  It spit out extra information when I went to the registration part of the menu but it was completely gone once powered off.  If it helps the output is below.
Code: [Select]
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000003-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000000-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'
uuid:00000003-0000-1010-8000-5453edda5100::upnp:rootdevice
Device: rootdevice u'Blu-ray Disc Player' 'uuid:00000003-0000-1010-8000-5453edda5100' 'upnp:rootdevice' '192.168.80.159', manifestation 'remote'

I got the first two lines just after turning it on, and the second two by going to the registration menu (not the actual registration process, just selecting the menu).

I did a port scan with the player on and I see ports 50001 and 50002 open not 22222 and 54400.
Code: [Select]
Nmap scan report for 192.168.80.159
Host is up (0.00049s latency).
Not shown: 998 closed ports
PORT      STATE SERVICE
50001/tcp open  unknown
50002/tcp open  iiimsf
MAC Address: 54:53:ED:DA:51:00 (Unknown)

Maybe the codes are different for the unit you programmed with vs my unit.  Maybe it's a UK/US thing... I don't know just throwing it out there.  I checked the manuals and online for codes but came up dry.  I don't mind contacting tech support but can you tell me what exactly i'll be asking for?  I'm assuming the initial registration communications is different than control commands.  If there is another way let me know.  I don't mind being a test dummy if it turns out you need two or more device template to cover all the Sony's.

12
I think ours (which mysteriously disappeared and got replaced with a Samsung unit that I haven't written code for yet) was a off the shelf unit from Tesco or something, so nothing special about it. The discovery protocol is UPnP on that unit, and on everything that the app can control, so I'm intrigued that it doesn't reply to my UPnP searches.

Just to check the theory that it might not show up unless you put it in registration mode - our unit was always showing - there's a script I put on your system (in the root account) that does a UPnP search and shows the devices found, then sits there monitoring the UPnP trafic. You can run it like so: python UPnP_test.py and you can close it with Control+C. Please run that after you put your player in registration mode and see if it shows up. You can run it before you do that too, so you can see what the output looks like and have something to compare with.

Okay, I can see the script.  I'll run it when I get home from work.

Thanks again!!

13
It's the "Sony BluRay LivingRoom" (device 69), right? Its IP Address and MAC Address fields are empty. I found a device that says it's a Sony Blu-ray player, IP 80.159, but I had to scan its ports to find out what it is (ports open: 22222, 54400). Problem is the script expects ports 50001 and 50002. Also, I did a UPnP scan and the Blu-ray drive didn't show itself. This is not OK, because our Sony devices use UPnP as the transport protocol for control. I tried poking it with various sticks, but no luck. What model is it? Do you have a device that can run the Sony Media Remote app (iPhone, iPad, iPod touch, Android phone, that kind of stuff) to confirm that it can actually talk to your player? This app used UPnP to talk to Sony devices as well...

Yup, that's the one Sony BluRay LivingRoom (I know, I should name it better than that). 

I tried it with the IP and mac fields populated at first but after I couldn't get it working it hit me that the Sony android app never asked for the IP address of the player,  I assumed that meant the app was broadcasting a message (UDP) and waiting for a response (or vice versa) to trigger the registration process. so I removed the IP and mac data in hopes that Dianemo was doing the same thing.

It's probably not responding to UPnP because it's not in registration mode or because it's off.  I'm using the android media remote and I've noticed that all functions work but I can not turn the unit on VIA the Sony media remote.  There were no problems registering the Sony media remote.  It could be a setting on the unit or the app but I haven't seen any thing that looks like it would enable or disable that.

The model number is BDP-S390/BM U2.

This isn't a high end unit, maybe that's the problem?

14
Users / Re: Dianemo S: Strange Behaviour with ID3 files
« on: September 12, 2012, 04:39:25 am »
I've got the same problem.  This is eventually going to become a big problem.



That screen shot doesn't include the actual media files!!

15
Weird. Unfortunately, that log is just the Whisperer, as I didn't add any logs to the communication itself, so it doesn't help. Can I get access to your machine and have a look at what's going on?

Sure, I just turned on remote assistance.  Thanks uplink!

Pages: [1] 2 3 ... 14