We have been developing these new and exciting features for the UCM/ETH03;
- Sending of emails for up to 4 email addresses for 32 Alarm Types
- Synchronisation of Comfort\'s date and Time with an Internet Time Server
- Simultaneous connection to 2 ports so 2 phones, tablets or computers can connect as a time. Currently only 1 connection at a time is allowed.
These are ready for beta testing prior to release. We would like to invite users with UCM/ETH03 to test the new features
Minimum Configurations (updated)
Please note that all the above software and firmware are beta versions
Some screenshots to show how it works;
Comfort Server Manager 2.0.1
select the IP address on the left (if there are more than 1 UCM/ETH03). The IP address of the UCM/ETH03 is shown on the right pane on top
The 2 ports each with their own independent idle time-outs are shown below. If not used the 2nd port should be left empty
SNTP Setting
Check that the local time is correct. Select one of the servers in the NTP Server Pool. These are a list of International NTP servers that provide the local time adjusted for Daylight saving where applicable
The NTP Synchronize Interval is the interval for the updating of time to Comfort. 60 minutes is the recommended interval athough you can set a shorter time for testing.
\"Send Time to Comfort\" should be checked if the time should be sent to Comfort.
Email settings
SMTP Server: enter the address of a SMTP server
Port: 25 or 587 (for STARTTLS)
User name: eg john@yahoo.com for sending of the email
email From: the name to be displayed in the FROM line of the email
email Subject: what is to be displayed in the SUBJECT line of the email
To Users 1 to 4: enter the email addresses of up to 4 people
Alarms: check the boxes 1 to 4 for the emails to be sent for each Alarm Type triggered
Let us know if you have any problems with the emails settings
there are email services like
http://www.smtp2go.com/ which you can sign up for an account in order to send emails from their server. Up to 20 emails a day are free
Hi Ident, great to hear these new features are moving on.
I\'ve just been trying them, but having some issues.
I have upgraded all of the components to the versions you list. That went well.
Firstly I configured SNTP. I am using pool.ntp.org and also tried Europe.pool.ntp.org. I have the box checked to send to Comfort.
I then reset Comfort and get a date time of 29 Aug 13, which is the usual startup date
Even after waiting the 10 mins I had set the interval to the date/time did not update. I had my IP address statically configured, and note there is nowhere to define the correct DNS server address, so I tried DHCP which will supply DNS servers to the clients.
I get the same problem.
Then onto email. I have an Exchange 2007 server on the same network as comfort. It will allow SMTP email relay from IP addresses on the same subnet.
After defining the sender and recipient etc as detailed in the instructions I found in the Exchange SMTP receive log that Comfort is trying to send emails, but failing.
It fails during the SMTP negotiation with an unrecognised authentication type message in the Exchange server logs
for reference the Exchange server here is on 10.151.110.20 and the ETH 3 module on 10.151.110.250
2014-05-02T19:19:58.063Z,SERV1\\Allowed Relays,08D1306798FAD288,1,10.151.110.20:25,10.151.110.250:1032,*,SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders,Set Session Permissions
2014-05-02T19:19:58.063Z,SERV1\\Allowed Relays,08D1306798FAD288,2,10.151.110.20:25,10.151.110.250:1032,*,SMTPSubmit SMTPAcceptAnyRecipient SMTPAcceptAuthenticationFlag SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender BypassAntiSpam BypassMessageSizeLimit SMTPAcceptEXCH50 AcceptRoutingHeaders,Set Session Permissions
2014-05-02T19:19:58.064Z,SERV1\\Allowed Relays,08D1306798FAD288,3,10.151.110.20:25,10.151.110.250:1032,>,\"220 mail.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 2 May 2014 20:19:57 +0100\",
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,4,10.151.110.20:25,10.151.110.250:1032,,250-mail.mydomain.com Hello [10.151.110.250],
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,6,10.151.110.20:25,10.151.110.250:1032,>,250-SIZE 10485760,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,7,10.151.110.20:25,10.151.110.250:1032,>,250-PIPELINING,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,8,10.151.110.20:25,10.151.110.250:1032,>,250-DSN,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,9,10.151.110.20:25,10.151.110.250:1032,>,250-ENHANCEDSTATUSCODES,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,10,10.151.110.20:25,10.151.110.250:1032,>,250-AUTH,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,11,10.151.110.20:25,10.151.110.250:1032,>,250-8BITMIME,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,12,10.151.110.20:25,10.151.110.250:1032,>,250-BINARYMIME,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,13,10.151.110.20:25,10.151.110.250:1032,>,250-CHUNKING,
2014-05-02T19:19:58.073Z,SERV1\\Allowed Relays,08D1306798FAD288,14,10.151.110.20:25,10.151.110.250:1032,>,250 XEXCH50,
2014-05-02T19:19:58.090Z,SERV1\\Allowed Relays,08D1306798FAD288,15,10.151.110.20:25,10.151.110.250:1032,,504 5.7.4 Unrecognized authentication type,
2014-05-02T19:19:58.096Z,SERV1\\Allowed Relays,08D1306798FAD288,17,10.151.110.20:25,10.151.110.250:1032,,221 2.0.0 Service closing transmission channel,
2014-05-02T19:19:58.096Z,SERV1\\Allowed Relays,08D1306798FAD288,19,10.151.110.20:25,10.151.110.250:1032,-,,Local
Extra note - time sync did eventually work - very nice. This is with the ETH03 module getting it\'s IP address via DHCP. I\'ll test with it statically configured, as the ETH03 will not receive DNS settings then.
The ETH03 can be static, it does not need DHCP
what email authentication does the Exchange aerver require?
Exchange 2007 is actually configured to accept a non authentication connection from the same subnet it is on. But it seems to be not possible to configure the SMTP settings on ETH03 without username/password?
I managed to solve the Exchange problem by defining a new SMTP connector that allowed basic authentication. For a future release it might be worth considering a check box to allow unauthenticated SMTP.
When ETH03 is not using DHCP where does it obtain it\'s subnet mask and DNS server information?
Also as a suggestion if the ETH 03 module is reset or sees that Comfort has been reset could you maybe try an SNTP sync at that point? From my testing it looks like after a reset you have to wait one full polling cycle for the first SNTP sync. One just after reset would be useful.
Having tested more I find that if the ETH03 module is configured with a static IP address it will not sync with the SNTP server, however if I change to a DHCP assigned address it will. Hence my question about where the ETH03 module gets DNS server info from when statically configured. I am wondering in that mode if it is unable to resolve the SNTP server name and then failing.
The next version will allow sending without authentication
When the ETH03 is on static IP, there is a Gateway field
I think this is where it gets the DNS
I have no problem with SNTP with a static IP
Good news about non-authenticated SMTP in a future release.
I see what you mean about a Gateway IP address when not using DHCP, however there is nowhere to enter the subnet mask and DNS server when in static mode. Both of these would also be required.
When in DHCP mode they will come from the DHCP server, and I suspect this is why time sync with SNTP is possible in DHCP mode but doesn\'t work in Static IP mode, since the ETH03 card does not have a DNS server that it can use to resolve the name of the NTP server.
I wonder if in static mode the ETH03 card is making an assumption that the gateway device (ie router) is also the DNS server. That might be the case for some installations, but it\'s not correct to assume it. In my installation DNS is provided by a dedicated DNS server and not the router. Therefore I\'d encourage you to add two more fields when in Static IP mode:-
Subnet mask (shouldn\'t assume it\'s 255.255.255.0 in all cases)
DNS server (shouldn\'t assume it\'s the same as the gateway as often it is not)
Could you also include a \'Default\' or \'Clear\' option as once you enter eMail settings there is no way to clear it.
The same goes for SNTP if the client decides against using it. You can disable sending updates to Comfort but it will continue to poll. Perhaps a option in the dropdown list.
Ingo
Superb. I can confirm this update has fixed the issue I had when using a fixed IP address on the ETH03 module, when the DNS server was not provided by the router. Originally in this mode SNTP would not work. It works correctly now.
Adding names works perfectly also.
Though I was able to type those names into server manager, which I didn\'t expect to be able to do if they are read from Comfort from Security-> Sign in codes.
Great to see this coming on so quickly.