bren1818 / TCPLightingWebInterface

Web App interface to control the "Connected by TCP" bulbs
MIT License
30 stars 15 forks source link

Comments, Questions, open forum (2) #6

Open bren1818 opened 8 years ago

bren1818 commented 8 years ago

Closed the last topic as it had gotten really lengthy. Opening this one for more questions

vijimaini commented 6 years ago

@sktaylortrash Thanks. I will look into using reverse proxy.

sktaylortrash commented 6 years ago

well won't be double checking that raspberry pi walkthrough this weekend courier couldn't be bothered to actually ship my purchase.

sktaylortrash commented 6 years ago

@bren1818 @merrickw

@bren1818 Within the wiki itself I did some organizing of the sidebar to make it more readable (at least to me) if you hate it or want it tweaked let me know

bren1818 commented 6 years ago

I trust you, everything you've done thus far has been great :)

I added a few small tweaks and bug fixes over the weekend to the repository. Nothing Earth shattering though.

Cheers!

Bren

On Mon, Dec 11, 2017 at 7:34 PM Paul notifications@github.com wrote:

@bren1818 https://github.com/bren1818 @merrickw https://github.com/merrickw

  • I've tested my instructions with a Pi Zero W and couldn't replicate the Wi-Fi issue. Tried 3 different SSIDs on two different routers, so no clue. At any rate I have created a troubleshooting page. The only entry right now is how to use raspi-config to configure Wi-Fi
  • I added the Apache directives you suggested Bren
  • Merrickw I've tweaked the file permissions stuff. Realized I always sudo my commands even file copies so I wasn't seeing the permission issue
  • I also couldn't replicate the php issue but since it doesn't hurt anything to have it there I've added libapache2-mod-php to the php install command

@bren1818 https://github.com/bren1818 Within the wiki itself I did some organizing of the sidebar to make it more readable (at least to me) if you hate it or want it tweaked let me know

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-350905228, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH-wLc5s1KohErtqsKc5Mv7b9W7m2ks5s_cowgaJpZM4LEhw5 .

sktaylortrash commented 6 years ago

@bren1818 did you mean to move the images folder into the CSS folder? if so it broke a bunch of the code

sktaylortrash commented 6 years ago

@bren1818 actually I see it was intentional it may only be the syncgateway image

bren1818 commented 6 years ago

I will double check the gateway image. I did mean to move all the image files. I wanted to tidy up everything. Must have missed that. Sorry

On Dec 11, 2017 11:18 PM, "Paul" notifications@github.com wrote:

@bren1818 https://github.com/bren1818 actually I see it was intentional it may only be the syncgateway image

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-350940716, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH5SNQnutgaeVcsmUzWklw5eOhssgks5s_f6EgaJpZM4LEhw5 .

sktaylortrash commented 6 years ago

I put in a pull request with the corrections. Never done that before hope I did it properly

bren1818 commented 6 years ago

@sktaylortrash your changes were great. I merged them in without issue. By the way, your work on the wiki is outstanding. Thanks kindly for all of your work on that!!

sktaylortrash commented 6 years ago

@bren1818 Thanks for the kind words. I think I've got pretty much everything relatively sorted out except the IFTTT integration page. I've edited the scheduler page you made just to tweak some of the language and to add a description of the relevant config.inc.php variables. Hopefully that's cool.

Do you think it's worth creating some recipes that link you through the steps to create a system from scratch? While I've tried to reference the related sections when in another there's not really an apparent order of operations to build a new system. i.e.

TCPLightingWebInterface Standalone Server on a Raspberry Pi

Using Dynamic DNS, Let's Encrypt & IFTTT

  1. OS Installation
  2. Webserver Installation
  3. WebInterface Install
  4. config.inc.php Customization
  5. Syncing the Gateway
  6. Dynamic DNS Setup
  7. Let's Encrypt
  8. IFTTT Integration
  9. Scheduler Configuration
vijimaini commented 6 years ago

@sktaylortrash I got my Raspi today and used your guide for installation for OS and webserver. It was great and easy to follow. The only issue I had was with changing password for SQL. The sql server complained about syntax error with: ALTER USER 'root'@'localhost' IDENTIFIED WITH 'mysql_native_password' BY 'NewPassword'; Other then that perfect, Tomorrow I will install TCPLightingWebInterface and let you know of any issues. Great Work!!

