Pi4J, the Java library to control the GPIOs of the Raspberry Pi
Find a file
Stefan Haustein 9ad488e921
Some checks failed
CodeQL Advanced / Analyze (actions) (push) Failing after 1s
CodeQL Advanced / Analyze (java-kotlin) (push) Failing after 1s
Build develop snapshot and push to download repo / Build & Deploy Snapshot (push) Failing after 3s
Build develop snapshot and push to download repo / Deploy to APT/Download Repo (push) Has been skipped
Merge pull request #575 from stefanhaustein/develop
Re-work the deferred delay class
2025-12-22 00:02:12 +01:00
.github/workflows CodeQL analysis, remove cpp 2025-10-21 09:12:52 +02:00
.mvn/wrapper Update Maven Plugin Versions and add Apache Maven Wrapper 2024-11-27 13:42:24 +01:00
.run [Project] Enabling building of gpiod plugin 2024-01-22 16:11:47 +01:00
assets/draw.io Added draw.io schemes for the documentation site 2020-06-24 22:44:03 +02:00
config/checkstyle Readd default rules 2024-11-16 15:46:16 +01:00
libraries #551 Reworking PWM to chip/address/bcm 2025-11-14 17:36:36 +01:00
pi4j-core improve javadoc 2025-12-21 12:00:08 +01:00
pi4j-distribution Bump to 4.0.0-SNAPSHOT 2025-09-10 15:48:49 +02:00
pi4j-test Align FFM Provider names with other plugins 2025-12-19 09:25:49 +01:00
plugins Align FFM Provider names with other plugins: formatting improvements 2025-12-19 09:37:16 +01:00
src/license iniital commit 2019-06-18 14:18:05 -04:00
.editorconfig added initial editor config for code style + README additions 2020-05-29 23:55:49 +02:00
.gitattributes iniital commit 2019-06-18 14:18:05 -04:00
.gitignore updated gitignore 2019-08-20 20:35:19 -04:00
autoRelease [Fix] Fixed deployment missing artifacts 2024-03-21 09:45:35 +01:00
autoReleaseBranch [Fix] Fixed deployment missing artifacts 2024-03-21 09:45:35 +01:00
build-docker.sh added a build-docker.sh script to build entire Pi4J project inside container 2020-06-30 13:22:31 -04:00
deployToMavenCentral.sh [Project] Don't call package when deploying 2025-03-24 07:46:02 +01:00
LICENSE.txt iniital commit 2019-06-18 14:18:05 -04:00
mvnw Update Maven Plugin Versions and add Apache Maven Wrapper 2024-11-27 13:42:24 +01:00
mvnw.cmd Update Maven Plugin Versions and add Apache Maven Wrapper 2024-11-27 13:42:24 +01:00
NOTICE.txt Avoid yearly code changes by removing years from the classes 2021-03-02 09:55:19 +01:00
pom.xml [Project] Update snapshot repository URL in pom.xml 2025-09-24 13:25:24 +02:00
providers.csv [New] Extended Providers with a priority 2024-01-10 17:14:26 +01:00
README.md #565: PWM on should be executed to handle changed values, even if already on 2025-12-11 10:31:36 +01:00
RELEASE.md [Fix] Fixed deployment missing artifacts 2024-03-21 09:45:35 +01:00
TODO added support for context 'shutdown' and 'initialized' events. 2019-09-09 14:00:17 -04:00

Pi4J :: Java I/O Library for Raspberry Pi

Maven Central Sonatype Nexus (Snapshots) License

Site Chat on Slack Pi4J on Mastodon Pi4J on LinkedIn

API documentation: APIdia


Project Information for V2+ of Pi4J

Project website: pi4j.com.

This project is intended to provide a friendly object-oriented I/O API and implementation libraries for Java Programmers to access the full I/O capabilities of the Raspberry Pi platform. This project abstracts the low-level native integration and interrupt monitoring to enable Java programmers to focus on implementing their application business logic.

Pi4J diagram

Builds are available from:

Using Pi4J

You need these Java runtimes to use Pi4J:

  • Java 11 for V2
  • Java 21 for V3
  • Java 25 for V4

When you want to use Pi4J in your project, you should definitely check out the Pi4J website where you can find a lot of information and many examples!

For example, for a minimal example to blink a LED (fully explained here), you need to import the dependencies and use this code:

var pi4j = Pi4J.newAutoContext();

var led = pi4j.digitalOutput().create(PIN_LED);

while (true) {
  if (led.state() == DigitalState.HIGH) {
    led.low();
  } else {
    led.high();
  }

  Thread.sleep(500);
}

Contributing to Pi4J

For full description of the code structure, how to compile... see the "About the code" on our website.

Pi4J code structure

Project Overview

Starting with Pi4J V2, the Pi4J project is prioritizing focus on providing Java programs access, control and communication with the core I/O capabilities of the Raspberry Pi platform.

Read all about it on pi4j.com: "What's New in V2".

Build Instructions

The Pi4J codebase can be built using Apache Maven 3.8+. and Java JDK 25 (since V4). The following command can be used to build the Pi4J JARs:

mvn clean install

Pi4J V2+ also includes native libraries that will need to be compiled if you are modifying any native code. Most users will never need to compile the native libraries as these artifacts are automatically downloaded
when building the Pi4J JARs from Maven repositories. One of the following commands can be used to build the Pi4J V2+ JARs and Native Libraries:

mvn clean install -Pnative
mvn clean install -Pnative,docker

# When you want to speed up...
mvn clean install -Pnative -DskipTests

NOTE: A comprehensive set of build instructions can be found in the Pi4J Documentation.

Adding a feature or solving a problem

If you have an idea to extend and improve Pi4J, please first create a ticket to discuss how it fits in the project and how it can be implemented.

If you find a bug, create a ticket, so we are aware of it and others with the same problem can contribute what they already investigated. And the quickest way to get a fix? Try to search for the cause of the problem or even better provide a code fix!

Join the team

You want to become a member of the Pi4J-team? Great idea! Send a short message to frank@pi4j.com with your experience, ideas, and what you would like to contribute to the project.

Previous Releases

License

Pi4J Version 2.0 and later is licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at: http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Copyright (C) 2012 - 2025 Pi4J