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

Pages: [1] 2 3
1
Feature requests & roadmap / Re: Alexa and amazon echo skill
« on: November 29, 2016, 11:44:57 am »
Hi all,

Sorry this has taken me a while to get going but it is still on my radar, I've got an oauth2 server running now on my core and looks to be working fine and issuing out tokens and all that nice stuff. I've brought a cheap domain name in the black friday sales and linked that into my core and installed an SSL certificate as well which is also working fine however after 2 days of pulling my hair out trying to get amazon to accept and link my skill to my core it seems that amazon are extremely picky on what SSL certs they will accept from what i can see it has to come from either, digicert, versign, twane or one of the other over overpriced big players you cant use just any old cheap certificate that you can get nowadays I got mine from godaddy but i tried a trial for geotrust as well and that also wouldn't work.

To verify that it was a certificate issue I copied my code over from my core on to one of the web servers at my work which has an enhanced certificate from digicert and it linked fine so this leads me to a problem either we all have to buy a £250+ a year SSL certificate and link an amazon skill to each of our cores so that there is no concern in security or the other option I'm looking at is develop a web interface on a server with an expensive certificate and then use this as a middle man to receive the commands from amazon or any other similar service link them to a user in a DB which has that persons core IP address or domain name and then route the command to there core.

To keep this as secure as possible ill still use Oauth2 on the core to link to this intermediate site but be a little more lenient on the certificate type allowing like a selfsigned one the good thing about this as well will be that the skill I produce should be allowed to be published publicly as its linking to a single secured service and although there will be concerns maybe with a third party site holding core details by using oauth2 a user can revoke access at any point.

To test this approach I'm making the intermediate site on a server i have access to at work where I'm currently building an internal web application, This will be fine to test but it cant obviously stay there for all to connect to I cant see my manager being to impressed but if I can get this working and others find it useful then perhaps we can group fund a certificate for the linuxmce.org domain and move the page built over to this server I think people would full more secure that way as well.

But anyway just thought id give an update and let people know its not been forgotten about.

Cheers

2
Feature requests & roadmap / Re: Alexa and amazon echo skill
« on: November 02, 2016, 09:42:25 am »
Ok so after some more digging to secure our API we need to use something like OAuth2 and in fact to use it with alexa you can only use OAuth2. There are a number of ways of doing this as I'm quite fluent in php id probably prefer to go down that route. I haven't used cakePHP before but I've heard of it and ill gladly take a look especially if it simplifies the DB connections, I'm still getting my head round the changes in the depreciated mysql php functions which I've become accustomed to for years :).

There is a nice example and demo of implementing an OAuth2 server over on this site: https://bshaffer.github.io/oauth2-server-php-docs/ I don't think it would be to much work to implement this on to the core.

In terms of security I believe keys are stored encrypted anyway so a person with access to the Linuxmce DB wouldnt get simple access to peoples accounts but if it really is an issue I guess a new schema just for this could be created with a password or something? But this is about giving an application like Alexa access to LinuxMCE not google giving LinuxMCE access to google if that makes sense.

Another option would be to implement a framework like this: https://apigility.org designed to help create api's and offers a few different security options for securing them, this would give better flexibility and future proof with regular updates but there are obviously disadvantages as well relying on yet another 3rd party piece of software.

Im confident i can implement any one of these on to the core to secure our apis the next stage would then i guess be what do we want our api to look like what commands would we send and what would our structured responses look like to give the best usability and flexibility with multiple services?

Ill continue digging and see if i can implement something on my core here just as a test and come back to you all. Cheers for the help and advice as well, I will be back I'm sure  ;)

3
Feature requests & roadmap / Re: Alexa and amazon echo skill
« on: October 27, 2016, 11:19:48 am »
Im still playing around with this, from a lot of reading up on the amazon developer site i think I've now created a basic skill that I can enable and send and receive requests from but the responses are NULL as I haven't actually done any linking to linuxmce yet thats the next step.

Did i see once on this forum that someone had created a JSON dcedevice before? I don't seem to be able to find it or any documentation on the api for it, just thought it might be an easy way to plug in.

Otherwise ill probably need to create my own scripts, but unfortunately my only coding skills are in php, javascript and html so id probably write an interface in php using a connection to the mysql db to get the details of controllable devices and there device ids etc and then use the same script to fire off exec commands to send the required dcemessages as they are received from amazon.

