Announcement

Collapse
No announcement yet.

Autelis with Jandy - no Aquapure device or Pump speed - now available!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • mda
    replied
    Great, thanks.

    Leave a comment:


  • spud
    replied
    Originally posted by mda View Post
    @Spud

    Autelis sent me an updated firmware for their box (version PC100JZ-ADV-1.6.16.jar)

    Due to the way things work on their end, it will now report <avail>8</avail> in /chem.xml when the chlorinator is not connected (rather than 0).

    Would it be possible for you to adjust the plug-in to handle <avail>8</avail> as this error condition? Thanks!
    if avail = 8, the chlorination error device should already report a GeneralFault error, because avail is a bit field with the following meaning

    <avail>
    Definition: Indicates what equipment is available
    Possible values: 1 byte bitflag array (0=not available, 1=available), bit0=chlorinator, bit1=chem1, bit2=chem2
    </avail>
    and according to this http://www.autelis.com/forum/viewtopic.php?f=4&t=555, the other bits are not related to chemical equipment

    so when available = 8 (1000 in binary), the first bit is 0 so the plugin will report an error in the chlorinator error device.

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    In version 3.0.0.20 available here, the "Chlorination error" device is now set to GeneralFault if<avail> is 0 or if the request to get chem.xml fails
    Originally posted by mda View Post
    I will also ask Autelis to confirm that their firmware is reporting the condition correctly...
    @Spud

    Autelis sent me an updated firmware for their box (version PC100JZ-ADV-1.6.16.jar)

    Due to the way things work on their end, it will now report <avail>8</avail> in /chem.xml when the chlorinator is not connected (rather than 0).

    Would it be possible for you to adjust the plug-in to handle <avail>8</avail> as this error condition? Thanks!

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    In version 3.0.0.20 available here, the "Chlorination error" device is now set to GeneralFault if<avail> is 0 or if the request to get chem.xml fails
    Thanks! I have installed it and will keep an eye on it.

    Leave a comment:


  • spud
    replied
    Originally posted by mda View Post
    Hi @Spud i think i ran into a bug with the way status is reporting on the Aquapure. I am not sure if it is in the plugin (.18) or the version of the autelis firmware (1.6.12) i am running.

    the other day, my pool person accidentally disconnected my Aquapure from my Jandy control system RS422 bus, but the plugin kept reporting status on the Aquapure as OK even though the Jandy (iAqalink app and local keypads) no longer showed the Aquapure as being connected to the system.

    I was not in town so I do not know what the Autelis was reporting to HS3 (and my log file does not have the info anymore, sorry), but it would either have been not returning the /chem.xml page at all or showing <avail>0</avail> (instead of the normal <avail>9</avail> in the /chem.xml page response)

    So, that makes me wonder if the plugin is taking either of those conditions into account when returning OK as status for the Aquapure device or only returning an error if the <chlrerr> attribute on the last response for /chem.xml is not 0 ?

    If it is not taking those two conditions into account, would it be possible for it to please check for the conditions where /chem.xml does not return or the <avail> attribute is not 9 -- and when that happens change the Value/Status of the HS3 Aquapure device to some value other than 0 (OK)? (perhaps something like 100 or -1 that Autelis will not return in the <chlrerr> attribute so we can use this as a trigger to alert that the Aquaure is no longer connected to the Jandy system?

    If you are already taking this into account, please accept my apology for the bother and would you mind letting me know what Value/Status the Aquapure device will show when the Aquapure is not connected?

    I will also ask Autelis to confirm that their firmware is reporting the condition correctly with <avail> attribute of 0 when the Aquapure is not connected. (i would recreate the condition to check this, but it requires taking apart my pool control system so it would be quite difficult right now).

    Thanks!
    In version 3.0.0.20 available here, the "Chlorination error" device is now set to GeneralFault if<avail> is 0 or if the request to get chem.xml fails

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    I added the pump information in version 3.0.0.18 available here: https://forums.homeseer.com/showthre...83#post1153183
    Hi @Spud i think i ran into a bug with the way status is reporting on the Aquapure. I am not sure if it is in the plugin (.18) or the version of the autelis firmware (1.6.12) i am running.

    the other day, my pool person accidentally disconnected my Aquapure from my Jandy control system RS422 bus, but the plugin kept reporting status on the Aquapure as OK even though the Jandy (iAqalink app and local keypads) no longer showed the Aquapure as being connected to the system.

    I was not in town so I do not know what the Autelis was reporting to HS3 (and my log file does not have the info anymore, sorry), but it would either have been not returning the /chem.xml page at all or showing <avail>0</avail> (instead of the normal <avail>9</avail> in the /chem.xml page response)

    So, that makes me wonder if the plugin is taking either of those conditions into account when returning OK as status for the Aquapure device or only returning an error if the <chlrerr> attribute on the last response for /chem.xml is not 0 ?

    If it is not taking those two conditions into account, would it be possible for it to please check for the conditions where /chem.xml does not return or the <avail> attribute is not 9 -- and when that happens change the Value/Status of the HS3 Aquapure device to some value other than 0 (OK)? (perhaps something like 100 or -1 that Autelis will not return in the <chlrerr> attribute so we can use this as a trigger to alert that the Aquaure is no longer connected to the Jandy system?

    If you are already taking this into account, please accept my apology for the bother and would you mind letting me know what Value/Status the Aquapure device will show when the Aquapure is not connected?

    I will also ask Autelis to confirm that their firmware is reporting the condition correctly with <avail> attribute of 0 when the Aquapure is not connected. (i would recreate the condition to check this, but it requires taking apart my pool control system so it would be quite difficult right now).

    Thanks!

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    I added the pump information in version 3.0.0.18 available here: https://forums.homeseer.com/showthre...83#post1153183
    Thanks!

    Leave a comment:


  • spud
    replied
    I added the pump information in version 3.0.0.18 available here: https://forums.homeseer.com/showthre...83#post1153183

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    yes for Aquapure error

    not yet for Speed pump RPM and wattage


    Thanks. I will hold off updating until you get pump speed and rpm too I think, so I can swap out all of my scraped devices at once. No rush!

    Leave a comment:


  • spud
    replied
    Originally posted by mda View Post
    Hi @spud, does .17 also handle Aquapure error status and Jandy Variable Speed Pump RPM and wattage?

    (just checking before I update and set out to redo what I have working with the webscraper)

    Thanks!
    yes for Aquapure error
    not yet for Speed pump RPM and wattage

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    in version 3.0.0.17 available here, I have added support for chemistry information (chlorinator setpoint, salt level, ph, ORP, etc...) for Jandy controllers
    Hi @spud, does .17 also handle Aquapure error status and Jandy Variable Speed Pump RPM and wattage?

    (just checking before I update and set out to redo what I have working with the webscraper)

    Thanks!

    Leave a comment:


  • spud
    replied
    in version 3.0.0.17 available here, I have added support for chemistry information (chlorinator setpoint, salt level, ph, ORP, etc...) for Jandy controllers

    Leave a comment:


  • mda
    replied
    Autelis with Jandy - no Aquapure device or Pump speed

    Originally posted by mda View Post
    @Spud, Autelis just added pump RPM and Watts, and Aquapure status/errors to Autelis firmware 1.6.12 for Jandy http://autelis.com/forum/viewtopic.p...0&p=2663#p2663


    No need anymore on my end, I was able to sort it out with Jon00's DataScraper script

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    The current version of the plugin does not parse chem.xml nor pumps.xml for Jandy controllers. I have added this to my TODO list.
    @Spud, Autelis just added pump RPM and Watts, and Aquapure status/errors to Autelis firmware 1.6.12 for Jandy http://autelis.com/forum/viewtopic.p...0&p=2663#p2663

    Here is the new pumps.xml:

    Code:
    <response>
    <pumps>
    <vsp1>1</vsp1>
    <vsp1rpm>2500</vsp1rpm>
    <vsp1watts>735</vsp1watts>
    <vsp2/>
    <vsp2rpm/>
    <vsp2watts/>
    <vsp3/>
    <vsp3rpm/>
    <vsp3watts/>
    <vsp4/>
    <vsp4rpm/>
    <vsp4watts/>
    </pumps>
    </response>


    And here is the new chem.xml:

    Code:
    <response>
    <chem>
    <avail>9</avail>
    <chlrp>30</chlrp>
    <saltp>94</saltp>
    <chlrs>5</chlrs>
    <salts>94</salts>
    <chlrerr>1</chlrerr>
    <orp1>0</orp1>
    <orp2>0</orp2>
    <ph1>0</ph1>
    <ph2>0</ph2>
    <orpfd1>0</orpfd1>
    <orpfd2>0</orpfd2>
    <phfd1>0</phfd1>
    <phfd2>0</phfd2>
    </chem>
    </response>

    This is showing a "Check Flow/PCB" error. Here is the error text lookup from their /chem.htm

    Code:
    var statusStrings = [ "Check Flow/PCB","Low Salt","High Salt","General Fault","?","?","?","?","OK" ];
    if(err > 0)
    {
    	for(i=7;i>0;i--)
    		if((parseInt(err)>>i) & 1)
    			break;
    	var txt = statusStrings[i];
    }
    else 
    	txt = statusStrings[8];
    return txt;		
    }
    When you add parsing /pumps.xml and /chem.xml, if you could please expose <chlrerr> from /chem.xml and <vsp1rpm> and <vsp1watts> from /pumps.xml as triggers/conditions, it would then be possible to send alerts on chlorinator errors (before discovering the pool has no chlorine after days of issues -- yes, that was my last weekend unfortunately) and also alert when the pump needs to be cleaned based on the change in wattage for the same RPM.

    Thanks!

    Leave a comment:


  • mda
    replied
    Originally posted by spud View Post
    The current version of the plugin does not parse chem.xml nor pumps.xml for Jandy controllers. I have added this to my TODO list.

    regarding the error, do you get it everytime you start the plug-in? if so please set the log level to debug, then capture the start of the plug-in. Thanks
    I have not seen that error again (since I have had debugging on) but got a new error on HS3 startup today (just once in perhaps 20 startups) and had debugging on.

    Code:
    6/11/2017 11:18:04 AM ~!~Plug-In~!~Found plug-in: Autelis, version: 3.0.0.15
    6/11/2017 11:18:34 AM ~!~Info~!~Plugin Autelis has connected. IP:127.0.0.1:49239
    [COLOR="Red"]6/11/2017 11:18:34 AM ~!~Error~!~Initializing plug-in(1): Autelis Instance::System.NullReferenceException: Object reference not set to an instance of an object.   at HSPI_Autelis.Logger.Init()   at HSPI_Autelis.AutelisApp.Init()[/COLOR]
    6/11/2017 11:18:34 AM ~!~Info~!~Plugin Autelis with instance:  has disconnected
    6/11/2017 11:18:37 AM ~!~Plug-In~!~Finished initializing plug-in Autelis
    Disabling it and re-enabling it started it back up without the error. My Autelis is online and seems fully responsive (i checked when the error happened) and the pool pump is running. Thanks.

    Leave a comment:

Working...
X