UI7 and Alternate Event Server

Developer's Corner General Dev Discussions
1

My VeraLite running 1.7.649. I have my event server recording events successfully to a database. If it matters, it’s running ASP Classic (don’t ask) on IIS in Windows 10, with an SQL Server 2014 Express backend. Everything seems to be going smoothly with the logging part.

I followed the wiki at [url=http://wiki.micasaverde.com/index.php/AlternateEventServer]http://wiki.micasaverde.com/index.php/AlternateEventServer[/url] using the instructions for UI7.

I noticed that Vera was sending the same events repeatedly, so I started deduping them in my database instead of just logging a bunch of redundant garbage.

Upon “tailing” the log, as indicated on AlternateEventServer’s wiki page (and removing the grep), I now see that it’s not treating my server’s response as a success for some reason, and retrying it later.

I’ve tried everything I can think of to determine the problem: Setting explicit Content-Type header (text/plain), specifying Content-Length, mixing up the “1234” in the JSON response with other numbers, including 0, etc. Attached is a screenshot of the log being tail’ed as it fires off an event or two. You can see my server’s response is exactly as specified in the wiki, and the Vera doesn’t seem to like it for some reason.

Can someone please clue me in as to what I might be doing wrong? My brain is fried.

2

Yes, this is exactly what happened to the alternate event server in the EventWatcher plugin. I’ve never got to the bottom of it. Had to edit the user_data.json file to remove the reference to the alt server in order to stop the log messages.

3

Ok, cool. I thought I was going nuts. I’m glad I asked, otherwise I would have kept slamming my face into my desk.

I’m already deduping the messages I see, so it’s not really a big deal. Thanks!

4

Try to set your response type from your server to “text/plain”. Not “application/json”. With that one change, I don’t see the retry messages anymore in logs.