Where do I report a Z-Wave plugin bug?

[timmymac123]

In case the appropriate person is watching...

z-Wave plugin version 4.1.0.1 Beta
HS Version 4.2.16.0

Set HomeSeer to NOT use port 80 (at least on Linux).
I was using 8088 as an example.

I then go to a main (z-wave) Device, Then click the Zwave tab. This shows the following:

When the port was set to 8088, all these links default to port 80 or something like:
http://x.y.z.a/Z-Wave/device-diag.ht...Optimize_Light
instead of
http://x.y.z.a:8088/Z-Wave/device-di...Optimize_Light

I tried all the links. Full optimize, rescan, replace node, remove bad node....all the same.
I could not even run the "Generic Configuration Parameters" and read them. They just timed out.

I reset HomeSeer to use port 80 and then restarted HomeSeer and now all those links works.
Pretty obvious this is a bug.

Lets hope for a simple fix in the next update?

[TC1]

These are User-to-User forums, HST personnel do not normally monitor them.

Open a trouble ticket or bug report here:
HomeSeer - Service Desk

[timmymac123]

Thank you!. Case opened

[SteveW]

I thought HST pulled that beta for further internal testing?

[timmymac123]

No idea about that. It was available when I refreshed the plugin page (last week maybe). I did manage to update to 4.1.0.2 last night after the post. Still had the same issue.

[TC1]

Looks like beta 4.1.0.2 is indeed available in the plugin download section. Seems like it was released without any fanfare.

[timmymac123]

For what it's worth, I tried posting to that link you gave me last night.
I was told to bugger off....it was very polite though.
I was told that particular forum is for "stable" release release products, not Beta.....

SO, where do I actually post about issues with "BETA" plugins?

[timmymac123]

And I will answer my own question...

Just send an email to support@homeseer.com

[randy]

I thought HST pulled that beta for further internal testing?

It was. There are some issues and it was never "officially" offered. There was a way to do an end run around HS and get it anyway. I think it was if you were running 3.0.10.0 and looked for an upgrade It is also common not to support beta releases. They are to be installed at your own risk.

[timmymac123]

I certainly didn’t do any end around. I suspect it was all timing when I did the update scan.

been running the 4.0 beta since it came out earlier this year. Try to mostly keep up to date

[randy]

I certainly didn’t do any end around. I suspect it was all timing when I did the update scan.

been running the 4.0 beta since it came out earlier this year. Try to mostly keep up to date

I understand. I was just repeating what Rich posted earlier when he was surprised to find users running it. He stated it was "for internal testing only'.

[spud]

timmymac123, this is a HS4 bug, it is now tracked internally as HS-1754. It should be fixed in the next HS4 release.
Thanks for reporting.