Open bren1818 opened 7 years ago
It's working fine without the token at port 80. The above command returns a full dump of everything.
I'm not worried about making it work with the token, I figure it's before they enforced tokens in the code (although interestingly they do return a dummy toekn when requested).
What I'm thinking now is, since the REST API works fine with the latest build (with tokens), what is the benefit of downgrading to the older builds that have SSH enabled? What benefit do we gain?
There isn't much reason to have the ssh enabled version in my opinion. It has a web interface, however I found it to be flaky and continues to try to update the bridge when you access it.
So if the command worked, then yep API works for you. It is funny about the dummy code as you indicate.
We'll have fun with the code. My Dev branch is cleaned up but less complete, but I did extend it to integrate with the Phillips hue bridge.
On May 19, 2017 10:32 PM, "inahas" notifications@github.com wrote:
It's working fine without the token. The above command returns a full dump of everything.
I'm not worried about making it work with the token, I figure it's before they enforced tokens in the code (although interestingly they do return a dummy code).
What I'm thinking now is, since the REST API works fine with the latest build (with tokens), what is the benefit of downgrading to the older builds that have SSH enabled? What benefit do we gain?
— 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-302845329, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCHwIZ7inIUTRJbaQNqNPxz9gUDXkKks5r7lDGgaJpZM4LEhw5 .
@merrickw - Good News! Using IFTTT, webhooks, this project and say a Google Home - you can totally control your lights using voice commands. I'll be documenting the process in the next few days and hopefully making a Youtube video. The process is trivial really and just relies on issuing commands to the api.php file via the webhooks in IFTTT. It'll require you to have a static IP, or use a service like dyndns, but works beautifully.
That is awesome! I look forward to trying this out. I do use a dyndns service, so that part is covered...
Thanks for working on this!
-------- Original message -------- From: Bren notifications@github.com Date: 11/27/17 7:11 PM (GMT-05:00) To: bren1818/TCPLightingWebInterface TCPLightingWebInterface@noreply.github.com Cc: merrickw merrickw@hotmail.com, Mention mention@noreply.github.com Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@merrickwhttps://github.com/merrickw - Good News! Using IFTTT, webhooks, this project and say a Google Home - you can totally control your lights using voice commands. I'll be documenting the process in the next few days and hopefully making a Youtube video. The process is trivial really and just relies on issuing commands to the api.php file via the webhooks in IFTTT. It'll require you to have a static IP, or use a service like dyndns, but works beautifully.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-347371017, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJOHK3p08GGdCLaukV_PxzsyZG6gzks5s60-PgaJpZM4LEhw5.
This is great news because I had nothing but bad luck with the firmware downgrading to make the hub work with smartthings. But with IFTTT I should be able to get it talking that way instead
I just gave it a quick test to turn one light off, and it worked like a charm.
I guess the next step would be to understand how to use the URL's to call scenes or multiple lights.
This is great!
You're too quick! I'm writing up a doc on how to connect everything :) yes, I'd say this gives me some more incentive to extend this project.
Gotta love black Friday Google home purchases :)
On Nov 27, 2017 8:09 PM, "merrickw" notifications@github.com wrote:
I just gave it a quick test to turn one light off, and it worked like a charm.
I guess the next step would be to understand how to use the URL's to call scenes or multiple lights.
This is great!
— 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-347380637, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH0uCw3y21A_8uZ54ZcK43yK6Kencks5s611FgaJpZM4LEhw5 .
@merrickw @sktaylortrash - I've written up some basic instructions on how to utilize IFTTT with the existing API in this project. I uploaded the docs into the DEV & Master branch. # Using this project with IFTTT.docx
I'll have to play some more with IFTTT and see what else I can work in with the existing API. This method appears to work fine with Rooms and Single Lights / grouped devices.
Enjoy!
@bren1818 that is super slick. My Google home wont be here until Thursday but I tested with my phone and it worked perfect. For the instructions you'll probably want to mention that a firewall hole needs to be made. Also the port change can usually just be done there without modifying the apache config. That's all I did anyways
Speaking of opening the firewall for http, port 80 ... I generally never leave that open for security. If I do open it up, what precautions should I take?
After I tested yesterday I just stopped XAMPP for safety...
From: sktaylortrash notifications@github.com Sent: Monday, November 27, 2017 10:17 PM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@bren1818https://github.com/bren1818 that is super slick. My Google home wont be here until Thursday but I tested with my phone and it worked perfect. For the instructions you'll probably want to mention that a firewall hole needs to be made. Also the port change can usually just be done there without modifying the apache config. That's all I did anyways
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-347401266, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJJBRLfZeI9ASDuU6Z8hhADULehTlks5s63tKgaJpZM4LEhw5.
So the security thing is the biggest issue with self running a service like this.
Hence why I was trying to get the smartthings integration mentioned here: working. But couldn't keep my bridge stable with the 3.0.39 firmware.
There's a couple options I would consider:
Another option I'm looking at is using a .htaccess file that only allows access from my subnet and specific external domains. I just need to figure out how to confirm what domain all the ifttt requests are coming from then I can use something like
@sktaylortrash Thanks for fielding that, spot on answer.
In a near future build I'll add a password option and a toggle to only process requests from an internal IP range and the IFTTT range.
The .htaccess method works well too, but not sure how comfortable people will be with configuring it. I should also add something about firewall rules. I was just eager to get it out there. Its nice to no longer have dumb bulbs.
I had been trying to create some routines with dialogflow but was struggling, this with IFTTT works pretty well though.
Sounds good.
In my testing last night the Say a phrase with a number option works pretty well to adjust brightness as long as you are willing to speak in percentages.
So say for my bedside lamp I create a phrase of Bedroom Lamp # and a web request of http://lighting.local/api.php?fx=dim&type=device&uid=216773570733536747&val={{NumberField}}
Then I say Bedroom Lamp 50 and the light goes to half brightness
I'm wondering though in your api is there a way to query the current brightness and then potentially reduce or increase by X amount? That way I could have a Dim Bedroom lamp command and have it reduce the current brightness by the X amount I specify.
Also once I get used to the smartthings world. Also only just got that hub I'm gonna see if I can write a device handler for it that communicates with your api. I'd really like to not have to buy other bulbs just yet to make my home more friendly to users beyond myself. Especially since I have 12 bulbs running currently and another 12 spares
@sktaylortrash I can definitely add a function for "dim-by". That shouldn't be too hard at all. I'll look into that tonight. There isn't one currently.
I hear you re: not having to purchase other bulbs. I purchased a number of TCP bulbs because truly they were/are a pretty fantastic product, but I also have my foot in the Philips Hue World. In my DEV branch I have code which allows you to connect to both TCP and HUE using my front end. If/when I find the time, I'll try and make it so we can create groupings from more than one bridge.
@sktaylortrash & @merrickw I just pushed a few updates to the api.php and include.php files as well as some extra files like a .htaccess, and documentation. I added in the requested Dim By / Brighten By functions too for devices / rooms / home and beefed up the security. I outlined the API calls in the 'API Notes.txt' I did some testing and it looks to work well. Let me know your thoughts :) Hope you like em!
Sweet that was fast turnaround. Everything looks good and seems to work with the security implemented. api Password and .htaccess file are behaving as I would expect. Between the two of them I think that's a solid as you're going to be able to make it without getting ridiculous
Bren - what's the best way to apply the changes without losing my configuration?
Also, will the existing URL's still work or is the added security required?
From: Bren notifications@github.com Sent: Tuesday, November 28, 2017 10:19 PM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@sktaylortrashhttps://github.com/sktaylortrash & @merrickwhttps://github.com/merrickw I just pushed a few updates to the api.php and include.php files as well as some extra files like a .htaccess, and documentation. I added in the requested Dim By / Brighten By functions too for devices / rooms / home and beefed up the security. I outlined the API calls in the 'API Notes.txt' I did some testing and it looks to work well. Let me know your thoughts :) Hope you like em!
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-347740661, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJLHm13WgTkCc7nIpEFY_QlMGIWEZks5s7M1GgaJpZM4LEhw5.
@merrickw
I just copied over the lighting_url, and user_email values. Basically check to make sure the new include.php variables are set the same as your old.
If you don't want security change REQUIRE_EXTERNAL_API_PASSWORD to 0 and RESTRICT_EXTERNAL_PORT to 2 and don't add the .htaccess file
*edited to reflect mistake mentioned in following post
@sktaylortrash Thanks for the quick tips;
A couple of edits - I believe for no new security you want REQUIRE_EXTERNAL_API_PASSWORD set to 0. Also, the token file needs to be copied over (if creating a new folder).
Thanks for the help, so far it's been handy to turn rooms on and off with Google Home.
From: sktaylortrash notifications@github.com Sent: Wednesday, November 29, 2017 9:13 AM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@merrickwhttps://github.com/merrickw
I just copied over the lighting_url, and user_email values. Basically check to make sure the new include.php variables are set the same as your old.
If you don't want security change REQUIRE_EXTERNAL_API_PASSWORD to 1 and RESTRICT_EXTERNAL_PORT to 2 and don't add the .htaccess file
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-347871996, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJHRiGXbOncub8dzkSQUs27Tf9ocAks5s7WaVgaJpZM4LEhw5.
@merrickw oops good catch on the 0. I've updated my previous post to reflect in case someone else wanders in.
I didn't move my install so I never thought about the token
@merrickw @sktaylortrash - Glad to hear you got things working 👍
I will work on documenting what each of the options mean in the include file. I think now that IFTTT has rolled out webhooks (perhaps they did sooner and I didn't notice) this project will get some more interest from all of those abandoned TCP users. TCP even yanked their youtube videos and documentation, so I added what I could find here. I've bought myself a Raspberry Pi zero which I'm going to test out as my webserver versus leaving my desktop on at home. We'll see how that goes :)
Keep us posted on the Raspberry Pi webserver, that sounds like a good idea.
Another question, is there a URL that would Activate/Deactivate Scenes/Smart Control? I see it's calling scenes.php from the console, but that's it.
The Pi should work well. I have my instance running in a Linux virtual machine without issue
@bren1818 Thanks the IFTTT Adiition works great. The only issue I have is that I cannot use SSL as I have self issued SSL certs and IFFTTT does not work on those certs. Has any body encountered same issue? Is using http good enough, though password is exposed.
If you really want HTTPS/SSL you could get a free certificate from Let's Encrypt. If you're running Apache on Linux I'm pretty sure they have a client that will auto renew their certificates.
Otherwise, with HTTP if you use the .htaccess file to limit external connections to only api.php - someone would have to be intercepting traffic between you and IFTTT in order to: 1: Get the port (assuming you run on an alternate than 80) 2: The uid for the light or room 3: The password for the api.
Then to do anything other than turn that one light on and off, they'd have to be intercepting your traffic for quite awhile to get more uid's. Well unless you turn lights off and on a lot in a short period
And ultimately the worst they could do is turn your lights off and on
Normally I'm super anal about punching holes in my firewall for services directly on my primary Lan and instead dump them in a DMZ but I wasn't concerned for this instance
@sktaylortrash @bren1818
Do you have a recommendation for a RaspberryPi Zero kit? I see a bunch on Amazon.
Can you recommend a tutorial to setup an Apache server on it?
I'm a windows guy so this is a bit out of my realm.
@merrickw if you want a complete kit then this one will do the trick https://www.amazon.com/CanaKit-Raspberry-Wireless-Starter-Official/dp/B06XJQV162 It has the mini-HDMI and the USB OTG already included. Also the SD card has the NOOBS quick setup environment already loaded.
So when you go through this tutorial you can skip the part about copying NOOBS to your card
Perfect. I'm going to give that a shot.
-------- Original message -------- From: sktaylortrash notifications@github.com Date: 11/30/17 1:47 PM (GMT-05:00) To: bren1818/TCPLightingWebInterface TCPLightingWebInterface@noreply.github.com Cc: merrickw merrickw@hotmail.com, Mention mention@noreply.github.com Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@merrickwhttps://github.com/merrickw if you want a complete kit then this one will do the trick https://www.amazon.com/CanaKit-Raspberry-Wireless-Starter-Official/dp/B06XJQV162 It has the mini-HDMI and the USB OTG already included. Also the SD card has the NOOBS quick setup environment already loaded.
So when you go through this tutorialhttps://www.raspberrypi.org/magpi/apache-web-server/ the part about copying NOOBS to your card
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-348282772, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJMqwXiKd_3r3xCC_QsznHeTz3Q6gks5s7vglgaJpZM4LEhw5.
@sktaylortrash Thanks. I will try let’s encrypt. I run Apache on Mac. I use a high end port and not 80. Our isp blocks port 80. I should also try Pi as a web server.
@vijimaini - I know it was answered above, but you can use www.sslforfree.com to make a genuine certificate if Let's Encrypt doesn't work for you. I have used www.sslforfree.com in the past and it works very well. That said, using a non standard port, the .htaccess and a password should keep you pretty secure 👍 Thanks @sktaylortrash for answering above - the kit you recommended to @merrickw was the one I ordered myself so we'll see how it works. I should get it on Friday.
@bren1818
Any thoughts on my other question - is there a URL that would Activate/Deactivate Scenes/Smart Control? From the Scenes UI I see it calling scenes.php from the console, but that's the full URL.
@merrickw the scenes code should be able to be run the same way through IFTTT You'd have to add the scenes.php to the .htaccess file as allowable. Then the URL for the webhook would be a post passing a 'scene', (scene ID) and an 'action' which was "on", "off" or delete.
something like {host}:{port}/scenes.php and then POST data {scene: sceneID and action: "on|off"}
I haven't played with it yet, but that should do it.
Cheers,
Bren
I'm not sure how to add POST data ... and get the Scene ID
From: Bren notifications@github.com Sent: Thursday, November 30, 2017 3:19 PM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@merrickwhttps://github.com/merrickw the scenes code should be able to be run the same way through IFTTT You'd have to add the scenes.php to the .htaccess file as allowable. Then the URL for the webhook would be a post passing a 'scene', (scene ID) and an 'action' which was "on", "off" or delete.
something like {host}:{port}/scenes.php and then POST data {scene: sceneID and action: "on|off"}
I haven't played with it yet, but that should do it.
Cheers,
Bren
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-348309074, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJI09OPTuTbLjGIgll4ylPeEtZ8G0ks5s7w3SgaJpZM4LEhw5.
I'll try and document tonight. Webhooks I believe has a post option. I'll test tonight and let you know. Worst Case I could add an option to the API.PHP to trigger scenes like the other calls.
Will let you know
On Nov 30, 2017 3:24 PM, "merrickw" notifications@github.com wrote:
I'm not sure how to add POST data ... and get the Scene ID
From: Bren notifications@github.com Sent: Thursday, November 30, 2017 3:19 PM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
@merrickwhttps://github.com/merrickw the scenes code should be able to be run the same way through IFTTT You'd have to add the scenes.php to the .htaccess file as allowable. Then the URL for the webhook would be a post passing a 'scene', (scene ID) and an 'action' which was "on", "off" or delete.
something like {host}:{port}/scenes.php and then POST data {scene: sceneID and action: "on|off"}
I haven't played with it yet, but that should do it.
Cheers,
Bren
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/ bren1818/TCPLightingWebInterface/issues/6#issuecomment-348309074, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ AWTwJI09OPTuTbLjGIgll4ylPeEtZ8G0ks5s7w3SgaJpZM4LEhw5.
— 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-348310350, or mute the thread https://github.com/notifications/unsubscribe-auth/ACDCH2zM_vqTddJ3KlJTySCmn_Get5Zvks5s7w8DgaJpZM4LEhw5 .
@merrickw I updated 3 files in the project, just for you 👍 pull the updated .htaccess, scenes.php and scenescreatedit.php
I made the scenes page tell you the scene Number (ID) and listed how to make a call via a webhook like so:
http://{{your-web-address}}:{{port}}/scenes.php?scene={{Scene Number}}&action={{on|off}}&password={{your-api-password}}
Dont worry about using post, I made it so it will work with the standard GET and uses the security from the api.php
Small confession, it looks like I never finished the creation and edit pages of scenes, but this is something I'll get around to eventually. It should pull the ones you've made via the app though.
Hope this works well for you.
Cheers, dinner time!
Bren
@bren1818
Scene stuff looks good worked fine in my initial testing.
Just to test everything I setup a completely clean linux VM tonight to make sure I knew what modules are needed to make everything work and that tutorial I linked to is a little deficient. There's several php modules needed to get this all sorted. I'll see if I can find a spare SD card to throw in my PI and build you guys out some better instructions. Depends on how busy work is tomorrow
On another note. I have a couple more bridge kits coming. Couldn't pass them up @ $10 a piece. Just wondering. Has any of this recent stuff made it's way into the DEV branch that has the multi bridge support? I'm thinking I'd possibly like to run my outdoor bulbs on one bridge, interiors on another.
Thanks @bren1818
I tested it out, It seems to be invoking a scene, but it's not invoking the right scene. I think it's just turning all the bulbs on. Let me know if I can help troubleshoot.
I am using a URL without a password or the htaccess file for now; My URL looks like: http://blahblah.noip.com:1234/scenes.php?scene=2147483643&action=on
weird I just fired off all my scenes one at a time and they behaved as expected
@sktaylortrash - 10$!? Where? Thats a great deal. I haven't seen any of the TCP stuff in stores for the last 6 or so months. I had kept an eye out. My second bridge actually bit the dust, that's why I haven't invested much time into the Dev branch. I haven't migrated any of these changes as with the Dev branch I took a different approach.
In theory you could setup more than one instance of this project under different ports and different names virtual hosts and it should hum along. You could have a poke around the dev branch, but I haven't really documented much of it. It follows some of the same principles, but I was working on it to tie the Hue bridge to the TCP bridge, given the IFTTT now has web-hooks I haven't decided if I want to continue with it.
The main driver for supporting more than one TCP bridge was because the bridges only allow 4 rooms when using a remote. Given I have a kitchen, living room, an office, two bedrooms and a basement, I couldn't program all of my rooms onto one bridge / remote pair so I thought If I have two bridges I could in theory control 8 different rooms.
For what its worth, it ended up being a hassle having more than one bridge, but poke around and let me know what you think. My Pi should be shipping in tonight.
@merrickw - It should work as expected ... I tested last night, that being said, the scenes function for me has always been a bit flakey. IE I can program a scene using the app and schedule it, but it never actually fires on the time I've specified (Even if the time on the bridge is correct). I'll look into it further though and see if I can find any reason why it wouldn't work.
Cheers,
Bren
The unopened kits were a couple hours away. Found them on a local buy and sell site. I haven't seen them yet my nephew's picking them up Monday but from the pictures there the ones with 2 bulbs a bridge and a remote. So if nothing else I got 4 more bulbs for $20.
I'll dig around in that other branch see what I can determine.
It's funny about scenes. I use them extensively to turn on lights in the morning when I wake up and again just after I normally leave as well as for exterior lights in the evening. Only trouble I ever have is with the drifting clock since the C&C servers when down
I'm just loading NOOBS to a sd card right now so hopefully I can get a running apache setup documented for you guys today
I also use scene extensively via the scheduler inside the bridge. And, yes, other than the drifting clock and sunrise/sunset issue due to dead C&C, I'd also say they are quite reliable.
And man, the latest IFTTT development is all very exciting!
On Dec 1, 2017 11:45 AM, "sktaylortrash" notifications@github.com wrote:
The unopened kits were a couple hours away. Found them on a local buy and sell site. I haven't seen them yet my nephew's picking them up Monday but from the pictures there the ones with 2 bulbs a bridge and a remote. So if nothing else I got 4 more bulbs for $20.
I'll dig around in that other branch see what I can determine.
It's funny about scenes. I use them extensively to turn on lights in the morning when I wake up and again just after I normally leave as well as for exterior lights in the evening. Only trouble I ever have is with the drifting clock since the C&C servers when down
I'm just loading NOOBS to a sd card right now so hopefully I can get a running
— 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-348545538, or mute the thread https://github.com/notifications/unsubscribe-auth/AYOM2-tpghR7MPKsXC_htxODGYJQML5eks5s8C06gaJpZM4LEhw5 .
I created a new test scene (from the TCP android app). When I activate the scene from your UI it turns on all lights to 100% bright. When I activate from the TCP app the dim is set very low for all lights.
I'm wondering if the other testers are trying varying dim levels or all 100% brightness?
@merrickw Good catch. I was only watching to see if the bulbs turned on and off. But your right it's ignoring the brightness settings on the scenes and just turning any affected bulbs on to full
@merrickw @sktaylortrash Hmm, I will have a look at that. Perhaps my bridge call back is missing something. I'll see what I can find - good catch.
Further to that previous comment. The scene edit function in the WebInterface shows that in the attached instance one light should come on at 44% while the rest are at 100%. In reality the 44% is ignored.
Also now noticing this is not an api only issue as manually triggering the scene from the activate button in the interface exhibits the same behaviour.
Array
(
[sid] => 2147483642
[active] => 1
[name] => Weekday AM
[desc] => Array
(
)
[order] => 3
[type] => schedulecustom
[icon] => images/scene/coffee.png
[islocal] => 1
[every] => 1,2,3,4,5
[starttime] => 06:30
[stoptime] => 07:10
[device] => Array
(
[0] => Array
(
[id] => 216773570733040739
[type] => D
[cmd] => Array
(
[0] => Array
(
[type] => power
[value] => 1
)
[1] => Array
(
[type] => level
[value] => 100
)
)
)
[1] => Array
(
[id] => 216773570733536747
[type] => D
[cmd] => Array
(
[0] => Array
(
[type] => power
[value] => 1
)
[1] => Array
(
[type] => level
[value] => 0
)
)
)
[2] => Array
(
[id] => 359841714533870036
[type] => D
[cmd] => Array
(
[0] => Array
(
[type] => power
[value] => 1
)
[1] => Array
(
[type] => level
[value] => 44
)
)
)
[3] => Array
(
[id] => 360123189510580692
[type] => D
[cmd] => Array
(
[0] => Array
(
[type] => power
[value] => 1
)
[1] => Array
(
[type] => level
[value] => 100
)
)
)
)
)
The array dump you pasted above comes from this raw bridge command:
cmd=SceneGetListDetails&data=<gip><version>1</version><token>".TOKEN."</token><bigicon>1</bigicon></gip>
To trigger the scenes, I hit the bridge with a raw command of:
cmd=SceneRun&data=<gip><version>1</version><token>".TOKEN."</token><sid>".$sceneID."</sid><val>1</val></gip>"; //val 1 is on 0 is off
I'll do some digging to see if there is more to it then that. I'll keep you posted
Sorry guys this took longer than planned - Hopefully it helps RaspberryPI-LAMP-Install.docx
Very cool. I'll be receiving my kit in the next day or two and will use your guide.
Thanks for putting this together.
From: sktaylortrash notifications@github.com Sent: Saturday, December 2, 2017 3:31 AM To: bren1818/TCPLightingWebInterface Cc: merrickw; Mention Subject: Re: [bren1818/TCPLightingWebInterface] Comments, Questions, open forum (2) (#6)
Sorry guys this took longer than planned - Hopefully it helps RaspberryPI-LAMP-Install.docxhttps://github.com/bren1818/TCPLightingWebInterface/files/1523660/RaspberryPI-LAMP-Install.docx
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/bren1818/TCPLightingWebInterface/issues/6#issuecomment-348677408, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AWTwJHC6u6VBbwFpl4VofzBeyJCgMngnks5s8Qr2gaJpZM4LEhw5.
@sktaylortrash Thanks for putting that guide together. I got my pi all setup and running yesterday and I can say it works quite well. Wish I had your guide at the time. For whatever reason my pi would not pickup on a mouse/keyboard combo. I got through the guides using just the keyboard and enabled ssh. I fortunately had a usb-ethernet adaptor because I was seemingly unable to figure our how to turn on wifi using just the keyboard.
I installed apache and php 5. I used the default virtual host and modified it to meet my needs, but your guide is great. Thanks for that.
@merrickw re: the scenes I'll poke around the bridge to see if I can find a different command which activates with the levels. Worst case scenario, I'll read the scene from the bridge and manually activate the rooms and lights per their settings. I'll probably not get to this this weekend as I'm out and about but will see what I can do.
Cheers!
Bren
http://www.noip.com/support/knowledgebase/install-ip-duc-onto-raspberry-pi/ -- one thing to add to pi setup 👍
Closed the last topic as it had gotten really lengthy. Opening this one for more questions