====== OpenAI - GPT4 ======

This section contains a collection of prompts for generating configurations for the **IB-System**, using the GPT chat with the GPT-4 model from OpenAI with the **WebPilot** or **Link Reader** plugin active.

https://chat.openai.com/

This section contains tips that will help in using AI tools to generate configurations for the **IB-System**. These tips have been tested and verified at the time of publication, but please note that their effectiveness may change over time.

It is important that third-party companies that provide AI tools regularly update and modify their algorithms to improve performance, adapt to new data and phenomena, or in response to changing requirements and standards. These changes can affect the way AI tools generate configurations, which in turn can affect the quality and correctness of the generated configurations.

Also remember that while AI is a powerful tool, it still requires human supervision and intervention. Regardless of how advanced AI tools are, it is always worth paying attention to the results they generate and being ready to intervene if something goes wrong.

===== ibvunit =====

==== ibvunit .xml - plik konfiguracyjny====

<code text propmpt.txt>
Based on

https://ibsystem.org/wiki/doku.php?id=en:ibvunit:ibvunit-config&do=export_text

Remember that devices can be abbreviated by a string in the form of: HxFyVz which means assigning the values of the attributes HardwareId="x" FirmwareId="y" FirmwareVersion="z"

Generate a configuration file for the ibvunit program (ibvunit.xml) supporting:

Gateway "0", Linux hardware ttyS1, default communication parameters, devices connected to it:
- Dedicated for IB-System, ID 1, 2, 3
- Non-dedicated H1020F1V1, id 11, 12

Gateway "1", Linux hardware ttyS2, speed 19200, devices connected to it:
- Non-dedicated H1012F1V1, id 101

For all gateways: SleepMS="20"

For all devices: TimeoutMS = "1000"

Skip elements: MWT, MaxDataWordsInFrame, MaxRetransmissions

Include paths in a format suitable for the Linux system.

The last known element should be <EDT>, if the plugin did not provide you with enough information, fill in the missing information and regenerate the code block with the xml file supplemented with missing data. Don't wait for the next command, just generate the final xml file, with all elements.
</code>

===== ibmanager =====

==== ibmanager.xml - configuration file ====

In the example query, personalize the text in quotes.

<code text propmpt.txt>
Based on

https://ibsystem.org/wiki/doku.php?id=en:ibmanager:ibmanager-config&do=export_text

generate a configuration file for the ibmanager program (ibmanager.xml) with default values for a new application:

name "custom-thermostat-home"
application version "1.0.0"
instance ""
location: longitude and latitude for the city of "Oxford, GB"
WanHostName: "s21c.ibsystem.org"
WanTcpPort: "22532"

Include the application name and version in the ibgui descriptor name.
Skip elements: TrackedVariable

Include paths in a format suitable for the Linux system.
</code>

==== alerts.xml - configuration file====

<code text propmpt.txt>
Based on

https://ibsystem.org/wiki/doku.php?id=en:ibmanager:ibmanager-alerts&do=export_text

generate an alert configuration file for the ibmanager program (ibalert.xml). The parameters for ibalert are s213c.ibsystem.org:33241, timeout 3000, SecureConnection=true

use regular expressions when defining alerts.

Alerts in which id starts with "critical." are critical alerts, for all logics, all instances, direct to all recipients.
Non-critical alerts do not start with "critical", for all ids, all logics, all instances, direct to all recipients.

rules:

critical alerts: every day at any time, every 1 min
non-critical alerts: daily from 9 to 20, every 24h

recipients:

John Smith, +48222222222, john81@example.com
Jane Doe, +48111111111, jane.doe@example.com

Send critical alerts via SMS only to all recipients.
Send non-critical alerts via email only to John Smith.

The last known element should be <Recipient>, if the plugin did not provide you with sufficient information, fill in the missing information and re-generate the code block with the xml file supplemented with the missing data. Do not wait for the next command, just generate the final xml file, with all elements.
</code>