sktaylortrash commented 6 years ago

@vijimaini glad it mostly worked. I'll double check that mysql syntax I used the same command on my ubuntu install which is also debian like raspbian but there might be a couple differences.

Edit - Sure enough there's differences. Plus I completely forgot the installation security script

bren1818 commented 6 years ago

@sktaylortrash - I don't mind at all. With respect to the IFTTT recipes, are you suggesting we demonstrate "Select your assistant, ie Google assistant", "select either 'Say a simple phrase' or 'say a phrase with a number'", Populate your three what do you want to says, and response in the boxes provided,, click create trigger, for "that" choose webhooks and Make a web request, and then paste the following?

I suppose we could outline that. My thought though, is if the end user has managed to get the project up and running on their home machine or raspberry pi, got port forwarding etc setup, the IFTTT should be probably the easiest :)

I'm open to suggestions for sure though and can definitely add into the project. I did add the "Dim By" and "Brighten by" functions to IFTTT. I was hoping to be able to build an export function so all applets could be imported to IFTTT rather than creating them, but it doesn't look like we can do that just yet.

vijimaini commented 6 years ago

@sktaylortrash I saw your updated command in guide for changing password for sql, that I ran without problem. I followed your guide to install webinterface on Raspi and went fine. There was one issue that File viewlogs.php was named viewLogs.php on the distribution directory, which I fixed in my raspi. The remote api access security instructions were missing but I just copied file from my Apache server running on Mini Mac on which I have current Webinterface. There are no instructions on enabling SSL modules on apache on Raspi. If you have any instruction let me know. I do have signed TLS certificates from Letsencrypt ready to go. I have do the the IFTTT working using http, so I can control lights through Google Home. The Guides are very handy!!

sktaylortrash commented 6 years ago

@bren1818 I wasn't meaning IFTTT recipes I was meaning having a list like the example I included above on the landing page or somewhere easily found. Just because when you look at the wiki it's not immediately clear what the order of operations are if you are new to this project.

@vijimaini For enabling SSL the only thing I have documented is the setup for Let's Encrypt's client certbot which does it all for you including scheduling the renewals. I could probably put something together regarding using a certificate generated externally but I hadn't really intended to produce a full apache manual. Also if you are not using a client to generate the certs on the server itself you will have to manually renew and install it every 60-90 days. Not what I could call user friendly. The caveat on the client being you need to be able to forward port 443 to the server. If I somehow found myself in a situation where I couldn't do that I wouldn't use Let's Encrypt I'd pay the $10 a year for a comodo cert

vijimaini commented 6 years ago

@sktaylortrash I was bit lost trying to enable mod_ssl, but googled it, as I am not used the raspi apache. All is done now and now I have IFTTT Triggers sent to the raspi api.php using https. Raspi System is GO now TCPwebinterface and IFTTT. I have enabled auto renew for certificates and will monitor.

sktaylortrash commented 6 years ago

@bren1818 I have some questions/thoughts on IFTTT apache config before I write up that set of instructions in the wiki. Any chance you have some time in the next several days and are amenable to chatting through some sort of instant messenger? would be more efficient than here

merrickw commented 6 years ago

@sktaylortrash @bren1818 I'm not sure if I missed this instruction somewhere, but I just re-installed my pi since my networking was getting screwy. For a custom port for Apache I needed to edit this:

sudo nano /etc/apache2/ports.conf

to replace the LISTEN 80 with my custom port.

I found that instruction from this page: http://www.noveldevices.co.uk/rp-webserverport

sktaylortrash commented 6 years ago

@merrickw you didn't miss something there's just no updated documentation for IFTTT regarding usage with the Pi. The items referenced in the Word doc were for XAMPP as that was the only tested implementation when @bren1818 blessed us with a functional API

bren1818 commented 6 years ago

@sktaylortrash scenes can now be setup with schedules. Makes my scheduler component largely irrelevant... but hey its here, & it appears to work!

sktaylortrash commented 6 years ago

@bren1818 cool - Not sure I'll get to play with it before I fly out in the morning. But I'll definitely check it out

sktaylortrash commented 6 years ago

@bren1818 couldn't help myself, updated my install changed a schedule and it showed in the phone app so looks like it's all good. Also the Remote icon on the info page is a nice touch

