Path name on Windows HS2

[dweingartner]

I'm trying to configure the Failure Summary Notification event (General Devices) on an HS4 Pro Edition 4.1.10.0 (Windows) system.
The system is remote so I don't have directory visibility at this time.
The event will not accept the attachment file location documented in the guide:
/html/SDJ-Health/SDJ-Health General Report-0.html

[SteveMSJ]

I'm trying to configure the Failure Summary Notification event (General Devices) on an HS4 Pro Edition 4.1.10.0 (Windows) system.
The system is remote so I don't have directory visibility at this time.
The event will not accept the attachment file location documented in the guide:
/html/SDJ-Health/SDJ-Health General Report-0.html

Hi
There is a rather small note on page 15 of the guide about this. HS4 had a problem displaying the reports as a web page with spaces in the file name. To get round this I had to make a change so that the file names have no spaces if you are running on HS4. On HS3 I kept the spaces so as not to break existing installations. The example events in the guide are for HS3. I will add a bigger note in the guide as a warning under the example event.

Try changing the file name in your attachment path to miss out the spaces and see if it works ok.

Steve

[dweingartner]

Steve,
Thanks for the quick reply. Yes, I realized that space issue soon after posting. I should have realized since I have it working on my own Linux system. I fixed it on the Windows machine and it's working.

However, on the Windows system, the only attachment path name that I can get HS4 to accept is:
C:\Program Files (x86)\HomeSeer HS4\html\SDJ-Health\SDJ-HealthGeneralReport-0.html

vs the format for my Linux ZeeS2:
html/SDJ-Health/SDJ-HealthGeneralReport-0.html

back slash vs forward slash, and full path name.

I admit this is probably just my ignorance of Windows.

[SteveMSJ]

Steve,
Thanks for the quick reply. Yes, I realized that space issue soon after posting. I should have realized since I have it working on my own Linux system. I fixed it on the Windows machine and it's working.

However, on the Windows system, the only attachment path name that I can get HS4 to accept is:
C:\Program Files (x86)\HomeSeer HS4\html\SDJ-Health\SDJ-HealthGeneralReport-0.html

vs the format for my Linux ZeeS2:
html/SDJ-Health/SDJ-HealthGeneralReport-0.html

back slash vs forward slash, and full path name.

I admit this is probably just my ignorance of Windows.

Yes, back slashes in Windows paths. Mine don't show the full path in Windows HS4 but they are events that were upgraded from HS3. There seems to be some inconsistency when entering paths in HS4 events. It is not desirable to have the full path, it should be relative, but if that is all that works then ok.

Steve

[SteveMSJ]

Yes, back slashes in Windows paths. Mine don't show the full path in Windows HS4 but they are events that were upgraded from HS3. There seems to be some inconsistency when entering paths in HS4 events. It is not desirable to have the full path, it should be relative, but if that is all that works then ok.

Steve

FYI I've done a bit more experimenting in Windows and it is due to the buggy HS4 Event interface, It actually works both ways, i.e. if you enter the full path for the attachment or just the relative path starting \html. However, with the relative path you can't collapse the action in the event, i.e. when you click on the Save icon it stays expanded. That normally means there is an error in the event but it actually works fine and sends the email. The attachments show two events which both work fine but the one with the relative path won't collapse.

It's unacceptable that there isn't a browse feature when adding an attachment in HS4 (unless I'm missing something). So much of the interface appears unfinished.

I've given up reporting small inconsistencies in HS4 to HST until they make significant progress on the outstanding bugs. I am applying work rounds in my plug-ins to cope with issues that HS4 throws up but I am not embarking on a full convert for now. I won't start to feel any pressure until HST have at least converted their flagship Z-Wave pi to HS4. How long has it been now, at least a year?

If you have any other issues please post them I will always try to help. I am actually in the middle of a fairly significant upgrade to the 'General Devices' section of the pi, adding filtered log messages to each monitored interface.

Steve