Indigo DomoticsSoftware Support and Home Automation Forumhttp://static.indigodomo.com/www/images/micro_eye.png2021-09-22T14:42:06-06:00https://forums.indigodomo.com/feed.php?f=2612021-09-22T14:42:06-06:002021-09-22T14:42:06-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=205682#p205682I’m sure that wouldnt’t be too complicated. But as I’m not actively using Indigo at the moment I won’t be maintaining this plugin unfortunately. The source is on GitHub should anyone want to develop this.
Sent from my iPad using Tapatalk
]]>2021-09-22T13:37:54-06:002021-09-22T13:37:54-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=205680#p205680One questions that I still have is how to send the reports as emails. I am using the Email+ plugin; its SMTP device is not recognized as a "Better EMail" device. Any way to make it work with Email+?
Thanks, Mark
]]>2019-10-16T10:08:10-06:002019-10-16T10:08:10-06:00https://forums.indigodomo.com/viewtopic.php?t=23051&p=183039#p183039 I am not sure if I should post this in this plugin section or in the script section. Anyways:
I have a Notification category that has a minor problem after I converted my Applescripts to Python, I use an action group that plays a sound via afplay before an announcement is spoken.
This AG is set in the "before speech" option of the notification category. This AG used to play a common sound using the "do shell script" statement calling afplay in an embedded AppleScript. So the sound was played before the announcement was spoken by the OS. After convertion that mini scipt to python I realize, that the sound and the spoken text are produced simultaneously - I suppose the phython script runs in an additional thread so both are ececuted nearly at the same time. What can I do?
]]>2018-07-27T05:20:59-06:002018-07-27T05:20:59-06:00https://forums.indigodomo.com/viewtopic.php?t=21068&p=164210#p164210 I have just installed your fantastic plugin, thanks!
I created a trigger to send me an e-mail when there is a slow node response (or no ack). This triggers a full report sent by e-mail and logged to Indigo log.
Is there any way I can include the "ZEAL Warning FL Lounge IR Motion 155" no ACK on sent z-wave command: 01 09 00 13 13 02 80 02 25 6B 38" below in the e-mail to see what device triggered the action?
Thanks! Peter
Code:
27 Jul 2018 at 12:45:34 ZEAL Warning "FL Lounge IR Motion 155" no ACK on sent z-wave command: 01 09 00 13 13 02 80 02 25 6B 38 Trigger Slow node reponse Action Group zeal full report ZEAL
Sent from my iPad using Tapatalk
]]>2018-07-17T15:09:04-06:002018-07-17T15:09:04-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=163652#p163652
]]>2018-07-17T15:05:40-06:002018-07-17T15:05:40-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=163651#p163651
Sent from my iPad using Tapatalk
]]>2018-07-17T15:02:51-06:002018-07-17T15:02:51-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=163650#p163650
]]>2018-07-17T14:50:47-06:002018-07-17T14:50:47-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=163648#p163648 If you disable the plugin or install the latest update you won’t get those notifications
Sent from my iPad using Tapatalk
]]>2018-07-17T14:45:17-06:002018-07-17T14:45:17-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=163647#p163647 "A new update of ZEAL plugin is available and can be updated from the plugin menu within Indigo"
I am getting multiple notices such as this. How can I unsubscribe?
]]>2018-03-29T12:18:31-06:002018-03-29T12:18:31-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=157814#p157814
]]>2018-03-04T05:04:22-06:002018-03-04T05:04:22-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=156036#p156036version 0.3.7 that disables update checking for now, due to the ssl errors caused by a change at github. The new Indigo store has an update checking mechanism, and I'll have a look at implementing that for update checking, rather than using github.
]]>2017-11-30T16:27:28-06:002017-11-30T16:27:28-06:00https://forums.indigodomo.com/viewtopic.php?t=19710&p=150339#p150339Skjermbilde 2017-11-30 kl. 23.14.00.png
Then an action for example like this can be added to the trigger: Skjermbilde 2017-11-30 kl. 23.20.21.png
Alternatively, in the plugin options you can set up variables that will be updated with the information on the triggering event and device: Skjermbilde 2017-11-30 kl. 23.23.07.pngThis allows you to use the variables to send more formatted e-mails or notifications.
Once you start getting "spammed" with notifications, you can continue to update the trigger with exclusion filters for the notification reports you don't want to trigger.
]]>2017-11-30T16:10:23-06:002017-11-30T16:10:23-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=150333#p150333Released version 0.3.4 that fixes some minor issues
]]>2017-02-07T05:10:33-06:002017-02-07T05:10:33-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=135022#p135022 I believe this is fixed, but I hadn't released the code yet, as there is one issue I wanted to fix first. I've just released 0.3.1 where the reset should work. Since I'm away for at least 10 more days, I don't think I'll be able to fix the remaining issue, so you should be aware: The ZEAL plugin checks at startup whether or not the Better Email plugin is running. If you have chosen to use the Better Email plugin, and during Indigo restart the ZEAL plugin is loaded before Better E-mail plugin, this option will be disabled and have to be re-enabled. I will change this to check a few times before giving up in next release
]]>2017-02-07T02:11:25-06:002017-02-07T02:11:25-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=135020#p135020
When I want to "Reset All Z-wave node statistics" It does not reset and I see this error in the log file.
ZEAL Error Error in plugin execution UiAction:
Traceback (most recent call last): TypeError: resetNodeStats() takes at most 2 arguments (3 given)
]]>2017-01-22T17:08:39-06:002017-01-22T17:08:39-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133869#p133869v0.3.0 released:
Better formatting and order for z-wave node statistics table
Action for statistics table added :
Can be sent as e-mail or output to indigo log
Supports device and variable substitution
When using Better E-mail plugin (> v7.1.0), e-mail can be sent in HTML format for better looking table. Need to enable this in plugin preferences and select a Better Email SMTP device for sending
Custom selection of columns to include
Selectable column to order by
Can set custom default value where stats are missing
The Better Email plugin was just updated with HTML e-mail support minutes ago, so this needs to be updated to use this feature.
Explanation to the columns: In: Number of received Z-wave commands Out: Number of sent Z-wave commands where Indigo was expecting a reply OutNoReply: Number of sent Z-wave commands where Indigo was not expecting a reply Notif.Rep.: Number of received notification reports from the device Batt.Rep.: Number of received battery reports from the device NoAcks: Number of sent z-wave commands with no acknowledge SlowAckTrigs.: Number of times the plugin has triggered on slow ack for the device AckMin: Minimum ack time for the device AckMax: Maximum ack time for the device AckAvg: Average ack time for the device (for sent commands where Indigo was expecting a reply)
The table can be output to log from the plugin menu or from a customizable action: Skjermbilde 2017-01-23 kl. 00.03.06.png
By default it will send plain text e-mails, for which the table will not look very good. If enabling Better E-mail in ZEAL plugin prefs, HTML e-mails with better looking tables can be sent: Skjermbilde 2017-01-23 kl. 00.04.27.png
The node statistics can be reset from plugin menu or from an action that can be triggered periodically etc.
]]>2017-01-18T14:40:10-06:002017-01-18T14:40:10-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133652#p133652 v0.2.1
Custom Z-wave device list in event dialogs -> Only one Indigo device per Z-wave node (one z-wave device may normally have multiple Indigo devices)
Possible to choose to trigger for all but selected Z-wave devices (exclude)
The limited device list was necessary for being able to exclude devices in triggers. As some Z-wave devices have 5-6 Indigo devices, all would have to be excluded etc.. There is some logic in the plugin attempting to figure out the "main" Indigo device for each z-wave node. So the device listed in the UI dialogs is the one the plugin finds as the "main" device. Please let me know how that works for your devices.
v0.2.2
Rough table print of z-wave node statistics to indigo log
I'll be working a bit more on the format of the table, column ordering, header names, sorting etc. but please do test it It will produce a table similar to this:
Z-Wave Error no ack/nak/busy reply (021) for setMultiLevelValue (re-sending) Z-Wave sent "Gang Ytter" off ZEAL Debug sent: 01 0E 00 13 15 07 60 0D 01 01 26 01 00 25 10 8F (node 021 ACK after 66 milliseconds)
The only command reported to the plugin is the successful one with ack after 66 milliseconds.
]]>2017-01-16T09:16:42-06:002017-01-16T09:16:42-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133476#p133476
]]>2017-01-16T06:32:06-06:002017-01-16T06:32:06-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133461#p133461
In my network, I see that I typically get ~60 ms when controlling a single device, however turning off all lights in living room etc. causes some traffic on the network and the response time will typically be 2-300 ms or up to ~700 for the farthest devices.
I think that this trigger on "slow ack" could/should be used more as a diagnose tool to identify devices with poor reception etc. The "no ack" trigger is probably more useful as it is now.
However, I have some plans for integrating this with my notification plugin, which I think will make also the "slow ack" more usable. What I'm planning is to make an option for sending periodic summary reports from the notification plugin, rather than instant notifications/e-mails.
The way I'm planning it is that you can make triggers with an action to the notification plugin. These will not be sent immediately, but when next summary report is sent. This way you should, for example, be able to get a list of slow responding devices etc. once a day or week instead of a lot of notifications.
The option to exclude devices is a good idea, I'll add that, as it should be quite easy to do
]]>2017-01-16T06:14:17-06:002017-01-16T06:14:17-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133460#p133460 I woke up this morning to a bevy of No Ack triggers--only one of them is a true No Ack.
I think that the default trigger time of 300ms is too short for my network (Z Stick Gen 2) so I've upped the limit to 1000ms. This is still going to give me false No Ack triggers as my record (so far) is an Everspring Illumination Sensor with a response time of 7330ms. Seems silly, but I may have to up the plugin limit to 10000ms.
Alternatively, a potential enhancement to the plugin would be an ability to exclude devices from the trigger (I realize I can include all devices *except* the ones I want to exclude, but that would require going back and updating the plugin configuration every time a change is made to the network).
Thanks for the great plugin! Dave
]]>2017-01-16T03:37:09-06:002017-01-16T03:37:09-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133459#p133459
]]>2017-01-15T17:54:57-06:002017-01-15T17:54:57-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=133446#p133446 Changes:
Possible to trigger on outgoing z-wave commands:
No ack from device
Slow ack from device
Information on trigger and triggering device can be stored to variables
Made it possible to reset/repeat low battery or battery level alarms after set number of hours (i.e. devices that continuously repeat low battery reports, not trigger every time), in addition to the previous automatic reset on battery replacement etc.
Added same reset/repeat logic to low battery reports as for battery level reports
Minor tweaks
Configuration of variables is done in plugin config: Skjermbilde 2017-01-16 kl. 00.48.52.png
Trigger for outgoing z-wave commands: Skjermbilde 2017-01-16 kl. 00.52.29.png
As for the other trigger types, you can choose to trigger for all devices or selected devices.
]]>2017-01-05T14:18:38-06:002017-01-05T14:18:38-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=132686#p132686Usage examples
Trigger on battery level Log output:
Code:
Z-Wave received "013 - Zipato keypad lyd" status update battery level 79% Trigger test zeal battery ZEAL Warning Received "Zipato keypad lyd" battery level below trigger threshold, battery level 79
(trigger level was set to 90% just to force the trigger)
Note that Indigo incorrectly sets the battery level to 0%. The battery level is actually 50%, the battery level of 255 is reserved for "low battery report"
Fibaro dimmer 2, overload Log output:
Code:
Z-Wave sent "Gang Bad" on Z-Wave received "Gang Bad" status update is off Trigger test zeal ZEAL Received "Gang Bad" notification report "Over-load detected", type 8, event 8
Fibaro dimmer 2, burnt out bulb detected Log output:
Code:
Z-Wave sent "Gang Bad" set brightness to 60 Z-Wave sent "Gang Ytter" set brightness to 60 Trigger test zeal ZEAL Received "Gang Bad" notification report "Load error", type 8, event 9
Single trigger for all motion sensors (that supports notification reports) Skjermbilde 2017-01-05 kl. 21.14.27.png
]]>2017-01-05T13:30:18-06:002017-01-05T13:30:18-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=132682#p132682 v0.1.2 posted - small bugfix
]]>2017-01-05T04:40:04-06:002017-01-05T04:40:04-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=132660#p132660
]]>2017-01-04T20:42:20-06:002017-01-04T20:42:20-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=132643#p132643
]]>2017-01-05T13:29:31-06:002017-01-04T17:43:27-06:00https://forums.indigodomo.com/viewtopic.php?t=17738&p=132625#p132625Download link
I'm making a new plugin that will listen for Z-wave alarms and notifications as well as battery reports. As I have a limited number of devices to test on, I'd appreciate feedback on how it behaves with different devices, as well as other feedback, before I proceed with the plugin.
Notification and alarm reports Basically you can create triggers that will listen for notification and alarm reports for selected or all devices. Normally you won't know which notification reports the device will send, so the idea is that you can create inclusion filters for many or all notification reports, and then later on choose to exclude those you don't want to trigger on. There is no limit to the number of filters. Skjermbilde 2017-01-05 kl. 00.27.06.png
Battery reports You will be able to make triggers for a set battery level or low battery report for selected or all devices. Skjermbilde 2017-01-05 kl. 00.31.39.png
Good to know
Alpha test - features and setup may change at a later stage
There are some differences between early Z-wave alarm reports (version 1) and later notification reports (v2-v8). Alarm reports (version 1) is not implemented as trigger yet
To minimize load when commands are received, the plugin stores a list of indigo devices, refreshes every hour. Can be refreshed manually by reloading the plugin.
Triggers for battery level can be set not to repeat until reset (avoid spamming every time device reports battery level). The trigger can be reset automatically when above set battery level or manually through plugin menu item.