bren1818 commented 6 years ago

Have a fantastic trip! Glad it works for you too! Happy holidays!

On Dec 24, 2017 1:37 AM, "Paul" notifications@github.com wrote:

@bren1818 https://github.com/bren1818 couldn't help myself, updated my install changed a schedule and it showed in the phone app so looks like it's all good. Also the Remote icon on the info page is a nice touch

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-353768319, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCHyU4sYQn2L5xDC6a_uABX8rldgeAks5tDfEygaJpZM4LEhw5 .

merrickw commented 6 years ago

@bren1818 Nice job on the scenes! Just tested it out, looks great.

One thing I never understood about scenes - what does stopping a scene mean? In my mind it should remember the state of every bulb before the scene and revert ... I never understood what the end of a scene means ... all scene devices off?

sktaylortrash commented 6 years ago

@merrickw scenes can be used in lots of ways I use them as additional grouping. So a main floor scene with no schedule turns all selected bulbs on at start and off at stop. Also I make groups and apply schedules so a selection of lights turns on at X (start) and off at X2 (stop). Scenes as groups is especially useful since virtual devices remove access to individual bulbs. So my ceilings fan has 4 bulbs if I virtual device them I lose the ability to only turn some bulbs off and on. But with a scene I can select a subset and start and stop that

merrickw commented 6 years ago

So this is where I get confused - let's say you have three scenes, a, b, and c. You start scene a, then start scene b, then stop scene b. Does that turn lights off or go back to scene a? If ending a scene just means turns lights off, that's like going to another scene of off, no?


From: Paul notifications@github.com Sent: Monday, December 25, 2017 4:00 PM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)

@merrickwhttps://github.com/merrickw scenes can be used in lots of ways I use them as additional grouping. So a main floor scene with no schedule turns all selected bulbs on at start and off at stop. Also I make groups and apply schedules so a selection of lights turns on at X (start) and off at X2 (stop). Scenes as groups is especially useful since virtual devices remove access to individual bulbs. So my ceilings fan has 4 bulbs if I virtual device them I lose the ability to only turn some bulbs off and on. But with a scene I can select a subset and start and stop that

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-353890595, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJCd2atMVVcWgxpId3v7WY7mhr6U6ks5tEAz9gaJpZM4LEhw5.

sktaylortrash commented 6 years ago

I haven't got scenes with overlapping lights so I can't honestly say what happens in that instance. Only thing to do is test that I guess.

bren1818 commented 6 years ago

Pretty sure, if the scene turns the lights on, it will turn them off when the scene ends (if you specify the end time).

Remember a scene starting can also turn lights off, I haven't tested if it will turn them back on if it starts by turning them off.

Merry Christmas.!

On Dec 25, 2017 4:52 PM, "Paul" notifications@github.com wrote:

I haven't got scenes with overlapping lights so I can't honestly say what happens in that instance. Only thing to do is test that I guess.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-353892380, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH4Mdloe9cJQqo8niK0uHclxnDaCFks5tEBkHgaJpZM4LEhw5 .

sktaylortrash commented 6 years ago

Hey guys and gals I'm still working on putting together some workable instructions for those unfamiliar with the Arduino programming environment but I have written some code for theses little $8 (less from China) wifi micro-controllers to create wall switches for controlling the TCP lights. Basically build-your-own remotes. I have 1 and 2 button versions built nodemcupng-small both

The project is over at https://github.com/sktaylortrash/TCP-Button if you are familiar with arduino and the nodemcu (esp8266) controllers have at it. For everyone else hopefully I have something put together really soon.

capncybo commented 6 years ago

Hey Bren, I actually just joined GitHub to say a BIG Thanks to you for this Project. I stumbled across it during your earlier efforts & what you've accomplished with this is Fantastic. I kinda forgot about it for awhile but checked it out recently & got to thinking... Screw using a PI maybe I can shoehorn this into my Asus Router via Entware instead. I won't say it was easy for me, as I struggled... my learning cure was steep, & there was A LOT of trial & error. But eventually I got it working. So in this case it's just the Router (with a Memory stick) & the TCP-Gateway. ZERO additional Hardware. PERFECT!!!

bren1818 commented 6 years ago