Obviously i need to add in a secure connection between the core and the amazon web service as well.

Does this seem the right approach or at last a workable approach?

4
Feature requests & roadmap / Re: Alexa and amazon echo skill
« on: October 24, 2016, 10:58:58 am »
Hey sorry for the delay had a few family issues, my echo arrived yesterday though so really keen to have a go at setting this up, my skill set is in web design really so I'm sure i could help at least with the http interface and designing of the api. my main struggle would probably be with the actual connecting up to the dcerouter, how to announce available devices ect.

You mentioned you found some nice code from google that would handle this don't suppose you could send a link  and ill see if I can get this intergraded as a starting point maybe?

cheers

5
Feature requests & roadmap / Alexa and amazon echo skill
« on: October 14, 2016, 05:37:36 pm »
Hi all,

The amazon echo has final made it way to the UK and I'm excited to get my hands on one, just wondering if anyone had looked in to adding a Linuxmce skill to control basic home automation like lights and heating ect, it seems like someone has created a skill for our slightly common sister vera but it annoyingly connects via there in house web interface so even though the code has familiar terminology like Device Ids ect it just wont simply port over.

the amazon alexa system looks simple enough at creating a skill using node.js the issue i have is just trying to think of the best way of implementing a secure external api type interface so that the external amazon alexa voice service can send and receive commands to our internal DCErouter.

Just thought id put it out there and see if anyone had looked into this or had any ideas of the best way of implementing a solution.

cheers

6
Users / Re: Joggler setup lmce-disked-mid-joggler
« on: October 30, 2015, 01:36:23 pm »
Hi Phenigma,

sorry it took so long but I'm all setup now and I've created a ticket for this issue #2517

cheers again

7
Users / Re: Joggler setup lmce-disked-mid-joggler
« on: October 20, 2015, 04:09:48 pm »
Thanks for getting back to us,

I know the whole joggler MAC address thing is crazy I have no idea what O2's motive was when they made it duplicate the wifi adapter address and leave the network cards mac address blank, seems a bit crazy to me.

But anyway thanks for looking into it I even tried with another joggler that I flashed the eeprom on the network card with a real mac address previously and it has the same issue so its creating a fake address ok its just not saving it for the next boot.

I'm really sorry I've tried to create a ticket for this but I don't seem to have a log in for trac that or Im going mad and just cant log on :-[

8
Users / Re: Joggler setup lmce-disked-mid-joggler
« on: October 18, 2015, 02:56:31 pm »
Thanks you so much for the quick and detailed reply.

I've noticed all the work you've put in over the last few months the install process seems to be far easier now which is a great help as I had to reinstall my core last week.

Unfortunately this jogger booting still isn't working, it's a shame as I got really excited when I saw the wiki updated to allow a full stack to be installed something I've tried to do manually before but with a lot of effort.

I can always use the old manual orbiter instructions so please don't put to much work in to this I'm sure it will fix itself down the line when you get to it but to help with debugging I'll try and walk trough the issue now.

So your recommendation to change the source worked a treat and I had no dependancy issues installing the packages this time. The steps I took were flash a usb stick with squeeze os 303-trusty, then first I tried using wifi so I set this up in squeeze os, then rebooted and ssh to the joggler so I knew the networking was all set up fine, I then changed the source, updated and then installed the lmce-disked-mid-joggler package all went through fine and rebooted.

It then just hang on the squeeze os splash but by pressing esc I could see there was an error mounting so I skipped through these errors and got to the announced ourselves to the router message but looking at the string sent to the core the IP address was just that of an internal address so obviously the wifi connection hadn't connected so then I tried the above again but this time I used an Ethernet connection to set up squeezeos then installed the lmce-disked-mid-joggler package again with no errors and rebooted. This time the mounts still failed so I pressed s to skip through them again and got to the announced ourselves to the router message. The string that was sent to the core then had an IP address and my other orbiters then show a message about a joggler being discovered. I select the room the joggler is in and the joggler then runs some scripts and reboots.

Now though I again get it hanging at the splash screen due to mount errors so I skip through them and it goes back to the announced ourselves to the router message and another joggler gets added to the system and this goes in a loop, looking at the string sent to the core the MAC address is randomising each item and not holding like it should.

