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

Pages: [1] 2 3 ... 110
1
Can you pastebin the output of the following on your 1204 core:
Code: [Select]
apt-cache policy lmce-md-metaJ.

2
New lmce packages were pushed to our repo, no idea why you wouldn't be seeing them off the top of my head.

Sent from my Nexus 5 using Tapatalk


3
Users / Re: 'Diskless' Raspberry Pis are out in the wild!
« on: December 02, 2016, 03:18:09 pm »
No need to be sorry, very glad that things are working!

J.

4
Installation issues / Re: Mythtv Setup issues
« on: December 01, 2016, 02:13:44 pm »
HDHomeRun units have been very successful for many people.  They are supported in MythTV quite easily if I remember correctly.

5
Feature requests & roadmap / Re: Alexa and amazon echo skill
« on: December 01, 2016, 02:11:21 pm »
Just a note, an OAuth2 server was just added to LMCE for initial integration and testing.  It'd be great if you could now shift to using the provided server and ensure it is functioning properly.  This server will be used for multiple cloud service authentications so needs to remain generic. 

Keep on playing and having fun!

6
Thanks again for the feedback!  The issue is actually the addition of a package that is in the Ubuntu backports repo which was not included in the diskless script.  Hopefully the fix will hit the repo today.  Have fun and thanks again for reporting!

Sent from my Nexus 5 using Tapatalk


7
An update will be out in a day or two that should fix the issue you are having.  Thanks for reporting it!

J.

8
I'll try to recreate your issue.

Sent from my Nexus 5 using Tapatalk


9
Users / Re: weather segfault
« on: November 22, 2016, 09:51:42 pm »
So two things.  First, WWO appears to no longer support a free api.  Second, OWM is segfaulting because it is trying to parse data that does not exist.  It is also not using the data that is provided to it, it appears to be hardcoded with a specific API key.  OWM needs a specific City ID (from a database at OWM) and does not work with city names.  Currently it always returns results for Orlando, Florida only, perhaps hard-coded but I'm not really sure here.

The long and short is that you will have to dig into the code to fix these issues if you want to make use of the weather interface.

J.

10
Users / Re: Important upgrades to sqlCVS coming soon.
« on: November 22, 2016, 08:53:55 pm »
The upgrades were all performed over this past weekend, everything seems to have gone smoothly.  Everyone running 1204 and 1404 should run:
Code: [Select]
apt-get update
apt-get dist-upgrade
This will ensure your database is upgraded and compatible with LMCE's database schema going forward.

Thanks,
J.

11
Users / Re: pluto-dcerouter
« on: November 14, 2016, 04:39:28 am »
Hi guys
I have an offline system, to upgrade I run apt - get on another system managed by a configuration  file
I recently updated the packages however pluto-dcerouter fails to install after it tries to connect to the internet (that isn't there) to update "GetIRCodes.php"
Is there a way to install the package without it connecting to the internet?
Is there an offline version I can use instead?
Manually download the ir codes?
Mat
nope.  An internet connection is required, that's always been the case. 
J.

Sent from my Nexus 5 using Tapatalk


12
Users / Re: ip secuirty camera
« on: November 10, 2016, 04:05:59 pm »
Ah, I see.

13
Users / Re: ip secuirty camera
« on: November 09, 2016, 09:32:09 pm »
Sorry, I'm not actually aware of the acronym...  I've never used an ip camera so I was confused. 

Sent from my Nexus 5 using Tapatalk


14
Users / Re: ip secuirty camera
« on: November 09, 2016, 05:44:11 pm »
I'm not even sure how RSTP works with an IP camera.  It doesn't even sound related.

Code: [Select]
Rapid Spanning Tree Protocol
In 2001, the IEEE introduced Rapid Spanning Tree Protocol (RSTP) as 802.1w. RSTP provides significantly faster spanning tree convergence after a topology change, introducing new convergence behaviors and bridge port roles to do this. RSTP was designed to be backwards-compatible with standard STP.

While STP can take 30 to 50 seconds to respond to a topology change, RSTP is typically able to respond to changes within 3 × Hello times (default: 3 times 2 seconds) or within a few milliseconds of a physical link failure. The Hello time is an important and configurable time interval that is used by RSTP for several purposes; its default value is 2 seconds.

Standard IEEE 802.1D-2004 incorporates RSTP and obsoletes the original STP standard.

15
Users / Important upgrades to sqlCVS coming soon.
« on: November 04, 2016, 07:32:04 pm »
Hi everyone,

This is mostly a heads-up notice that a pretty major back-end change will be coming soon.  There is a big change coming to the way that sqlCVS checks for changed records and compares records for importing into LinuxMCE's databases.

The background is fairly simple: MySQL 5.6 has changed the way that datetime fields and timestamp fields can be stored.  sqlCVS has always used a datetime of '0' to store records that have not been locally altered.  Two days before the release of Ubuntu Xenial 16.04 Canonical upgraded the mysql-server version they were to ship.  The new version no longer permits storage of '0' dates.  This has meant that some serious testing has been performed so that datetimes are properly converted to the new permissible format. sqlCVS must also continue to function properly from both the server and client sides.  All existing supported LinuxMCE systems (1204, 1404) and new systems (1604) must also seamlessly upgrade and continue to function as if nothing had changed.  During this update all tables (both server and client side) will be updated to store datetimes as NULL rather than '0' for unaltered records.

All tables and text fields will be updated to UTF8 on the schema server and LinuxMCE clients.  At the moment tables are converted to UTF8 after installation (the exception is tables in pluto_main which are already UTF8 on the server).  Converting the other server side tables will ensure that data is preserved and stored properly when sent to the schema server from clients.

I have done extensive testing on upgrading existing installs and new installations of 1204, 1404 & 1604.  Without these changes we have been unable to successfully install and run 1604 systems.  Once these changes have been applied we hope to release the first of our working 1604 builds for install and use.

On top of sqlCVS the next set of 1404 DVDs that are produced will be upgraded to the xenial Ubuntu Hardware Enablement Stack which means that new 1404 DVD installs should recognize all the same newer hardware that xenial can.  The Hardware Enablement Stack brings updated kernel and X.Org packages into trusty to support that newer hardware.  A new 1204 DVD will be produced but there will be no changes to it's Hardware Enablement Stack (the xenial stack is not available for precise).

Lots of other bugs are lurking and we're always looking for people that are willing to help out with other aspects.  Remember Rule #1 always.

Happy LMCEing!

J.

Pages: [1] 2 3 ... 110