I thought I would start a new topic on this insteading of continuing to post in the previous one.
I have done further investigating and found the following:
1. The leading space bug I reported in Oct is still present.
2. The command to suspend a zone or suspend all zones does not get thru to the Hydrawise unit as observed in its event log.
3. All other commands including start/stop zone(s) and resume zone(s) work fine and are detected in the Hydrawise event log.
I have tried the following:
1. Uninstall/reinstall plugin (v4.0.4.0).
2. Rerun auth wizard.
3. Redo config settings regards controller and child devices.
I have also checked the entries in the plugin ini file and they all seem correct, just for good measure I deleted the data in the file and reran wizard and observed the correct recreation of the data.
The way I understand how the plugin works is that it talks to the authors server which then handles interaction with Hydrawise server to alter parameters in your Hydrwise account which is then picked up by the local unit.
As all but one command type is working fine I can only conclude that the issue is on the authors server and the way it is trying to remit the suspend command to the Hydrawise server.
I have done further investigating and found the following:
1. The leading space bug I reported in Oct is still present.
2. The command to suspend a zone or suspend all zones does not get thru to the Hydrawise unit as observed in its event log.
3. All other commands including start/stop zone(s) and resume zone(s) work fine and are detected in the Hydrawise event log.
I have tried the following:
1. Uninstall/reinstall plugin (v4.0.4.0).
2. Rerun auth wizard.
3. Redo config settings regards controller and child devices.
I have also checked the entries in the plugin ini file and they all seem correct, just for good measure I deleted the data in the file and reran wizard and observed the correct recreation of the data.
The way I understand how the plugin works is that it talks to the authors server which then handles interaction with Hydrawise server to alter parameters in your Hydrwise account which is then picked up by the local unit.
As all but one command type is working fine I can only conclude that the issue is on the authors server and the way it is trying to remit the suspend command to the Hydrawise server.
Comment