Thanks for the compliment and sharing! That's really nifty. I'll going to have to Google Asus Entware. I hadn't heard of that prior. If you write up what you did, I'd be happy to mention it. I need to place an article about what one member @sktaylortrash did by wiring a switch up to make API Calls. He was also instrumental in assisting with documentation.

Thanks again, hope to hear more about your setup!

On Jan 23, 2018 11:27 PM, "capncybo" notifications@github.com wrote:

Hey Bren, I actually just joined GitHub to say a BIG Thanks to you for this Project. I stumbled across it during your earlier efforts & what you've accomplished with this is Fantastic. I kinda forgot about it for awhile but checked it out recently & got to thinking... Screw using a PI maybe I can shoehorn this into my Asus Router via Entware instead. I won't say it was easy for me, as I struggled... my learning cure was steep, & there was A LOT of trial & error. But eventually I got it working. So in this case it's just the Router (with a Memory stick) & the TCP-Gateway. ZERO additional Hardware. PERFECT!!!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-360017321, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH9bRP6s-4XRkfRZZLiXYBWUfkQmqks5tNrFDgaJpZM4LEhw5 .

sktaylortrash commented 6 years ago

Hey all,

Wondering if anyone out there has the CFL version of this system - http://bit.ly/2Gc5LVJ Also if anyone has the energy monitoring module - http://bit.ly/2DCEm1G

just curious on compatibility with the rest of what we have

bren1818 commented 6 years ago

Fascinating. I've seen references to some of this stuff in the code base but never actually looked them up. Its a crying shame they killed this equipment off, they had a lot of nifty stuff on the go.

Love the remote:

https://www.ebay.ca/itm/GREENWAVE-REALITY-DE220-1-IN-HOME-DISPLAY-ENGERY-MONITORING-SYSTEM-M3/222398285222?_trkparms=aid%3D222007%26algo%3DSIM.MBE%26ao%3D2%26asc%3D20170831090034%26meid%3D2e299e2b145a4c0faceeea33dd0dd91b%26pid%3D100005%26rk%3D1%26rkt%3D4%26sd%3D253378730949&_trksid=p2047675.c100005.m1851

On Wed, Jan 24, 2018 at 11:08 AM, Paul notifications@github.com wrote:

Hey all,

Wondering if anyone out there has the CFL version of this system - http://bit.ly/2Gc5LVJ Also if anyone has the energy monitoring module - http://bit.ly/2DCEm1G

just curious on compatibility with the rest of what we have

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-360184188, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH1ywNa8weDM2qE0rO1bWJWkvkY4wks5tN1VggaJpZM4LEhw5 .

capncybo commented 6 years ago

Good Point Bren, I should have thanked sktaylortrash for his work with the wiki too. Anyways to summarize what I did. -I updated my RT-AC68U Router firmware to the latest ASUSWRT-MERLIN Firmware. available via: https://asuswrt.lostrealm.ca/ Then you need to format a portion of a USB-Drive or Memory Stick in EXT3 format (I made a 32G EXT Partition.) Stick that drive into one of your routers usb ports Then you ssh into your router (Use Putty if on windows) My router was the standard: ssh 192.168.1.1 after logging in with your router's admin username & password... type: entware-setup.sh (you should be prompted if the script see's a suitable partition to install ENTWARE) I pressed <1> (The install should begin) After the install you NEED to do the following.... opkg update (if you don't update you will not have the newest packages/repositories required) Now comes the fun part the big install, Enter the following... opkg install php7 php7-fastcgi php7-mod-ctype php7-mod-dom php7-mod-gd php7-mod-intl php7-mod-json php7-mod-mbstring php7-mod-mcrypt php7-mod-pdo php7-mod-pdo-sqlite php7-mod-simplexml php7-mod-sqlite3 php7-mod-xml libxml2 php7-mod-fileinfo lighttpd lighttpd-mod-fastcgi libsqlite3

It might be overkill, & perhaps every module may not be required but the above worked.

Next I installed nano, git, & git-http... opkg install nano git git-http (Note: I find nano better for editing config files than vi) Configure lighttpd by ENTERING the following... sed -i 's/#server.port = 81/server.port = 81/g' "/opt/etc/lighttpd/lighttpd.conf" sed -i "/server.upload-dirs*/cserver.upload-dirs = ( \"/opt/tmp\" )" "/opt/etc/lighttpd/lighttpd.conf"

