OpenZWave / open-zwave-control-panel

UNMAINTAINED - We are looking for someone to maintain ozwcp! The OpenZWave Control Panel (ozwcp for short) is an application built on the OpenZWave library that permits users to query, manage and monitor Z-Wave nodes and networks. It provides a web based user interface using AJAX principles.
Other
130 stars 72 forks source link

Compiled under Window 7 Visual Studio 2015. Does not update. #34

Open robertja52 opened 8 years ago

robertja52 commented 8 years ago

I got open-zwave-control-panel to compile and run under windows7 using visual studio 2015 and pthread-win32. All open zwave library functions appears to work. The web page shows up and I can connect to a controller. The web page does not update (log output, controller status). The log file shows that I have retrieved a homeid.

/tmp has been modified to use the TEMP environmental variable instead since /tmp doesn't exist in Windows. Wiresharking connection shows that the data appears to be sent to the browser (chrome or firefox), but doesn't display. Any ideas on how to figure out what is wrong?

Fishwaldo commented 8 years ago

Anything in the Java Console etc on the browser?

Can you post the log somewhere that it dumps to the console. Might give us a idea where its going wrong.

robertja52 commented 8 years ago

Java Conole didn't open. Is this application even using Java? In Firefox developer console I get a junk after document element error for the file poll.xml Firefox thinks the file contains. Notice the oll> at the end of the document.

<?xml version="1.0" encoding="utf-8" ?>
<poll homeid="eedf2371" nodeid="1" sucnodeid="0" nodecount="1" cmode="Primary" save="1" noop="0">
    <log size="0" offset="12506"></log>
    <admin active="false" />
    <update />
</poll>
oll>
Fishwaldo commented 8 years ago

The code writes temporary files to the "temp" directory, that it then serves upto the browser. I would check your changes around the temp directory changes....

veleek commented 6 years ago

Given this was open two years ago and there was no update from the bug creator, this bug should be closed as no-repro.