Tuicemen.com

Advanced search  

News:

Alex10  (Build 1.5.3.4 ) is now  available for download ~:0~

Pages: [1] 2 3 ... 10
 1 
 on: Today at 08:08:32 am 
Started by Tuicemen - Last post by brobin
In my house we have 2 Echos and 2 dots. One of each is registered to my Amazon account and the others to my wife's Amazon account. All four are on the same network in the house.  After setting up Alex10 I asked each unit to discover devices and, to my delight, all the units did so even though there are two different Amazon accounts. All the units also discovered the Honeywell T-stats and the Lutron scenes as well.  ~:0~

 2 
 on: Today at 06:41:51 am 
Started by Tuicemen - Last post by Tuicemen
Update:
I brought a second dot to the cottage and set it up with a different account hoping this would solve my issue with it not seeing my X10 setup.
With this new dot setup and discovering my X10 devices I gave the old Dot (with other account)a second go.
Success  `:) ~:0~  it is seeing my devices here and although it doesn't see the devices at the city (when asked to discover devices) it will control them.
The fact that two accounts aren't required is good news.

I found two Dots aren't needed here,  as Alexa can hear me from anywhere on the main floor or the loft.
In the city extra Dots are required, although it is a smaller place it isn't a open concept design.

 3 
 on: Today at 04:41:58 am 
Started by Tuicemen - Last post by Tuicemen
Version 4.5.1 of the bridge is available from GitHub.
I haven't included this in the installers yet however if your having issues with viewing the Bridge UI in your browser you may wish to download it and give it a go.
This adds no new features to Alex10 nor the possibility of any to Alex10.

Note: You will need to rename it to ha-bridge.jar, stop the currently running bridge & alex10, place it in the Alex10 folder before restarting the bridge.
Also note, Alex10 will report a new bridge is available with this running. Do not click to install as it will install the old 4.5.0 which is currently with Alex10.

 4 
 on: Today at 04:21:19 am 
Started by mldenison - Last post by Tuicemen
Glad to hear your happy once more.
There are a few tweaks to any setup which can be helpful.
Manually entering settings is always best however some are intimidated by it.
Auto detection and assigning settings isn't always fool proof as all routers and PCs behave differently.
 (Chr)

 5 
 on: May 28, 2017, 05:10:00 am 
Started by mldenison - Last post by mgtr
I went through the steps to change the ip to static.  It was about as though I was using a recipe to make a dish I never heard of.  I am not sure what I did, or why I did it, but by golly, now it works as it did before.  I have no plans to look behind the curtain to find the Wizard.  I am happy now, and will leave well enough alone!
Now, on to the Harmony hub!  Thanks again for all the help.

 6 
 on: May 28, 2017, 03:37:31 am 
Started by mldenison - Last post by Tuicemen
The issue most likely was you didn't have your PC set to a static IP.
When the router rebooted your PC was given a different IP
Alex10 is still trying to use that IP and so was the Bridge.
Be sure the IP in Alex10 is the same as what you set in the bridge.
To help avoid this in the future set your PC to use a static IP.
https://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/

 7 
 on: May 27, 2017, 02:57:28 pm 
Started by mldenison - Last post by mgtr
OK, I need to modify the above.  I switched to ipconfig to find my ip, and then put that into the bridge.  When I told Alexa to discover devices, Alexa said that she found them all, but they were not listed in the Alex10 control panel.  When I tried to use Alexa to change the state of a device, it didn't work. 
So, I am close to having the problem solved, but no banana yet.  Help!

 8 
 on: May 27, 2017, 11:19:39 am 
Started by mldenison - Last post by mgtr
A month ago, everything was hunky-dory.  Alexa worked with Alex10 to turn things on and off.  Then we left town for a month, and now the above statements are untrue.  I can run the bridge from Chrome and turn things on and off, but Alex10 shows no devices, and discovery on Alexa also yields no devices.  I have changed the inbound permissions for Java (that was the last puzzle piece a month ago) and they are still changed. 
I read with interest the whole series of posts on Alexa hates Alex10, and figured that was my problem.  So, I changed the IP on the bridge control panel, and saved the result.  (To get the IP, I just typed IP into my browser and it returned an IP-looking number).  Still nothing on Alex10 control panel.
I know, the moral is don't go away for a month, but I cannot undo that.  What do I try next?

 9 
 on: May 27, 2017, 09:27:53 am 
Started by mldenison - Last post by brobin
Is the lamp that's plugged into the appliance module a CFL or LED bulb? If so, those can generate noise that prevents the module from hearing the OFF command. When the bulb is off it doesn't generate noise so the ON command is received in the clear.  To test for this condition try using an incandescent bulb or some other appliance, like a fan. However, if you're using a LAMP module rather than an Appliance module don't test with anything but an incandescent bulb that is at least 40 watts.
 I recently had a similar problem with an Appliance (Fixture) Module I use to control my pool light. When it burnt out I replaced the incandescent bulb with an LED bulb and had the same problem you're experiencing.  My solution, found at the jvde.us website, was to use a hash choke (see ebay) in series with the hot lead going to the bulb after the module. A plug in noise blocker (X10 XPPF or similar) between the module and the lamp should also do the trick.

 10 
 on: May 24, 2017, 04:48:59 pm 
Started by mldenison - Last post by Tuicemen
Since Alex10 was designed to enhance AHP use it to handle timers.

lights/appliances behaving as you describe usually indicates a noise or signal sucker.
However if this behaviour doesn't happen when you send the command from the bridge web interface or from the ALex10 UI then the issue is in how Alexa understands the device name. If this is the case try renaming the device.

Pages: [1] 2 3 ... 10