diff --git a/setup.cfg b/setup.cfg
index 79bc678..f645233 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -2,4 +2,4 @@
 # This flag says that the code is written to work on both Python 2 and Python
 # 3. If at all possible, it is good practice to do this. If you cannot, you
 # will need to generate wheels for each Python version that you support.
-universal=1
+#universal=1
diff --git a/setup.py b/setup.py
index 0d73d55..76c635b 100644
--- a/setup.py
+++ b/setup.py
@@ -25,7 +25,7 @@
     # https://packaging.python.org/en/latest/single_source_version.html
     version='0.1.0',
 
-    description='Automation Library for Yamaha receivers that support the YNCA protocol.',
+    description='Automation control library for Yamaha receivers that support the YNCA protocol.',
     long_description=long_description,
 
     # The project's main homepage.
@@ -44,7 +44,7 @@
         #   3 - Alpha
         #   4 - Beta
         #   5 - Production/Stable
-        'Development Status :: 4 - Beta',
+        'Development Status :: 3 - Alpha',
 
         # Indicate who your project is intended for
         'Intended Audience :: Developers',
@@ -77,16 +77,16 @@
     # your project is installed. For an analysis of "install_requires" vs pip's
     # requirements files see:
     # https://packaging.python.org/en/latest/requirements.html
-    install_requires=['pyserial'],
+    install_requires=['pyserial>=3'],
 
     # List additional groups of dependencies here (e.g. development
     # dependencies). You can install these using the following syntax,
     # for example:
     # $ pip install -e .[dev,test]
-    extras_require={
-        'dev': ['check-manifest'],
-        'test': ['coverage'],
-    },
+    #extras_require={
+    #    'dev': ['check-manifest'],
+    #    'test': ['coverage'],
+    #},
 
     # If there are data files included in your packages that need to be
     # installed, specify them here.  If using Python 2.6 or less, then these
@@ -104,9 +104,9 @@
     # To provide executable scripts, use entry points in preference to the
     # "scripts" keyword. Entry points provide cross-platform support and allow
     # pip to create the appropriate form of executable for the target platform.
-    entry_points={
-        'console_scripts': [
-            'ynca=ynca:main',
-        ],
-    },
+    #entry_points={
+    #    'console_scripts': [
+    #        'ynca=ynca:main',
+    #    ],
+    #},
 )