|
|
Post by lpercifield on Dec 22, 2013 17:54:59 GMT
The solid blue indicates that the Visualight is having trouble connecting to the server. The two conditions that cause this are Wifi connection problems or an issue with your router/internet provider. Issue 1: Wifi: There is a slight bug in the firmware that causes connection issues when using a network or password with special characters - !@#$%^&*()_+= To fix this issue try another network without special characters or change the SSID of the network. Follow these steps to reset your Visualight: github.com/lpercifield/visualight/wiki/TroubleshootingIssue 2: Network: There are occasions where your router/internet provider block the Visualight connection based on the network port being used. This issue is a little more complex to solve. If you have admin access to your router that will help speed up the process. Visit this site: portquiz.net:5001/ to check if the port is blocked on your network. The page should show something like this:  Another issue that might cause your visualight to not respond is a browser problem: This is caused by a web browser that does not support websockets. You can visit this page to test your broswer: jimbergman.net/websocket-web-browser-test/If this doesn't work then try using another browser, we use Google Chrome here and it works great. When you click "Settings" under your visualight name you should see this:  |
|
joey
New Member
Posts: 1 
|
Post by joey on Dec 23, 2013 23:50:20 GMT
Hi,
My light arrived today. I've connected it two different networks. It shows up on the visualight website. I'm not impacted by the firmware bug as far as I can tell. Port 5001 is unblocked per the test. The browser allows websockets (google chrome). My dhcp server shows a good lease for it's MAC address. The wifly light is solid green. However it won't alert via the website nor will it use my default startup color. Any other thoughts?
Joey
edit: I've noticed using safari and chrome that the light switched from connected to disconnect repeatedly every 10 seconds or so.
|
|
|
|
Post by ecompositor on Dec 24, 2013 0:36:13 GMT
I have managed to connect my Diy and production bulb to the software. after logging out and reconnecting My lights go away. Do I need to reconnect and register the bulbs every time they are removed from power? I can live this , I just want to make sure im not missing something. It is looking good.
|
|
|
|
Post by lpercifield on Dec 25, 2013 19:21:22 GMT
Joey, It sounds like you are having an issue with the connection between the visualight server and your web browser. Can you confirm that its in the settings section that you see the connection change between connected and disconnected? First it may just be a cache issue. In chrome try "Clear Browsing Data" to reset or in safari try "reset safari". Once this is done try logging back into the site. The solid light on the wifly indicates a connection to the Visualight server so the issue shouldn't be on the hardware side. Let me know what you find out, Leif Hi, My light arrived today. I've connected it two different networks. It shows up on the visualight website. I'm not impacted by the firmware bug as far as I can tell. Port 5001 is unblocked per the test. The browser allows websockets (google chrome). My dhcp server shows a good lease for it's MAC address. The wifly light is solid green. However it won't alert via the website nor will it use my default startup color. Any other thoughts? Joey edit: I've noticed using safari and chrome that the light switched from connected to disconnect repeatedly every 10 seconds or so. |
|
|
|
Post by lpercifield on Dec 25, 2013 19:25:01 GMT
The bulbs should definitely stay registered in the system when they are switched on and off. When you say that your lights go away what does the website show? Are they not listed in the "Lights" menu at all or are they grayed out? Leif I have managed to connect my Diy and production bulb to the software. after logging out and reconnecting My lights go away. Do I need to reconnect and register the bulbs every time they are removed from power? I can live this , I just want to make sure im not missing something. It is looking good. |
|
n1mie
New Member
Posts: 1
|
Post by n1mie on Dec 25, 2013 20:01:02 GMT
Yeah, been having trouble for awhile today. I plugged in the visualight and followed the directions. The popup window that directs joining the network never saw the visualight. I tried repeatedly, tried troubleshooting ideas, tried different browsers, still no luck. I followed the same procedure with my iPhone and it worked. I was able to change the color the first time I tried. Now it doesn't work. I've gone back through the sequence again. I've swapped it to a different network. Still no joy. The port (5001) is open and passes the above test. There are no special characters either in my network name or it's password (straight alpha characters, one cap). I am using Safari or Firefox and I've definitely test both for web sockets and both work. I'm baffled!
|
|
|
|
Post by lpercifield on Dec 26, 2013 16:21:39 GMT
n1mie, I'm sorry you're having trouble. After you first had it working what has the color of the light been? Have you seen it flashing blue again like the initial setup? Also, there are three status LEDs on the red module inside the bulb. With it on, can you tell me what colors are blinking or solid? Leif Yeah, been having trouble for awhile today. I plugged in the visualight and followed the directions. The popup window that directs joining the network never saw the visualight. I tried repeatedly, tried troubleshooting ideas, tried different browsers, still no luck. I followed the same procedure with my iPhone and it worked. I was able to change the color the first time I tried. Now it doesn't work. I've gone back through the sequence again. I've swapped it to a different network. Still no joy. The port (5001) is open and passes the above test. There are no special characters either in my network name or it's password (straight alpha characters, one cap). I am using Safari or Firefox and I've definitely test both for web sockets and both work. I'm baffled! |
|
|
|
Post by lpercifield on Dec 29, 2013 16:24:19 GMT
|
|
|
|
Post by jasoneppink on Dec 29, 2013 17:39:05 GMT
I have successfully registered the Visualight (WOO) but I can't send it any color alerts, so it remains white. The green LED is blinking fast.
|
|
|
|
Post by lpercifield on Jan 3, 2014 17:59:02 GMT
Jason, My apologies for the delay in getting back with you. The fast blinking green LED indicates that the bulb is having trouble connecting to the visualight server. If you feel adventurous you can enable debug mode using Arduino. This will show the logs from the Visualight as it attempts to connect and is a great way to diagnose the issue. Also, sometimes the problem your are experiencing is fixed with a simple power cycle. Let me know if you are able to enable debug mode and what the logs show. Steps to setup debug mode: visualight.boards.net/thread/15/enable-debug-modeLeif I have successfully registered the Visualight (WOO) but I can't send it any color alerts, so it remains white. The green LED is blinking fast. |
|
|
|
Post by jasoneppink on Jan 5, 2014 18:32:41 GMT
Aha, I uploaded the factory reset sketch then uploaded the basic sketch again. Not sure what happened, but it's working like a charm now! (Tip to everyone else: make sure you turn debug back off if you turned it on.)
|
|
|
|
Post by claudiuo on Jan 9, 2014 18:12:55 GMT
jasoneppink Sorry if this is obvious, I just want to make sure I get it right. So basically, you went through the steps in the debug thread and loaded visualight_factoryRestore.ino and then the visualight_basic.ino? I will try to do the same since my light is still in the "just white" state. Thanks for posting this, hope it will help me as well.
|
|
|
|
Post by claudiuo on Jan 13, 2014 2:56:02 GMT
lpercifield Sorry to bother you with what may be a trivial issue, but I can't figure it out. I am on Linux Mint and when I try to compile the visualight_factoryRestore.ino I get a bunch of errors, like: /home/.../libraries/Visualight/WiFlyVisualight.h:337:27: error: ‘prog_char’ does not name a type /home/.../libraries/Visualight/WiFlyVisualight.h:337:38: error: ISO C++ forbids declaration of ‘str’ with no type [-fpermissive] Anything that I should be doing and I'm missing? Thank you!
|
|