This is strange though as it worked fine in squeeze os, so any ideas would be greatful.

Many thanks again for everything

9
Users / Joggler setup lmce-disked-mid-joggler
« on: October 16, 2015, 08:45:01 pm »
Im having a few issues setting up a new joggler.
 I noticed the wiki has changed stating that a full stack can be installed with the following package: lmce-disked-mid-joggler but I get a dependancy error when I try to install this package on the latest squeezeos image of trusty.

I traced the dependancy issue to a Deb called lmce-core-locator so I checked the Deb.linuxmce.org source and found this package missing in the trusty image but I did see it in the precise image so I manually installed it from there instead.

The whole lmce-disked-mid-joggler Deb seemed to then install fine but when I try to boot the joggler it hangs at the squeeze is splash.
If I press esc it shows mounting errors but if I press S multiple times to skip this I eventually get to the announced ourselves to the router message but nothing seems to happen from there.

I can't see any new devices created in my core and the joggler will just sit there for hours.

Does anyone know of a fix for this? I'm currently running 12.04 on my core but the joggler is 14.04 not sure if this could be the issue.

Any help would be greatful cheers.

10
Installation issues / Re: Dependancy issues running Diskless_CreateTBZ.sh
« on: January 11, 2015, 10:47:36 am »
Hi Phenigma,

I tested rebuilding the image & it now works perfectly.

Thank you so much for your help, you've done loads to improve the system lately as well & it's much appreciated especially all the work on the rpi.

Thank you

11
Installation issues / Re: Dependancy issues running Diskless_CreateTBZ.sh
« on: January 09, 2015, 12:06:41 am »
Hi Phenigma,

Thank for your help, sorry should have probably given a bit more detail.
I'm attempting to create the rpi image I had this working great with your hdmi cec adapter for the pi working as well which I love by the way.
But randomly yesterday the cec control stopped working so I attempted to rebuild the image but still no success so then I apt-get updated the core & re-ran Create_DisklessTBZ.sh but then started to get these errors.