And, finally, get PHP Working: cat >> /opt/etc/lighttpd/conf.d/30-fastcgi.conf << EOF server.modules += ( "mod_fastcgi" ) fastcgi.server = ( ".php" => ( "localhost" => ( "socket" => "/tmp/php-fcgi.sock", "bin-path" => "/opt/bin/php-fcgi", "max-procs" => 1, "bin-environment" => ( "PHP_FCGI_CHILDREN" => "2", "PHP_FCGI_MAX_REQUESTS" => "1000" ) ) ) ) EOF

Of course one still has to use git to grab your files... git clone https://github.com/bren1818/TCPLightingWebInterface.git

And after that, copy the entire TCPLightingWebInterface directory & subdirectories into... /opt/share/www this can be done by going into that directory via: cd TCPLightingWebInterface (and then) cp -R * . /opt/share/www

Nevermind from here on I'm duplicating the config instructions... The final step is to restart the lighttpd web server /opt/etc/init.d/S80lighttpd start

gzapatal commented 6 years ago

### @bren1818 , I want to thank you for this amazing develop/project, my TCP Lights got back to life and I did integrate them to my smart home project.

I set an Apache server on my Win10 box but I'll try setting up the Lighttpd web server into my Asus router (thanks @capncybo ) but using Optware (https://www.hqt.ro/lighttpd-web-server-with-php-support-through-optware-ng/), from my understand if I use Download Master I need to use Optware

PartialVolume commented 6 years ago

@bren1818 I just want to say thanks for some great software !!, Real nice work. The whole setup works beautifully with IFTTT. (Kubuntu Linux server with one TCP gateway and 10 TCP connected bulbs.

fgildred commented 6 years ago

Hi All, Curious if anyone has tried setting this up recently? Long story short, I had bulbs and a hub in storage. Went to setup them up the other day and ended up here. I "had" the hub working with smartthings as I had blocked the TCP device from talking out to the web. Well, I made the mistake of then changing the local IP. For some reason that hosed my setup. I went to attempt to setup things again and no go.

Fast forward to the next day and I succesfully restored the firmware, or so I thought. I really want to use @bren1818 project, but I wonder if I have a now defunct hub. In desperation, I went ahead and let it update to the latest firmware. I then tried to drop back to 2.0.47. It seemed to work, and I can even get ssh into the box, but the web interface doesn't seem to work anymore(It only allows me to see the settings page. The "SmartControl" and "My Home" options are grayed out.) I do see information on the Settings page and it shows the right firmware revision.

So-am I out of luck with @bren1818 project if my gateway doesn't seem right? Has anyone seen this? From what I understand the phone app(i'm on iOS) is no longer available. After the box is booted up, I can click the sync button and it appears to do it's thing. Before I venture forth with a raspberry pi, I wanted to know if anyone has had issues like I have with the web interface.

sktaylortrash commented 6 years ago

I was only able to get this project working with the latest firmware 3.0.74 which doesn't have ssh working. Also I was able to download the app from Apple and Google recently. They just only work within your home and not over the internet any longer

bren1818 commented 6 years ago

Hey there - the web app should work no problem with the latest bridge firmware, although I have heard that there was a "silent" firmware pushed out by Greenwave which made downgrading fail. I haven't been able to re-downgrade my hub, so I've let it update to the latest and its running without issue.

Before you setup the Raspberry Pi, you can always run the project from a local web server on your laptop/desktop. @sktaylortrash https://github.com/sktaylortrash did a fantastic job cleaning up my documentation and writing some extra documents here: https://github.com/bren1818/TCPLightingWebInterface/wiki/Installation-for-Apache-on-XAMPP-Windows I followed his instructions to setup my Raspberry Pi and haven't looked back. Runs beautifully.

I can also say even though I made the web interface, now that I have the lights integrated through the web interface with IFTTT, I've been using the Google Home and voice commands almost solely.

Best of luck, there's a great group of people here so feel free to ask questions if you get stuck.

Cheers,

Bren

On Mon, Aug 20, 2018 at 8:16 PM, fgildred notifications@github.com wrote:

