disappearing trigger sensors

[johnnyt]

Am finding that sometimes when I click on an event to verify/edit it, the drop down list for sensors to check are both BLANK and need to be re-entered. This is an intermittent problem.

Attached are examples of events from the config file for which this has happened one more than one occasion.

[Michael McSharry]

If I understand what you are observing then I think a help desk ticket needs to be submitted. When it is time for HS to draw a event trigger on the GUI it will call a plugin to get the template for formatting the display. The actual values that go into the template user entry areas are inserted by HS. If the value is now blank rather than the previously entered selection then HS has lost track of the value to plug into the template. I'll work with HST, but it needs to start with the help desk to get their support.

[johnnyt]

Is a HS 1.7 problem worth reporting at this point? Will I just be told that fixes to HS 1.7 are no longer being done, or that "Plugin authors are being urged to go to web pages for config", as I was told a few months ago after reporting that in HS 2.0 mcsTemp opened up behind all my windows, did not show a task on my task bar, and locked the HS GUI window until I closed the plug-in?

[Michael McSharry]

I think you are correct about the support for HS1 being discontinued. It is also true that use of a Windows GUI is awkward under HS2. Only one interactive GUI window can be open at a time under HS2 so until the mcsTemperature one is closed the focus cannot be changed to any other HS2 window.

If you look at the Temperature Action and Trigger setup under HS2 it cannot be understood without a reference back to the HS1 screenshot because HS2 does not obey the formatting SDK for triggers and events. When the HS2 SDK is published then I can see what can be done about this. I'm not anxious to make additional changes at this time because new builds of HS2 tend to be a two step forward, one step backward evolution and analyzing what was broke in the one step backward is enough right now. I do not also want to introduce my changes at the same time to introduce uncertainty of my changes vs. HS2 build changes breaking something.

I'm still running HS1 as it satisfies my needs. In the long term users will need to migrate to HS2. It is just a matter for each to decide when the benefits of the new version outweigh the benefits of the old one.

[johnnyt]

I hear you about HS 2, although, as a user, I considered the builds I tried to be only ONE step forward and TWO steps back, in part because of my heavy reliance on mcsTemp and the problems mentioned here.

As well - bugs aside - a step back for me is the pain of having to configure a system (other than a small tweak or two) using web pages rather than the richer client behaviour of a GUI. Despite my 2 GHz dedicated server, the process of configuring my system from scratch (the recommended approach, I learned) seemed to take twice as long to do.

I did say to myself I would try again later (and did invest in it, i.e. paid for the upgrade) even though I don't see that particular pain point going away...