logo elektroda
logo elektroda
X
logo elektroda

Integration of Home Assistant with room panel (thermostat) PILOT R WiFi

yacorek 2439 7
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 19674831
    yacorek
    Level 10  
    Hello, everyone.
    I am just starting my adventure with Home Assistant.
    I want to integrate my room panel (thermostat) into the HA and to be honest I don't know how to go about it. I've tried to find something on the web, but I'm having a poor time.

    The manufacturer gives this information:
    The R WiFi remote control is not an internet module however it allows communication in the local network with the possibility of redirection to the outside (depends on the conditions of the internet provider). In addition, it has the ability to send real-time data to a server and view them on www.aplikacja.prond.pl/pilotWifi 8 This makes the WiFi Pilot a functional device for remote monitoring of temperatures and the operating status of equipment in the boiler room.

    For developers:
    Pilot R WiFi transmits data to the browser in JSON format, which advanced users can use in their own control projects (smart building, etc.). Details are described in the appendix for programmers.
    Appendix for developers
    The Pilot R WiFi module can be communicated with via the network using queries of
    HTML. The queries should be sent to: [ip address PilotR]/main . The data is sent in
    JSON format. Examples for javascript.

    Reading parameters from PilotR
    var xh = new XMLHttpRequest();
    xh.onreadystatechange = function () {
    if (xh.readyState == 4) {
    if (xh.status == 200) {
    var res = JSON.parse(xh.responseText);
    //here „res” contains all read parameters
    };
    xh.open(“GET”, “/main”, true);
    xh.send(null);
    Example response:
    {“t_kot”:21.8, “t_pok”:20.9, “outputs”:0, “status”:0, “alarm”:0, “n_kotmin”:35, “n_kotmax”:85,
    “n_reg”:55, “t_mix”:0, “t_pog”:-128, “t_cwu”:0, “opal”:0, “n_kot”:55, “n_cwu”:0, “signal”:-85,
    “n_mix”:0, “n_pok”:23.6, “hist”:0.2, “c_odpomp”:10, “downgrade”:0, “sound”:3, “dod_al”:96,
    “c_zalpomp”:60, “data”:“30.03.2020”, “czas”:“15:09:13”}
    Meaning of parameters:
    t_kot – boiler/circuit temperature 0 - 99.9 (100 means exceeding the range)
    t_pok – room temperature -9.9 – 60.0 (280.5 means failure of PilotR sensor)
    outputs – status of controller outputs (0 –off or none, 1 – on):
    bit 0 – pump 3
    bit 1 – blower 2
    bit 2 – not used
    bit 3 – blower
    bit 4 – central heating pump
    bit 5 – DHW pump
    bit 6 – feeder
    bit 7 – blower (on fan 1)
    status – operation status and other markers:
    bit 0 – 0-nothing 1-signal of missing fuel (this is not AL5)
    bit 1 – 0-pilot operates 1-pilot extinguishes display
    bit 2 – indication of reaching the preset temperature (blinking dot) 0-calculated from
    setpoint and boiler temp. 1-status bit 3
    bit 3 – blinking dot: 0 - off, 1 - on
    bit 4 – HUW priority: 0-not active, 1-active
    bit 7,6,5 – operating status:
    000 – no status (controller not sending)
    001 – stop
    010 – firing up
    011 – operating
    100 – holding
    101 – manual operation
    110 – positioning
    111 – not used
    bit 8 – 0-room control 1-boiler/circuit control
    bit 9 – no connection between pilotR and controller (e.g. defective cable)
    alarm – 0 –no alarm other values 0x01-0x0f are the displayed alarm number
    n_kotmin – minimum boiler setting allowed by the regulator
    n_kotmax – maximum boiler setting allowed by regulator
    n_reg – setting for the regulator calculated from the formula n_kot-obnuska (used in older regulators, here only
    used in older regulators, here only for information)
    t_mix – mixer temperature
    t_pog – temperature of the weather sensor (from the regulator)
    t_cwu – DHW temperature
    opal – fuel level 0-no data 1-101 = 0-100%
    n_kot – boiler setting
    n_cwu – HUW setting 0-no data or HUW off, 15-75
    signal – wifi signal level -127-0
    n_mix – setting mixer 0-no data
    n_pok – room temp. setting 1.0-50.0 in 0.2 steps
    hist – room hysteresis 0.1-5.0 in 0.1 steps
    c_dpump – pump off time 0-91
    lowering – lowering set point 0-99
    sound – indication 0-3
    add_al – additional alarm 30-95, 96=off
    c_zalpomp – pump activation time 10-99
    date – date calculated by PilotR
    time - time counted by PilotR
    Sending parameters to PilotR
    var xh = new XMLHttpRequest();
    xh.open(“POST”, “/main”, true);
    xh.send("{“n_pok”:22.0}");
    Variables handled by PilotR:
    n_kot – boiler setting - integer in the range n_kotmin – n_kotmax
    n_cwu – HUW setting - integer from the interval 15-75
    n_pok – room temp. setting – float variable with 1 decimal place in the range
    in the range 1.0-50.0
    hist – hysteresis for the room – float variable with 1 decimal place in the interval 1.0-5.0
    interval 1.0-5.0
    c_pump – pump off time 0-91, where 0=on permanently, 91=
    permanently disabled (no cyclic pumping)
    decrease – setting decrease 0-99
    sound – signalling 0-3
    dod_al – additional alarm 30-96, 96=disabled
    c_zalpomp – pump activation time 10-99
    command – functions – variable of string type:
    rudder – change of control mode in PilotR (room<->boiler)
    status – changing the operation status of the boiler controller (operation<->stop)
    config – saving PilotR configuration to EEPROM memory
    Parameters can be sent separately or in multiples, it is not recommended to send
    unnecessary parameters, i.e. those that have not changed.
    Attention !!!
    Sending settings related to PilotR i.e.: hist, c_odpomp, obnizka, sound,
    dod_al, c_zalpomp causes their temporary change (until power off).
    Permanent saving is made by sending the command ‘config’. Other settings and
    commands are immediately written to the controller or PilotR memory after approval.
    As the EEPROM memory has a finite number of entries, it is not possible to use
    these parameters for a smooth control of e.g. the set boiler temperature. For this purpose
    This is also why limits of up to 25 changes per day have been introduced, counted separately for each parameter.
    parameter. This is sufficient for time-based control every hour. For stepless control of the
    The boiler setting can be reduced by setting the room control accordingly.
    room control.
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 19676766
    yacorek
    Level 10  
    Thank you very much for your tips!!!! I was able to use the RESTful Sensor to read and display the temperatures in Home Assistant!
    Greetings!
  • ADVERTISEMENT
  • #4 19676820
    starob
    Level 29  
    yacorek wrote:
    Thank you very much for your guidance!!!!
    .

    ... and that's all they saw of him :) .

    How about showing the solution instead?
  • ADVERTISEMENT
  • #5 19678092
    yacorek
    Level 10  
    I don't like to brag :P But of course with those interested I will share what I managed to do ;) .
    The Chrome add-on has also been very helpful, and it's all about the Advanced REST client.
    I'm still trying to pull more information from Pilot R.
    At the moment in Home Assistant it looks like this:
    Integration of Home Assistant with room panel (thermostat) PILOT R WiFi .
  • #6 19678614
    xury
    Automation specialist
    Take an interest in NodeRed. In NR you will extract everything from a JSON object.
  • #7 21350116
    warsztatblonie
    Level 1  
    >>19678092 .
    Hello, anything more you managed to do with this regulator?
    >>19678092
  • #8 21470065
    ic3ek
    Level 15  
    Hi.

    Sorry for rehashing an old story, but does anyone have any information on what system this remote control works in? On the 1-wire connection there is no way to get any valid data, "just probably coded bushes". On 1-wire there is no proper data, "only probably coded bushes", but on the 2 external RJ-12 pins there is the usual RS232, but only information about the boiler temperature and HUW, no more information.

    yacorek wrote:
    I don't like to boast But of course with those interested I will share what I managed to do
    The Chrome add-on has also been very helpful, and it's all about the Advanced REST client.
    I'm still trying to get more information out of Pilot R.
    At the moment in Home Assistant it looks like this:


    Would you be able to drop the JSON file that PILOt R Wifi generates, then I'll try to upload all the information that this remote sends , and integrate into HA.

    I see that you have already done something because there is a boiler temp in HA, maybe share the code you wrote to transfer this sensor to HA.

    I need to know if it is possible to integrate it peacefully into the HA, because I intend to buy still from the last PILOT R WIFI, although at home I have Pilot G, which is much better has the appearance of "still the old version".

    Best regards

Topic summary

The discussion focuses on integrating the PILOT R WiFi room panel thermostat with Home Assistant (HA). The device communicates over a local network and provides real-time data in JSON format accessible via a web interface. Integration is achieved using Home Assistant's RESTful Sensor to fetch temperature and status data through REST API calls. Tools like the Advanced REST client and Chrome add-ons assist in extracting JSON data. Node-RED is recommended for parsing JSON objects within HA. Some users seek further details on the device's communication protocols, noting that 1-wire connections yield no valid data, while RS232 on external RJ-12 pins provides limited boiler temperature information. Sharing JSON output files and integration code is requested to enhance HA compatibility. The PILOT R WiFi is contrasted with older models like Pilot G, with interest in full integration capabilities and data extraction for smart building applications.
Summary generated by the language model.
ADVERTISEMENT