Jump to content

Mark LaBelle

c4Forums Member
  • Content Count

    430
  • Joined

  • Last visited

  • Days Won

    11

Mark LaBelle last won the day on November 17 2015

Mark LaBelle had the most liked content!

4 Followers

About Mark LaBelle

  • Rank
    Control4 Guru

Recent Profile Visitors

1,427 profile views
  1. Anyone need an HC800 and 3 HC 250's? I have some for sale.
  2. Found the issue - seems you have to turn off and back on Windows Features>SMB1 and the reboot. It now allows me to upload. Wife is happy we have a doorbell again! She was sick of flashing the lights on and off. 😄. Hey, it was a good workaround.
  3. For months now - since the upgrade to 2.9, announcements has never worked right - or in the case of my doorbell - AT ALL. I deleted the announcement agent and readded and started to build the myriad of announcements again (pain the arse). I went to add a simple doorbell sound to the announcement agent and low and behold I am now getting an error that it can't upload the simple wav or mp3 file from my desktop. See image for error. Something about an SM1B protocol for file sharing. Says I need SMB2. Crazy! Any idea what the heck happened to announcements?
  4. Did you ever get this fixed - same issue after upgrading?
  5. I love my dmx controlled RGB. I have them everywhere.... Domaudeo.com Man, they are highly configurable and spot on. No "popcorning" and works with any RGB lighting. BTW, that IP Driver for the Samsung works flawlessly. It just took some time for the system to catch up and get acclimated. 🙂
  6. Cyknight was the one who helped me... search Cyknight Fireplace Relay. It was back about 2 years ago or so.
  7. Well if it wasn’t for you it wouldn’t have!!!!! Thanks again Cyknight! Every time I turn it on I think about you. 😄
  8. Always to the rescue! I would love that - thanks! Marklabelle@comcast.net
  9. I did mine with a relay. I ran some doorbell wire from the fireplace to the HC800 in the basement or you could go wireless if you had power nearby. I think there is a thread here from my attempt. It works perfectly now.
  10. Hey guys, Got a new Samsung TV (UN55NU7100) and the WOL is way wonky. I've read some other threads, but it seems so hit and miss. I used SDDP and assigning just a static IP, but same results. It won't power up in anything less than 30 seconds or so. Off is fine, it's the ON functions. Also, it defaults to 0 volume every 3rd time or so. I've captured some of the LUA output to troubleshoot, but I can't seem to get this thing to power up quickly. Might have to resort to IR, since I have a Zigbee to IR laying around. Sending WOL... [ C4 <---- ]: SET_INPUT (INPUT: 1001) ExecuteCommand: SET_INPUT (INPUT: 1001) [ C4 <---- ]: ON (CONNECT: 1) [ C4 <---- ]: SET_VOLUME_LEVEL (OUTPUT: 7000, LEVEL: 0, ROOM_ID: 11) ExecuteCommand: SET_VOLUME_LEVEL (OUTPUT: 7000, LEVEL: 0, ROOM_ID: 11) [----> DEV ]: https://192.168.1.132:1515 id: 3262, method: directVolumeControl, jsonrpc: 2.0, params: {AccessToken: [ACCESS TOKEN], volume: 0} [----> C4 ]: VOLUME_LEVEL_CHANGED (OUTPUT: 7000, LEVEL: 0) [----> C4 ]: MUTE_CHANGED (OUTPUT: 7000, MUTE: false) [ DEV <----]: 0 Failed to post https://192.168.1.132:1515/: Couldn't connect to server [----> DEV ]: https://192.168.1.132:1515 id: 3263, method: muteControl, jsonrpc: 2.0, params: {mute: muteOff, AccessToken: [ACCESS TOKEN]} [ DEV <----]: 0 Failed to post https://192.168.1.132:1515/: Couldn't connect to server [----> DEV ]: https://192.168.1.132:1515 id: 3264, method: inputSourceControl, jsonrpc: 2.0, params: {inputSource: HDMI1, AccessToken: [ACCESS TOKEN]} [ DEV <----]: 0 Failed to post https://192.168.1.132:1515/: Couldn't connect to server HandleInputChangedResponse(nResponseCode, json) Starting Power On Delay Timer... Sending WOL... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Poll already in queue... Not putting poll in queue... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... Sending WOL... [ DEV <----]: Waiting for TV Power On... [ DEV <----]: TV Responding... [----> C4 ]: ON () Sending WOL... Poll already in queue... Not putting poll in queue... [----> DEV ]: https://192.168.1.132:1515 id: 3303, method: powerControl, jsonrpc: 2.0, params: {AccessToken: [ACCESS TOKEN], power: powerOn} [----> C4 ]: MUTE_CHANGED (OUTPUT: 7000, MUTE: true) [----> C4 ]: VOLUME_LEVEL_CHANGED (OUTPUT: 7000, LEVEL: 25) [ DEV <----]: 200 {"id":"3303","jsonrpc":"2.0","result":{"power":"powerOn"}} [----> DEV ]: https://192.168.1.132:1515 id: 3304, method: powerControl, jsonrpc: 2.0, params: {AccessToken: [ACCESS TOKEN], power: powerOn} [ DEV <----]: 200 {"id":"3304","jsonrpc":"2.0","result":{"power":"powerOn"}} [----> C4 ]: MUTE_CHANGED (OUTPUT: 7000, MUTE: false)
  11. but i could use power sensing through a wireless outlet and a generic game icon right?
  12. Is there a driver for Nintendo Switch? I got one for the kids for Christmas and was going to ask to have it added to the system, but I heard there is no driver from Control4. Mark
  13. I'm assuming that this driver is officially dead? It's now telling me again that the connection to the remote server is offline and that I need to activate with a valid key. Argh! Kiinda liked the geofencing - any other drivers out there?
  14. Ever since I had my system upgraded to 2.10 the main screen on all the tablets and panels in the house show the Comfort Icon with three dots. I can't see temperature in a given zone until I click on Comfort. I'm running two nests - one for upstairs and one for downstairs. I also noticed that the temperature shows three dots on the screen savers, when I choose to show the temperature. Anyone else experience this?
×
×
  • Create New...