I’m having trouble with the Plum binding.
I recently built and bought a new home server, and migrated all of my services over from my old 2008 Dell to it. Most everything is working properly (and faster) on the new build, but the major exception is my Plum binding. It looks like Plum has gone under, but I don’t think that’s the cause of my problems (thought it could potentially complicate solutions). The binding worked up until the day I made my transition over to the new server.
It’s strange because the motion events are passed as expected via the binding, but no light control is possible. Based on the logs, it looks like some kind of java permissions issue, but I’m at a loss as how to fix it.
The binding appears to start fine:
2019-04-02 01:55:45.093 [INFO ] [g.openhab.binding.plum.PlumActivator] - Plum binding has been started.
2019-04-02 01:55:45.107 [INFO ] [ing.plum.internal.PlumMotionWatchdog] - Starting Plum motion sensor watchdog
2019-04-02 01:55:45.107 [WARN ] [enhab.binding.plum.PlumActiveBinding] - The Plum Binding does not support runtime updates. Restart OpenHAB for item changes to take effect
2019-04-02 01:55:45.109 [INFO ] [b.core.service.AbstractActiveService] - Plum has been started
2019-04-02 01:55:45.297 [INFO ] [ing.plum.internal.PlumMotionWatchdog] - Starting Plum motion sensor watchdog
2019-04-02 01:55:45.300 [INFO ] [.plum.internal.PlumTCPStreamListener] - Starting monitor thread for Plum IP: 192.168.1.91
2019-04-02 01:55:45.298 [INFO ] [ding.plum.PlumGenericBindingProvider] - processing item "V_3DIN_Fixture_MotionContact" read from .items file with cfg string 192.168.1.91:bfe1363d-1286-4211-bf2c-a1c184e7d9ad#motion
2019-04-02 01:55:45.301 [INFO ] [ing.plum.internal.PlumMotionWatchdog] - Starting Plum motion sensor watchdog
2019-04-02 01:55:45.301 [INFO ] [.plum.internal.PlumTCPStreamListener] - Starting monitor thread for Plum IP: 192.168.1.92
2019-04-02 01:55:45.301 [INFO ] [ding.plum.PlumGenericBindingProvider] - processing item "V_3KIT_Fixture_MotionContact" read from .items file with cfg string 192.168.1.92:db74fb2a-7c68-46b2-ac55-b6fc7fb4beca#motion
2019-04-02 01:55:45.302 [INFO ] [ing.plum.internal.PlumMotionWatchdog] - Starting Plum motion sensor watchdog
2019-04-02 01:55:45.302 [INFO ] [ding.plum.PlumGenericBindingProvider] - processing item "A_3DIN_Fixture_Dimmer" read from .items file with cfg string 192.168.1.91:bfe1363d-1286-4211-bf2c-a1c184e7d9ad#dimmer
2019-04-02 01:55:45.301 [INFO ] [ding.plum.PlumGenericBindingProvider] - processing item "V_3KIT_Fixture_MotionContact" read from .items file with cfg string 192.168.1.92:db74fb2a-7c68-46b2-ac55-b6fc7fb4beca#motion
However, these then appear in the logs at regular intervals, one for each of my two LightPads:
2019-04-02 01:45:50.788 [ERROR] [enhab.binding.plum.PlumActiveBinding] - Plum HTTP Request to IP 192.168.1.91 returned ERROR javax.net.ssl.SSLException: Received fatal alert: insufficient_security
2019-04-02 01:45:50.889 [ERROR] [enhab.binding.plum.PlumActiveBinding] - Plum HTTP Request to IP 192.168.1.92 returned ERROR javax.net.ssl.SSLException: Received fatal alert: insufficient_security
Old build:
2008 Dell Studio (I don’t see anything else on the case and it’s taken apart)
Ubuntu 16.04 LTS
openHAB 2.4 Release inside a Docker (via systemd)
New Build:
AMD Ryzen 5 2600 processor
ARock B450 motherboard
32 gb RAM
Ubuntu 18.10
openHAB 2.5M1 inside Docker (again, as a systemd service)
The new build was set up with a few minor changes that I don’t think are in play, but I’ll include anyway. Shinobi (CCTV) and node-red were both installed on bare metal (for various reasons). On the previous setup they were both containers.
What I’ve tried:
Installed Zulu JDK 8 (on host, obviously)
Crypto policy = unlimited (see my openhab.service file below)
Ensured that openhab user (9001) has permission to read the binding jar
Cleared the cache
Uninstalled and reinstalled binding
Lightpads and server all use static IPs (assigned by router)
Here’s my systemd service file:
[Unit]
Description=openHAB 2
Requires=docker.service
After=docker.service
[Service]
Restart=always
ExecStart=/usr/bin/docker run --name=%n --net=host --tty \
-v /etc/localtime:/etc/localtime:ro \
-v /etc/timezone:/etc/timezone:ro \
-v /opt/openhab/conf:/openhab/conf \
-v /opt/openhab/userdata:/openhab/userdata \
-v /opt/openhab/addons:/openhab/addons \
-v /opt/openhab/.java:/openhab/.java \
--device=/dev/ttyUSB0 \
--device=/dev/ttyACM0 \
-e USER_ID=9001 \
-e GROUP_ID=9001 \
openhab/openhab:milestone
ExecStop=/usr/bin/docker stop -t 2 %n ; /usr/bin/docker rm -f %n
[Install]
WantedBy=multi-user.target
Even though the Plum is essentially a dead product, I was hoping to still get some good years out of use of them. They are attractive and integrate really well with openHAB. I would be really grateful for some advice!