Here is the log file (sorry it's so large I left it trying for about an hour)
http://paste.ubuntu.com/9695235/

And here is the Create_DisklessTBZ.sh script - note I commented out the deb cache in case I had a funny package in there if your wondering why that's like that.
http://paste.ubuntu.com/9695246/

Also I noticed I can get it to run successfully if I comment out line 550 but then when I boot the pi & it sets up I end up with just a command prompt I guess as no device packages have been installed.

Really hope you can help the biggest annoyance is I think the htmi cec issues I was have was just down to the cable now in the end so all this was a bit pointless but I hope it can be brought back to life if not I guess I'll have to just reinstall the core.

Many thanks again for any help you can give.

12
Installation issues / Dependancy issues running Diskless_CreateTBZ.sh
« on: January 07, 2015, 10:50:07 pm »
Hi all I'm trying to re-run Diskless_CreateTBZ.sh as i had some issues with my rpi image and rebuilding it didn't seem to help but now i keep getting the following dependancy issues over and over. does anyone have any ideas what the issue could be.

I'm currently running 12.04 if thats of help.

Cheers guys

Code: [Select]
Wed Jan  7 21:37:44 GMT 2015 - #### Package pluto-orbiter failed (/opt/Diskless_CreateTBZ.DVMafPyAN) - We wait 10sec and try again - to stop retrying press Ctrl-C. 
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
8 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up pluto-storage-devices (2.0.0.46.14122429893) ...
Can't locate Crypt/SmbHash.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.14.2 /usr/local/share/perl/5.14.2 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.14 /usr/share/perl/5.14 /usr/local/lib/site_perl .) at /usr/pluto/bin/smbpass.pl line 3.
BEGIN failed--compilation aborted at /usr/pluto/bin/smbpass.pl line 3.
dpkg: error processing pluto-storage-devices (--configure):
 subprocess installed post-installation script returned error exit status 2
dpkg: dependency problems prevent configuration of pluto-boot-scripts:
 pluto-boot-scripts depends on pluto-storage-devices (>= 2.0.0.46); however:
  Package pluto-storage-devices is not configured yet.
 pluto-boot-scripts depends on pluto-storage-devices (<< 2.0.0.47); however:
  Package pluto-storage-devices is not configured yet.

dpkg: error processing pluto-boot-scripts (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-dcecommon:
 pluto-dcecommon depends on pluto-boot-scripts (>= 2.0.0.46); however:
  Package pluto-boot-scripts is not configured yet.
 pluto-dcecommon depends on pluto-boot-scripts (<< 2.0.0.47); however:
  Package pluto-boot-scripts is not configured yet.

dpkg: error processing pluto-dcecommon (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-confirm-dependencies:
 pluto-confirm-dependencies depends on pluto-boot-scripts (>= 2.0.0.46); however:
  Package pluto-boot-scripts is not configured yet.
 pluto-confirm-dependencies depends on pluto-boot-scripts (<< 2.0.0.47); however:
  Package pluto-boot-scripts is not configured yet.

dpkg: error processing pluto-confirm-dependencies (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-orbiter:
 pluto-orbiter depends on pluto-boot-scripts (>= 2.0.0.46); however:
  Package pluto-boot-scripts is not configured yet.
 pluto-orbiter depends on pluto-boot-scripts (<< 2.0.0.47); however:
  Package pluto-boot-scripts is not configured yet.
 pluto-orbiter depends on pluto-confirm-dependencies (>= 2.0.0.46); however:
  Package pluto-confirm-dependencies is not configured yet.
 pluto-orbiter depends on pluto-confirm-dependencies (<< 2.0.0.47); however:
  Package pluto-confirm-dependencies is not configured yet.
 pluto-orbiter depends on pluto-dcecommon (>= 2.0.0.46); however:
  Package pluto-dcecommon is not configured yet.
 pluto-orbiter depends on pluto-dcecommon (<< 2.0.0.47); however:
  Package pluto-dcecommon is not configured yet.

dpkg: error processing pluto-orbiter (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-test-serial-port:
 pluto-test-serial-port depends on pluto-dcecommon (>= 2.0.0.46); however:
  Package pluto-dcecommon is not configured yet.
 pluto-test-serial-port depends on pluto-dcecommon (<< 2.0.0.47); however:
  Package pluto-dcecommon is not configured yet.

dpkg: error processing pluto-test-serial-port (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-hald:
 pluto-hald depends on pluto-dcecommon (>= 2.0.0.46); however:
  Package pluto-dcecommon is not configured yet.
 pluto-hald depends on pluto-dcecommon (<< 2.0.0.47); however:
  Package pluto-dcecommon is not configured yet.

dpkg: error processing pluto-hald (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pluto-createdevice:
 pluto-createdevice depends on pluto-boot-scripts (>= 2.0.0.46); however:
  Package pluto-boot-scripts is not configured yet.
 pluto-createdevice depends on pluto-boot-scripts (<< 2.0.0.47); however:
  Package pluto-boot-scripts is not configured yet.

dpkg: error processing pluto-createdevice (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 pluto-storage-devices
 pluto-boot-scripts
 pluto-dcecommon
 pluto-confirm-dependencies
 pluto-orbiter
 pluto-test-serial-port
 pluto-hald
 pluto-createdevice
E: Sub-process /usr/bin/dpkg returned an error code (1)

13
Users / Re: Raspberry Pi Model A+ Experiences
« on: November 25, 2014, 08:48:34 am »
I haven't got a model A yet but I was tempted to get one to see if it could run as a simple orbiter combined with the small adafruit touchscreen and placed in a wall box to control lights, set alarm status etc.

Not sure if the 256mb ram would run orbiter though but a web interface may work, I know this could be done with the model b but this a+ is quite a bit smaller now and more importantly in-wall its not as tall.

Just my ideas there so cheep you can afford to experiment:)

14
Developers / Re: O2 Joggler As full MD - Testing needed
« on: August 15, 2014, 02:59:09 pm »
Thanks Coley,

Sorry for the delays Ive just recently had a baby so thats taken most of my time at the moment.

I have tried to do it under chroot but I end up with a few errors as I need to download the kernel source patch it and then compile it and finally install it but it doesn't seem like it likes compiling over a chroot environment, I dont really know where next to go I would be so grateful if someone with more Linux knowledge could help, So if you have a joggler that you wouldn't mind sparing and fancy a challenge the guide to getting to where I am now is as so:

1 - Download the Joggler reflashing tool and updated openpeak firmware from this site:
http://birdslikewires.co.uk
2 - Follow instructions on the site to install the updated openpeak firmware.
3 - After doing this you are left with a Joggler that is up to date and that you can easily SSH to.
4 - Download the following rom files from here http://www.tardistracker.com/roms.zip  unzip and add to a newly formated FAT32 usb stick, there are 2 folders in this zip file one is a backup of the normal EFI boot rom the other is the new coreboot rom, copy the .rom file out of the coreboot folder and place on the root of the usb stick.
5 - Now place the usb stick into the Joggler and reboot.
6 - Check the DHCP address on the Joggler and SSH to the Joggler; username is joggler and password is joggler
7 - Now issue the following commands:

# cd /mnt
This will enter the USB stick
# ls
This will list the files on the stick and should show this:
 coreboot.rom
Now the next two lines will flash the boot rom:
# modprobe fh
# dd if=/mnt/coreboot.rom of=/dev/fh count=1 bs=1024k
Now finally reboot:
# reboot

after reboot you should now see a different boot splash with an icon of a shark, this is now your bios.

8. now we need to flash our EEPROM so we need a tool to do that and we need DOS to run it so first download a usb bootable freedos imaged from here: http://ftp.chtaube.eu/pub/FreeDOS/bootable-usb/FreeDOS-1.1-memstick-2-256M.img.bz2 and thne download the realtek EEPROM flash tool from here: http://www.biosrepair.com/bios/PG8168.rar.

9. now dd over the dos image to a memory stick (must be at least 256mb).

10. now mount your memory stick and extract the EEprom programing tool to the stick so you can access it once freedos is booted on the joggler.

11. browse to the extracted EEprom programming tool directory on the memory stick and find 3 .cfg files named like this "8168.CFG" each one is for a different version of the  network card to be safe I edited all of them so open each one in a text editor and then at the top of the file find the line "node id=" and edit this to whatever mac address you want, I would recommend just offsetting the last few digits and then save each amended .cfg file.
 
12. now attach a small usb hub to the usb port of your joggler and attached a keyboard and the memory stick you have just been using and apply power.

13. follow the options on screen to boot yourself in to freeDOS and browse to the EEprom programming tool folder.

14. now type the following and press enter to flash "PG8169 / W".

15. now type PG8169 / R to read the network card and check all is written correctly.

16. now power down the joggler.

17 - Go to www.rom-o-matic.com and create a usb based PXE image and flash to a usb stick.
18 - Place usb stick into the joggler and connect a network cable between the joggler and your internal LMCE network.
19 - power on the joggler and you should boot in to iPXE which will configure the network card and then TFTP from the core using your new mac address.

20. that should be it you should shortly see the announced ourselves to the router messaged and the Media Director should start to be created, once done your get a message saying rebooting but the joggler wont reboot just pull the power and turn it on again, you should now boot in to LMCE.

21. your now as far as me you should after a bit of loading be presented with errors relating to the graphics drivers this is where I need your help.

if you want to read more on the EEprom flashing tool use google to translate teh following site: http://www.biosrepair.com/bios/pg8168.htm.

Hope someone can follow this and possibly offer some assistance, Many thanks.

15
Developers / Re: O2 Joggler As full MD - Testing needed
« on: July 22, 2014, 03:45:22 pm »
Hi,

Just to update you all,

I have made some progress with PXE booting the joggler. I found a program to reflashing the blank EEPROM of the jogglers network card and have now set a real mac address.

I will give further detail for you all to follow shortly but I can now using the instructions already posted for adding a bios and using an iPXE image to boot get to the announcing ourselves to the router, creating the media director and then boot the initial Kernel and then the full media director kernel that starts loading the beginnings of LinuxMCE.

However I then halt on errors regarding the gma500 having no valid LVDS backlight data, I believe this is to do with the intel graphics driver, there are also a number of patches available for the joggler to solve other issues such as this but for a different kernel version but as Ubuntu 12.04 is already available as an image to download these are freely available but I cant boot enough to install a different kernel or any of the patches, as soon as ssh comes up the error above halts the system in a few seconds after.

Is there a setting I can add to the boot line that will take me to just a very basic recovery console so I may install patches and graphics drivers?

Many thanks as always   

Pages: [1] 2 3