
Morris Hansen
Members-
Posts
199 -
Joined
-
Last visited
Everything posted by Morris Hansen
-
Yes they continue to work.
-
I have the same issue with some of the devices going offline. It seemed to be associated to one emulator (I am running 3 different ones). Today I only show one device offline. For me, it does not seem to be a specific device type. First it was everything on one bridge, today it is one light.
-
I was able to download the zip files and extract the individual files without any problems. I am using Windows 7. On Windows, you should be able to see the individual files in the zip and actually extract and look at the file in Notepad. I didn't try the import but it should work. It did awhile ago.
-
Dean, The first step is getting your ISY working with Sonos. Others have documented this and it is available on the ISY Wiki Once you have the ISY able to control one of your zones, you just need to add a network resource for each zone and each function per zone. I have 7 zones and 42 different network resources. I use Play, Pause, Mute, Unmute, Previous, and Next. I have not added the volume up and volume down yet but that would be 2 additional resources per zone. I then added 3 different programs per zone. One program controls Play and Pause, the second controls Mute & Unmute and the third does Previous & Next. The reason I used it this way is because each pair have common functions. In each program I put one function in the Then clause and the other in the Else clause. Sonos Deck Play - [ID 0004][Parent 0011] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Resource 'Sonos Deck Play' Else Resource 'Sonos Deck Pause' Once you have all these programs created, you then use Barry's configuration tool. This will find all the devices/scenes/programs in the ISY. For each program you want, create the friendly name, assign it to the emulator, etc. Once you have all the programs mapped, update the Echo and you should be working. You will notice that telling Alexa to turn on the device will actually run the Then part of the program. Turning off will run the Else part. Since the functions are similar, it is not that hard to remember. I may change some of the friendly names and everyone will use what works for them. Alexa, Turn On Sonos Deck, this will execute the Play Network Resource on the Deck zone. Notice I left Play out of the friendly name since this is the primary command. Alexa, Turn Off Sonos Deck, this will execute the Pause Network Resource on the Deck zone. Alexa, Turn On Sonos Deck Mute, this will execute the Mute Network Resource on the Deck zone. Alexa, Turn Off Sonos Deck Mute, this will execute the Unmute Network Resource on the Deck zone. Alexa, Turn On Sonos Deck Next, this will execute the Next Network Resource on the Deck zone. Alexa, Turn Off Sonos Deck Next, this will execute the Previous Network Resource on the Deck zone. I left Sonos in the friendly name as it acts kind of like a skill. There is a lot of Network Resources and Program but mostly it is copy and paste so not that complicated. Morris
-
Dean, I will describe this in more detail later. I had almost everything typed in and then fat fingered my typing and lost it all. Will need to do this later when I return home.
-
I have Sonos control working great using Alexa with the ISY in the middle. Need to setup each Sonos device and function (play, pause, etc) as a separate network resource. It is very responsive with next to no delay.
-
First I would like to echo what has been said multiple times on this thread, great work on everyone working through the issues that come up with trying to integrate all the disparate pieces. I wanted to contribute my part on what I don't think has been covered in the 46 pages of this thread. And I have read the pages multiple times. I have had my ISY integrated with Elk for several years. Works well. On my Elk I have 3 thermostats and I am able to control them easily through the ISY. So today I wanted to get the Echo to control my thermostats. After a few attempts, looking at packet debugs, etc. I got it working. Add a device using Barry's configuration tool. Changed the Friendly name to something easy to use, Main Thermostat, Upstairs Thermostat, etc. DeviceType needs to be Dimmer The On URL looks like this: rest/elk/tstat/1/cmd/6?value\u003d${intensity.math(X/255*100)} The 1 is for my first thermostat, the 6 is for Heat and the \u003d is hex for an equals sign and then I needed to convert the requested temperature back to something the ISY/Elk understands. For Cool setpoint, change the 6 to a 5. As others have indicated, to use the Echo for thermostat control, say "Alexa, Set Main Thermostat to 68" I also use my ISY to control my Sonos. I have setup Network Resources within the ISY for each Sonos zone and what I want the zone to do (ie. play, pause, mute, unmute, etc.) To get this working with the Echo, I did the following: Create a program on the ISY, I did not put anything in the If section, For the Then section, I entered the Network Resource for the specific zone I want to play, and finally in the Else section, I put the Resource for Pause. I did a separate program for each zone I wanted to play/pause and the same for mute/unmute. Now in Barry's tool, the programs I created above show up, I added the program and made the On URL be the Then section and the Off be the Else section. I used a Friendly name like Sonos Deck, Sonos Family Room, etc. To use Echo, I say "Turn Sonos Family Room On" and it starts playing whatever is in the queue. "Turn Sonos Family Room Off", pauses whatever is playing. To play next track, "Turn Sonos Family Room Next On" You could easily drop Sonos from the friendly names. I still need to figure out the naming convention I want to use. The last step I did was to have a program in the ISY that shuts off all devices (lights) on each floor, turns off the Sonos, and set the temperature for sleeping. "Alexa, Turn Bedtime On" and everything shuts down and adjusts the thermostats. I can't wait to see what others come up with and what Izzy will add to the solution.
-
I have everything ready to put together the emulator/bridge solution that is being discussed here but if the "official" support is coming in a couple days I will continue to hold off. Having a timeline would be very helpful, though not sure if that is possible.
-
I have been following this thread with great interest. My echo just arrived today. When you say to dim or brighten without a value, how much does it change and is this configurable?
-
Michel gave me some new code without the semi-colon and it works. The support on here is outstanding. Thanks Michel
-
Finally made some progress. I simulated a SMTP client by telneting into the SMTP server and entering the commands myself. What I was able to determine is: - semi-colon after the Mime-version doesn't matter. - it does seem to matter that there cannot be a semi-colon after the charset. I tried utf and iso, both worked without a semi-colon and both failed with a semi-colon. - Mime-Version:1.0 works. The space after the colon doesn't need to be there and neither does it need to be capitalized. - Mime by itself works. Doesn't need content type - It worked without any content encoding. So it appears that AT&T doesn't like the semi-colon after the charset. At least I can recreate it at will.
-
Unfortunately that didn't fix it. This morning I enabled my emails again on the Elk and captured what it is sending to ATT. The emails from Elk work. Thanks, 220 m1plsmtpa01-06.prod.mesa1.secureserver.net ESMTP EHLO mydomain.net 250-m1plsmtpa01-06.prod.mesa1.secureserver.net hello [98.245.240.129], secureserver.net 250-HELP 250-AUTH LOGIN PLAIN 250-SIZE 31457280 250-PIPELINING 250-8BITMIME 250 OK AUTH LOGIN 334 VXNlcm5hbWU6 xxxxxxxxxxxxxxxx 334 UGFzc3dvcmQ6 xxxxxxxxx== 235 ... authentication succeeded MAIL FROM: 250 sender ok RCPT TO: <10digitnumber@mms.att.net> 250 <10digitnumber@mms.att.net> recipient ok DATA 354 enter mail, end with "." on a line by itself MIME-Version: 1.0 To: 10digitnumber@mms.att.net From: security@mydomain.net Cc: Subject: Email Alert X-Mailer: Allegro Software RomMailer /4.01 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Incoming Driveway . 250 j2cZ1k0012oCq5N01 mail accepted for delivery QUIT 221 m1plsmtpa01-06.prod.mesa1.secureserver.net closing connection
-
Michel, I think I tried html before but just to make sure I did several more tests. I am still not able to receive anything that is not the default or test message. Morris
-
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:= 14px; font-family: Calibri, sans-serif; "> v> My Name Morris@mydomain.net =div>
-
I setup a packet capture. Hopefully this will help. The first section below is when a test message is sent. The second section is when sending from the program. It appears the setup at the beginning is different and there is extra data (Mime-Version....) in the actual data when it doesn't work. 220 m1plsmtpa01-02.prod.mesa1.secureserver.net ESMTP EHLO [192.168.1.18] 250-m1plsmtpa01-02.prod.mesa1.secureserver.net hello [98.245.240.129], secureserver.net 250-HELP 250-AUTH LOGIN PLAIN 250-SIZE 31457280 250-PIPELINING 250-8BITMIME 250 OK AUTH PLAIN 334 AHNlY3VyaXR5QDUzMzcubmV0AHYxMGplZXA= 235 ... authentication succeeded MAIL FROM: 250 sender ok RCPT TO: <10digitnumber@mms.att.net> 250 <10digitnumber@mms.att.net> recipient ok DATA 354 enter mail, end with "." on a line by itself X-Mailer: ISY Mailer v1.0 (http://www.universal-devices.com) From: Home Security To: 10digitnumber@mms.att.net Date: Mon, 31 Dec 2012 20:00:35 -0700 Subject: ISY Test 2012/12/31 20:00:34 Test message from ISY Home Automation device. . 250 iT0X1k00F2oCq5N01 mail accepted for delivery QUIT 221 m1plsmtpa01-02.prod.mesa1.secureserver.net closing connection ===================================================== 220 p3plsmtpa01-07.prod.phx3.secureserver.net ESMTP EHLO [192.168.1.18] 250-p3plsmtpa01-07.prod.phx3.secureserver.net 250-AUTH LOGIN PLAIN 250-8BITMIME 250 PIPELINING AUTH PLAIN 334 AHNlY3VyaXR5QDUzMzcubmV0AHYxMGplZXA= 235 Authentication succeeded. MAIL FROM: 250 Sender accepted. RCPT TO: <10digitnumber@mms.att.net> 250 Recipient accepted. DATA 354 End your message with a period. X-Mailer: ISY Mailer v1.0 (http://www.universal-devices.com) From: Home Security To: 10digitnumber@mms.att.net Date: Mon, 31 Dec 2012 20:55:44 -0700 Subject: Driveway Incoming Alert : Alert Mime-Version:1.0; Content-Type: text/plain; charset="utf-8"; Vehicle entering the driveway . 250 Accepted message qp 5088 bytes 440 QUIT 221 Good bye.
-
I appreciate the support. Without seeing the actual traffic between the ISY and the SMTP server, it may be tough to figure out. What is so odd is that the test email's work, just nothing from a program or with non-default content. Here is my error log for the last couple of days. I didn't see any of the error number (50000) you indicated before. Do any of these make sense? Sun 2012/12/30 08:48:51 AM System -5012 49 Sun 2012/12/30 09:17:47 AM System -110022 /CONF/MAIL/5.NTC Sun 2012/12/30 09:17:47 AM System -110012 /CONF/MAIL/5.NTC Sun 2012/12/30 09:19:36 AM System -110022 /CONF/MAIL/5.NTC Sun 2012/12/30 09:19:36 AM System -110012 /CONF/MAIL/5.NTC Sun 2012/12/30 11:03:31 AM System -140005 CLI-WBug Sun 2012/12/30 08:55:31 PM System -140005 CLI-WBug Sun 2012/12/30 09:05:32 PM System -140005 CLI-WBug Sun 2012/12/30 09:25:31 PM System -140005 CLI-WBug Sun 2012/12/30 10:05:33 PM System -170001 [uDSockets] RSub:27 error:6 Sun 2012/12/30 10:05:38 PM System -5012 50 Mon 2012/12/31 10:00:12 AM System -60006 n/a Mon 2012/12/31 10:36:49 AM System -50001 -19 Mon 2012/12/31 10:55:26 AM System -140005 CLI-WBug Mon 2012/12/31 10:57:26 AM System -140005 CLI-WBug Mon 2012/12/31 10:59:26 AM System -140005 CLI-WBug Mon 2012/12/31 11:01:27 AM System -140005 CLI-WBug Mon 2012/12/31 11:03:27 AM System -140005 CLI-WBug Mon 2012/12/31 11:05:26 AM System -140005 CLI-WBug Mon 2012/12/31 12:03:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:23:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:25:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:27:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:29:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:31:27 PM System -140005 CLI-WBug Mon 2012/12/31 02:33:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:35:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:37:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:39:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:41:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:43:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:45:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:47:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:49:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:51:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:53:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:55:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:57:26 PM System -140005 CLI-WBug Mon 2012/12/31 02:59:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:01:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:03:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:05:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:07:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:09:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:11:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:13:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:15:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:17:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:19:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:21:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:23:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:25:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:27:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:29:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:31:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:33:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:35:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:37:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:39:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:41:29 PM System -140005 CLI-WBug Mon 2012/12/31 03:43:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:45:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:47:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:49:27 PM System -140005 CLI-WBug Mon 2012/12/31 03:51:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:53:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:55:25 PM System -140005 CLI-WBug Mon 2012/12/31 03:57:26 PM System -140005 CLI-WBug Mon 2012/12/31 03:59:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:01:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:03:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:05:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:07:29 PM System -140005 CLI-WBug Mon 2012/12/31 04:09:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:11:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:13:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:15:26 PM System -170001 [TCP-Conn] -1/-140002, CLI-WBug Mon 2012/12/31 04:17:29 PM System -140005 CLI-WBug Mon 2012/12/31 04:19:27 PM System -140005 CLI-WBug Mon 2012/12/31 04:21:26 PM System -140005 CLI-WBug Mon 2012/12/31 04:21:48 PM System -5012 51 Mon 2012/12/31 04:28:53 PM System -50001 -19 Mon 2012/12/31 05:30:36 PM System -50001 -14
-
Michel, I do have my own SMTP server setup. The same one I have configured in Outlook. I have tried another email account though it is on the same domain with the same SMTP server. Same results. I switched to the default SMTP server and it acted the same. All testing shows that I get messages to @txt.att.net and my email address but nothing other than the test message will go to @mms.att.net I also sent a message from Outlook using the same smtp account and I was able to send a message to @mms.att.net without any issues.
-
I sent the same message that worked yesterday. (ie. default subject of program name and customized body). I received a message at txt.att.net and email but did not get any message to mms.att.net. Both of the received messages did have the customized body. So to be sure of my testing yesterday, I did another test directly to mms.att.net by itself. The same message that I used yesterday did not work today. I created another similar custom notification and it did not work either. I may have just gotten lucky yesterday. I can still send test messages to mms.att.net. Nothing with any content seems to work today.
-
I was able to get a message to work through mms.att.net If I put the default subject (which is the program name), this works sort of. I get the default header information but none of the message body comes through. Here is what I got to work but again the body did not get sent.
-
Not sure what you mean by static header. Are you referring to the Subject? I have tried both leaving the subject blank and putting something in there. Here is what my customization looks like.
-
Appreciate the help. I have a Subject of 'Driveway Activity' and the body is 'Vehicle entering the driveway at ${sys.time12} on ${sys.date}' all formatted as text. I changed the body to be Hello and still did not get any message. Also tried the HTML format. I tried a different customization message and it did not work either. So I then tried a message with content of Default and that worked. So it has something to do with the customization. I am not seeing any error's in the error log.
-
I forgot to add that if I test the notification from the Configuration,Emails/Notifications,Settings/Groups tab, it works great. It only fails if I do a test my THEN part of a program. If I change the email address to txt.att.net, my program tests just fine. I am able to send emails just fine to mms.att.net from the same email account I am using on the ISY as well as other email accounts. I am not getting any errors on the screen or in the error log. There is only one line in my THEN statement and that is Send Notification to 'Cell' content 'Driveway Incoming'
-
I have been migrating my notifications from Elk over to the ISY. Everything for the most part is working great. One item I can't seem to figure out is why I am not able to actually send an email to my cell number@mms.att.net. It works fine to @txt.att.net. Using my email client, I can send just fine to the mms address. The reason I want to use mms.att.net is to get rid of the annoying sequential numbers that show up on text messages to @txt.att.net. If I use MMS, the messages show up as my email address which I can then assign different ring tones to. I can't seem to find where I have anything wrong. I am only changing the destination email address and it goes from working to not working with no errors. Any ideas?
-
Release 3.3.7 (RC4) Is Now Available
Morris Hansen replied to Michel Kohanim's topic in Previous Releases
edit: Upgrading Java seemed to fix it. Not sure if this is a new issue or not but when I use the admin console to change the Elk thermostat settings, the changes are implemented but the UI does not show the new temp set point. I know this use to work but not sure when it stopped working. -
Release 3.3.7 (RC4) Is Now Available
Morris Hansen replied to Michel Kohanim's topic in Previous Releases
Upgraded without any issues