amiga-news.de - Archive

Archiv 'New hardware and software products'

`11.Aug.2026` Jan Stermann (ANF)	Home Assistant client for AmigaOS: ami2ha ami2ha is a native AmigaOS client for the Home Assistant home automation system, with the first version (0.1) having been released recently. The program connects to the server via the WebSocket API and displays sensor readings, statuses, and switches in a configurable MUI window; changes are updated in real time. The entities that appear on the Amiga are specified in Home Assistant using a label. When establishing a connection, the Amiga queries which entities have this label. This means the selection can be changed without touching the Amiga. Grouping, order, labeling, and display style are configured in a settings window and saved in a text file. Further features: ARexx port (AMI2HA) with commands such as GET, ATTR, ON, OFF, TOGGLE, and CALL automatic reconnection after a disconnection Launch from the Workbench; settings in the icon tooltypes Command-line modes (LIST, GET, WATCH ...) that do not require MUI Memory requirements depend on the size of the dashboard, not on the size of the Home Assistant installation: Based on an installation with 2,079 entities, displaying twelve entities takes up about 1.3 KB instead of 960 KB. Requirements: AmigaOS 3.0 or later, a TCP/IP stack with bsdsocket.library (Roadshow, AmiTCP, Miami, or the UAE emulator), and MUI 3.8 or later for the user interface. The archive includes a 68000 build and a 68020 build, an installer script, and an AmigaGuide manual. It was developed and tested on AmigaOS 3.2 on an Amiga 4000T and on FS-UAE. HTTPS support (AmiSSL) is not yet included. Therefore, the server must currently be accessible via plain HTTP, which is usually the case on a home network. Plans include visual enhancements and the integration of additional smart home components such as roller shades, irrigation systems, solar panels, etc. ami2ha was created in conjunction with Claude (Anthropic): The concept, strategic decisions, and all testing on actual hardware were handled by developer Jan Stermann, while the code was written primarily through dialogue with the model. The entire process is documented in the Git history. The program is licensed under the MIT License. You can download ami2ha and the source code from GitHub. (nba) [News message: 11. Aug. 2026, 14:29] [Comments: 0] [Send via e-mail] [Print version] [ASCII version]
`11.Aug.2026` AMIGASYSTEM (ANF)	Player interface: PlaySID-GUI for AROS PlaySID-GUI provides AROS with a new graphical interface for playing SID music files. The tool uses Mihaly Horvath’s cSID player as its playback backend, a cross-platform command-line SID player based on the code from the jsSID project. cSID is not included in the archive, but is available separately for download. PlaySID-GUI was compiled natively on AROS 64-bit v11 with AI support and is freely available as public domain software. When using the file browser, please note that the "Parent" tab should not be used, as otherwise files will not be added correctly to the playlist. (nba) [News message: 11. Aug. 2026, 14:29] [Comments: 0] [Send via e-mail] [Print version] [ASCII version]
`10.Aug.2026`	Amiga Corporation announces completion of its own RTG system At the Kickstart UK in Derby (United Kingdom) last weekend, there was also a presentation by Mike Battilana of the Amiga Corporation, followed by a Q&A session. A transcript of Battilana’s speech, generated with AI support, is now available. The Amiga CEO explained, among other things, that work on components for AmigaOS 3 has already begun. Among other things, they have developed an RTG subsystem, which he would be happy to demonstrate to visitors at the event later: WWe’ve already started working on some new features for AmigaOS 3—I actually have an RTG subsystem here. I can show it to you later downstairs." [Editor's note: Retro Games Ltd., Amiga's most important licensee at present, announced in July that its upcoming ARM-based Amiga clone, the THEA1200, would also support RTG. It is currently unclear whether the solution announced by the Amiga Corporation will be already used in this project.] During the Q&A session, Battilana also comments on other topics related to the further development of OS4: Amiga will receive "everything" from Hyperion following its exit from the 68k market, with the exception of "some code that was backported from AmigaOS 4." According to estimates, this backported code amounts to between 800 and 1,000 lines of code. There is still a need for discussion between the two companies - but he is confident, since "no one wants to see the features newly introduced in OS 3.3 die out so quickly." A TCP stack was introduced with OS 3.9. Amiga wants to prevent users from having to update or supplement individual parts of their system with components from older releases; therefore, an (IPv4) TCP stack should remain an integral part of the system in the future in Battilana's eyes. Amiga will soon receive a build of AmigaOS 3.1.4 that already incorporas the first improvements from subsequent versions (3.2 and the unreleased 3.3). As an example, he cites Olaf Barthel's work on the file system. He proposes collaborating with the AROS project in order to "plan things even better together." Developing their own hardware is definitely being considered - but for now the priority is completing an AmigaOS version that offers greater value to existing hardware partners such as Retro Games Ltd. The release of the AmigaOS source code - a possibility Battilana has raised several times in the past - is still being considered. He speaks of "free" as in "free upgrades" as a first step; a second step could involve dual licensing; and the final step - which is still (quote) "very theoretical" at this point - would be "true open source" as defined by the Open Source Initiative. However, open source releases would not include a trademark license. The numbering for Amiga's own OS releases could start at 3.10, for example - Battilana finds it confusing that the Hyperion releases have lower version numbers than the H&P products - or simply use year numbers like "3.28". (cg) [News message: 10. Aug. 2026, 16:42] [Comments: 0] [Send via e-mail] [Print version] [ASCII version]
`08.Aug.2026` Thomas Lübker (ANF)	Artificial Intelligence: amiagent 0.5.3 - remotely control a real Amiga via MCP Thomas Lübker writes: "'amimcp' connects a real Amiga to an MCP server on a Mac or PC. An AI assistant can use it to work directly on the hardware: execute AmigaDOS commands, read and write files, capture the screen, and send mouse and keyboard inputs. The Amiga component is called 'amiagent': a small TCP daemon written entirely in C, without any third-party libraries, and compatible with AmigaOS 2.0 and later. It includes both a 68000 and a 68020 build. MCP (Model Context Protocol) is an open standard through which an assistant is provided with tools that it calls up itself - in this case, for example, `amiga_shell` or `amiga_screenshot`. The server is model-independent; it never knows which model is on the other end: Claude (Anthropic) - Claude Code, Claude Desktop, this was used to test amiagent GPT / ChatGPT (OpenAI) - Codex CLI Gemini (Google) - Gemini CLI Lokale Modelle - LM Studio, Goose, Cline, Continue Editor-Modelle - Cursor, Zed, Windsurf It's always the same server; only the configuration file is different. Pure Python 3 from the standard library - no pip, no venv. Things get interesting when you can no longer use the machine to repair it. If Picasso96 is set to a mode that isn't synchronized with the monitor, the Amiga runs perfectly but still displays nothing. The agent remains accessible over the network; it can read `DEVS:Monitors`, capture what the machine thinks it's displaying, and write back a working mode. The prerequisite is that the Amiga is running and connected to the network - it's not a rescue system... New in 0.5.3: Files are read using a 64-KB buffer instead of an 8-KB buffer, so large files are retrieved noticeably faster from the Amiga. On machines with limited memory, the previous method is used automatically. The protocol remains unchanged. The same release includes 'amibench 1.0,' a standalone CPU and memory benchmark for comparing two Amigas, which runs in about ten seconds. Just to be safe: The connection is not encrypted, and the agent executes whatever is sent to it. Always set a TOKEN, run it only on your own LAN, and never open the port on your router." (cg) [News message: 08. Aug. 2026, 23:28] [Comments: 0] [Send via e-mail] [Print version] [ASCII version]

<- 1 2 3 4 5 6 7 8 9 10 -> ... 15 500 991