Hi All, Curious if anyone has tried setting this up recently? Long story short, I had bulbs and a hub in storage. Went to setup them up the other day and ended up here. I "had" the hub working with smartthings as I had blocked the TCP device from talking out to the web. Well, I made the mistake of then changing the local IP. For some reason that hosed my setup. I went to attempt to setup things again and no go.

Fast forward to the next day and I succesfully restored the firmware, or so I thought. I really want to use @bren1818 https://github.com/bren1818 project, but I wonder if I have a now defunct hub. In desperation, I went ahead and let it update to the latest firmware. I then tried to drop back to 2.0.47. It seemed to work, and I can even get ssh into the box, but the web interface doesn't seem to work anymore(It only allows me to see the settings page. The "SmartControl" and "My Home" options are grayed out.) I do see information on the Settings page and it shows the right firmware revision.

So-am I out of luck with @bren1818 https://github.com/bren1818 project if my gateway doesn't seem right? Has anyone seen this? From what I understand the phone app(i'm on iOS) is no longer available. After the box is booted up, I can click the sync button and it appears to do it's thing. Before I venture forth with a raspberry pi, I wanted to know if anyone has had issues like I have with the web interface.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-414505886, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH2sFtwBw0lx9mAuCaD5XXxMaMqQpks5uS1F5gaJpZM4LEhw5 .

fgildred commented 6 years ago

I’m thrilled you are both still here and quite surprised how quickly you both replied! Having purchased around a dozen bulbs, I’m quite keen to get them connected with all of my other hue bulbs, door sensors, and the like. Also, trying to avoid the wife aggro as I’ve been swapping out bulbs left and right.

