Jon00 Event Viewer & Documenter for HS3

[cheeryfool]

Broken actions ?

Jon

I am guessing there's no way in the scripting interface to determine broken Actions?

What is seems to be doing now is reporting the good THEN actions upto the first broken one, then ignoring the broken one and any other after it, good or bad.

I couldn't see reference to this on this thread or in the help doc, but I definitely have broken events where the Actions only are broken, that are not showing up in the Broken filter list.

Is this another item to go in Known Limitations?

Cheers
James

[jon00]

That is correct. Once it detects a broken action, the returned code is absolute gibberish which I cannot do much with. I therefore just mark actions/triggers as broken. At least it pinpoints an issue which is better than nothing.

[cheeryfool]

Jon00 Event Viewer & Documenter

That is correct. Once it detects a broken action, the returned code is absolute gibberish which I cannot do much with. I therefore just mark actions/triggers as broken. At least it pinpoints an issue which is better than nothing.

I may be missing something here...



If a trigger or condition is broken, I see the event as Broken.



If only one (or more) actions are broken (triggers and conditions are good), then it doesn't show as broken for me.



If I select an event in that state, the detail in the report looks like an entirely good event, until you compare it alongside the actual HS3 event view, and you realise that everything from the broken action and below is missing in the script output.



Again, maybe this is beyond what is possible with what you have to work with from HST.

EDIT: Adding screenshots for clarity

1. Showing 5 actions on main HS3 Event view, with the middle one broken due to replaced dimmer:



2. Showing just the first 2 good actions from the Jon00 Event Viewer tab

[jon00]

Indeed, I have to filter out all this code, otherwise the page would be filled with it. When I get time, I will see if I can salvage anything extra to detect.

[cheeryfool]

Indeed, I have to filter out all this code, otherwise the page would be filled with it. When I get time, I will see if I can salvage anything extra to detect.

thanks

[cheeryfool]

Out of interest, is there a way for me to look at the raw gibberish maybe in debug mode?

[jon00]

No, it is just part of the code.

[cheeryfool]

Ok. Figured it probably was.

[jon00]

Anyway, good news! Rich has added the event voice command as a new scripting call. It will be available in Beta 407 so I will be able to add the missing metric to the list.

[cheeryfool]

[jon00]

I'll see what can be done.....

[cheeryfool]

I'll see what can be done.....

Thanks

[cheeryfool]

Added screenshots to post 78 for clarity on broken Actions

[jon00]

Version 1.0.3 is now available

Changes since 1.0.2

(Requires HomeSeer version 3.0.0.407 or higher)

Added support for displaying event voice commands
Improved coding to discover broken events
Added search capability for voice command events only
Added search capability for duplicate event voice commands

(For those still running Homeseer versions prior to 3.0.0.407, V1.0.2 is also supplied in the download zip).

[cheeryfool]

Changes since 1.0.2

(Requires HomeSeer version 3.0.0.407 or higher)

Added support for displaying event voice commands
Improved coding to discover broken events
Added search capability for voice command events only
Added search capability for duplicate event voice commands

(For those still running Homeseer versions prior to 3.0.0.407, V1.0.2 is also supplied in the download zip).

Awesome update Jon. Exactly what I was looking for. Found a couple more events with broken actions that I didn't know were broken. I also found 2 dupe voice commands. One of which I am struggling to remove off the report. I think I need to delete and create the event (it's a simple one). I think this is caused by some spurious behaviour in the event engine when you copy an event that has a voice command. It seems in some cases to be sticky even after you remove or replace the voice command. Sometimes in this case, when you click into the Voice command box, the pop-up contains the original copied value instead of the current replaced value. In any case, not your issue.

Thanks again for the quick turnaround and great new features.