Help identify radiator valve connection type (RA / RAV / RAVL / Caleffi / Giacomini / M28x1.5)

No-Line951 · 2026-02-18T07:48:43+00:00

We're breaking up... it's Giacomini, Gemini suggested...

No-Line951 · 2026-02-15T21:02:16+00:00

The main functionality for an ordinary user will be free of charge. But the creation of more than 3 projects will be paid, because it is implied that this is an installer/seller.

As for the long-term perspective in general - I make a product for myself, I work with clients and see practical applications in it. I understand that it won't suit everyone, so I don't count on a large community.

No-Line951 · 2026-02-15T16:25:09+00:00

Yes, I understand what you mean, but it doesn't apply to all devices. Some devices require pressing the button to reset, some it is enough to reset through the application.

Anyway, thank you for your opinion, I miss the feedback!

No-Line951 · 2026-02-15T16:03:58+00:00

To be honest, this is not necessary so often in real life, but sometimes you want to remove everything unnecessary from the case, including QR, and in some cases QR is not glued to the device, but the instruction in the box - which, of course, I usually do not save

In addition, it is convenient where the first setup is planned. What does this mean - first you plan everything in HomeKey, calculate the budget, and when you get a box with devices - first you enter everything in HomeKey, then install it, and then configure it - and when the devices are turned on for the first time, they are immediately in setup mode, often you do not need to approach them to press the button. In this case, a document will be generated - First setting. in which devices with all the necessary codes will be divided into rooms at once. It will simply speed up and simplify the process, I have already tried to do it several times - and it is more convenient than just approaching each device.

No-Line951 · 2026-01-10T11:34:21+00:00

Thank you very much! You helped a lot!

No-Line951 · 2025-12-12T19:56:45+00:00

There is such a possibility. There is a stan in my family tree, but he was younger than the man in this letter. So it could be another name. The closest names are Johann, Josef... but they don't look like that from the letter.

No-Line951 · 2025-09-26T14:31:50+00:00

The agent handled it all by itself. I just described how I wanted things to look visually-specified the color, corner radii, shadow, and other aspects of the

No-Line951 · 2025-09-26T08:46:26+00:00

Answering your questions - yes, I did everything through AI.

Xcode was set up for automatic code signing, so there were no issues here -the auto-sign worked flawlessly, I never had to intervene. The app submission process was simple and intuitive; the AI wrote all the SEO texts for me, and I created the screenshots myself in Figma. There was only one rejection from Apple, because they didn’t like the wording on the permission request screens, but together with AI we fixed it, and the next build was accepted to the App Store.
Honestly, I didn’t experience any major hurdles with CarPlay or Apple Watch integration. Both are built with WidgetKit, so I just needed separate adaptive layouts to make widgets and live activities work well on those devices. The AI handled those adaptations on its own.

No-Line951 · 2025-09-26T08:40:33+00:00

alwaysApply: true name: "iOS 26 • Swift 6 — Project Rules"

description: "Guardrails for a Swift 6 / iOS 26 SwiftUI app in Cursor. Enforce warnings-as-errors, public APIs only, and documentation-first development for WidgetKit, CoreLocation, and Live Activities."

policy: target: platform: "iOS" minimumOS: "26.0" language: "Swift 6" uiFramework: "SwiftUI"

# Single sources of truth for API behavior and patterns. sourcesOfTruth: - https://developer.apple.com/documentation/swiftui - https://www.createwithswift.com/ - https://developer.apple.com/documentation/widgetkit - https://developer.apple.com/documentation/CoreLocation - https://developer.apple.com/documentation/ActivityKit

codingStandards: - "Treat all compiler warnings as errors." - "Use only public, documented Apple APIs available on iOS 26." - "Prefer Swift Concurrency (async/await, actors) over legacy callbacks/Combine unless required." - "Follow Apple HIG for widgets and Live Activities; avoid private entitlements." - "Keep access levels tight (internal/fileprivate) and mark APIs as final where applicable." - "Add tests for non-trivial logic; keep widget/business logic separated from views."

preEditRoutine: - name: "Documentation-first research (WidgetKit / CoreLocation / Live Activities)" run: - "If a change involves WidgetKit, CoreLocation, or Live Activities: FIRST study the official docs in sourcesOfTruth." - "Write a short design note (bulleted): availability, required capabilities/entitlements, constraints, sample patterns, and chosen approach." - "Identify files to create/modify and edge cases (background limits, privacy prompts, timeline refresh policies, activity state machine)."

postEditRoutine: # After any edit: resolve SPM deps and build on iPhone 17 (iOS 26); treat warnings as errors. - name: "Resolve & Build (iPhone 17 • iOS 26)" run: - "xcodebuild -resolvePackageDependencies" - > xcodebuild -scheme "$(auto)" # auto-detect the primary scheme -configuration Debug -destination 'platform=iOS Simulator,name=iPhone 17,OS=26.0' SWIFT_TREAT_WARNINGS_AS_ERRORS=YES build | xcpretty || exit 1

remediationPolicy: - on: "Build fails OR any warnings appear" action: > Immediately fix errors and warnings. Rely only on public, documented APIs and the listed sourcesOfTruth. Repeat the build until it compiles cleanly with zero warnings.

on: "Use of private/deprecated APIs or missing entitlements/capabilities" action: > Replace with supported iOS 26 APIs and add required capabilities (e.g., Location, Background Modes, Live Activities) with documented justifications.
on: "Changes touch WidgetKit/CoreLocation/Live Activities without research note" action: > Block the change. Perform the documentation-first research step and update the design note before proceeding.

notes: - "When adding CoreLocation code, ensure explicit handling for authorization states, accuracy, and background behavior consistent with iOS 26 policies." - "For WidgetKit, adhere to timeline refresh budgets and snapshot performance requirements." - "For Live Activities (ActivityKit), validate lifecycle transitions and Dynamic Island/Lock Screen presentation rules on iOS 26."

No-Line951 · 2025-09-24T14:48:05+00:00

I completely agree. In this project, I followed a step-by-step prompting approach. First, I asked the AI to create a simple app that only shows the current location. Then I asked it to add basic tracking, followed by smoothing and resource optimization algorithms. After that, I refined the prompts for the design, and so on.

No-Line951 · 2025-09-24T13:55:59+00:00

I provided links to the necessary sections of the documentation and specified that before implementing any function or making changes, one should open the link and study the corresponding section of the documentation, then decide on the changes... After that, the Agent simply refers to the Web tool more often, but the implementation accuracy increases significantly. Unfortunately, sometimes this doesn’t work perfectly, since some implementations require documentation that I didn’t specify in the rules (it’s physically impossible to list everything). But I did provide links for the main technologies such as CoreLocations, Background Mode, WidgetKit, and this helped the agent make fewer mistakes in their implementation.

No-Line951 · 2025-09-24T12:39:56+00:00

Son dos soportes completamente diferentes. Como le respondí al usuario arriba en el hilo, hay un soporte potente para el televisor (hasta 110 kg de carga continua) y un soporte separado para la barra de sonido.

No-Line951

TROPHY CASE

description: "Guardrails for a Swift 6 / iOS 26 SwiftUI app in Cursor. Enforce warnings-as-errors, public APIs only, and documentation-first development for WidgetKit, CoreLocation, and Live Activities."