Reading Paul’s comment, I gave the greenwave reality app another try. I did try updating the firmware to the latest version again, but thankfully, even though I removed the block in my dd-wrt router, it didn’t take. I say thankfully as the downgrade to 2.0.47 is still in the unit and so using the root account and the thinkgreen pass as the credentials, I was able to login and add two bulbs via the app. It is definitely cludgy and has lots of errors popping up in it(complains it can’t get energy use, thermostat reading, won’t identify bulbs, etc.), but I was able to then setup my smartthings integration again! ( https://community.smartthings.com/t/release-tcp-connected-bulbs-work-with-smartthings-again/78817 )

However, I’d really like to explore Bren’s project that he and Paul have done such a nice job with. I cannot find anywhere to register for an account on greenwaves site, so if I do update to the latest firmware, I fear I won’t be able to log back into the box. Anyone know where/how do I create an account? Am I out of luck if I never set one up back when greenwave supported it? Or will that matter? (I assume it will?). Thanks in advance

bren1818 commented 6 years ago

You are out of luck with Greenwave for sure. They shut down their service and then turfed the interface on the bridge via the updates.

That said you should still be able to use the old firmware with my project, you'd just need to connect over port 80 vs 443 if I recall correctly.

Once you get the project up and running you could technically allow access to the web interface outside of your local network if you want.

Let me know if it works for you. It may require a bit if tweaking but I'm pretty sure it should be a go. Keep us posted. Good luck!

On Mon, Aug 20, 2018, 10:05 PM fgildred notifications@github.com wrote:

I’m thrilled you are both still here and quite surprised how quickly you both replied! Having purchased around a dozen bulbs, I’m quite keen to get them connected with all of my other hue bulbs, door sensors, and the like. Also, trying to avoid the wife aggro as I’ve been swapping out bulbs left and right.

Reading Paul’s comment, I gave the greenwave reality app another try. I did try updating the firmware to the latest version again, but thankfully, even though I removed the block in my dd-wrt router, it didn’t take. I say thankfully as the downgrade to 2.0.47 is still in the unit and so using the root account and the thinkgreen pass as the credentials, I was able to login and add two bulbs via the app. It is definitely cludgy and has lots of errors popping up in it(complains it can’t get energy use, thermostat reading, won’t identify bulbs, etc.), but I was able to then setup my smartthings integration again! ( https://community.smartthings.com/t/release-tcp-connected-bulbs-work-with-smartthings-again/78817 )

However, I’d really like to explore Bren’s project that he and Paul have done such a nice job with. I cannot find anywhere to register for an account on greenwaves site, so if I do update to the latest firmware, I fear I won’t be able to log back into the box. Anyone know where/how do I create an account? Am I out of luck if I never set one up back when greenwave supported it? Or will that matter? (I assume it will?). Thanks in advance

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-414525693, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH96pbSnMSvNq69ZBm68q85VQ9sfHks5uS2r9gaJpZM4LEhw5 .

henroFall commented 6 years ago

This project is awesome. I have my hub flashed with v2 and working with Smartthings via the TCP Connect Smart APP and had to find the APK for my phone app, but today that crapped out. This project saved my life, now I can keep discovering all of these cheap bulbs I got online without needing my phone.

Oh, and yes, with v2 firmware, absolutely change the config file to use port 80 and not 443.

Thanks again!

jadakin commented 6 years ago

Great project, thanks, and I'm pleased ti find you are still interested in the bulbs. Thanks to your work, I have added 16 or so to add to my original pair and they all work very well. Most of them came from ebay as starter sets at a cost that was about the same as ordinary leds, so good news all round.

One thing: Most of these sets came with wireless gateways - I have three or four of them. I can find no reference to these in any of the dev work, and while they work fine with the Greenwave app, I just cannot get them to work with your project, and I'm curious as to why. I am no expert, but as far as I can tell the GWRlogin to fetch a token produces a 400-bad request response.

Have you come across these at all? They would be handy if my wired gateway ever got bricked!

bren1818 commented 6 years ago

@jadakin Glad you're making use of the bulbs. They're a fantastic product, too bad they were abandoned. I appreciate the note on the wireless gateway. I never saw those in Canada, but can't imagine they should work any differently than the wired gateway. Perhaps they're not using SSL ( try using port 80 vs 443?) but I'm afraid without having one, I can't do much in the way of debugging. Let me know if using port 80 works. Given you got them off Ebay, they could be on various firmware versions.

sktaylortrash commented 6 years ago

@jadakin I know I had some random weirdness happen when I had 2 wired gateways on the same network. Have you tried it with the wired one unplugged. Also can you let me know the model number of a wireless gateway. I'd love to try to get one to mess with

jadakin commented 6 years ago

@bren1818 Totally agree they are a fantastic product. My only real complaint with the hardware is the way they cycle up and down when they occasionally lose sync. I've come back of holiday to find my house flashing like a beacon! The wireless hubs are model number UBW1J1-1G01-TP. I did try disconnecting my wired hub before I tried the wifi one, so it's not that, sadly. They are a "wall wart" type design: would a UK one be any good to you? I'd be more than happy to donate one as a "thank you".

jadakin commented 6 years ago

@bren1818 I did try port 80, by the way. No joy.

sktaylortrash commented 6 years ago

@jadakin do you have really dirty power? In all the years I've had these bulbs I've never had them lose sync

bren1818 commented 6 years ago

@jadakin Shoot sorry to hear that. I looked up the UBW1J1-1G01-TP but didn't find much on it. Its also odd that your bulbs would cycle up and down. In theory that should only happen if they're in discovery mode, and that should only occur if they're powered on and off in succession 3 times. A UK plug would be of no use to me, and I have a few spare bridges kicking around already. @sktaylortrash may be interested though. He's been incredibly helpful with this project and also dives into the hardware side of things, even wiring up custom switches - you may want to PM him. Your best bet though is to try the hard-wired bridge. On your network - do you have pre-assigned ip addresses for network items? does the App indicate a different IP? Depending on your hardware is is possible the wireless bridge was issued a ipv6 address versus ipv4?

jadakin commented 6 years ago

@sktaylortrash Sorry, I've been getting my participants mixed up. My bad. You are welcome to a wireless bridge if it's practical to send it to you. Pm me. They are UK plugs and marked only at 220v 50hz, though they look fairly easy to crack open. My bulbs have lost sync two or three times in as many years. We are in a rural area with old overhead lines and it's credible that occasionally it has bounced on and off enough to upset them.

@bren1818 The hard wired bridge works fine. I was trying the wireless bridge independently, so yes, it gets a different IPv4 address which the app reports correctly (like I said, it works with the app no problem). I haven't bothered making it static as I was only testing and it hasn't had a chance to expire. The firmware page on the app gives the Gateway firmware as 0.7.18, which is clearly different to the wired version as you would expect, but whether it is the "new" firmware or not is unclear. I couldn't get it to work with port 80 or port 443 though.