Homeduino switches GPIO 0

---

I recently upgraded to homeduino 0.9.7 via GUI and now everytime I’m switching one light on or off, my GPIO 0-Pin gets set to IN. This causes a LED that indicates that some background task is running to turn off. I can activate it again manually via sudo gpio mode 0 out, but I don’t want to do it every time.
Unfortunately, I seem to have missed some updates in between, so I can’t tell whether it worked with 0.9.6 or not. Usually I’m not logged in as admin, that’s why.

This is my config:

    {
      "plugin": "homeduino",
      "driver": "gpio",
      "driverOptions": {},
      "transmitterPin": 4
    }

receiverPin is not set on purpose. If activated, the Raspberry Pi has a significant higher cpu load. During the next vacation receiver and transmitter will be moved to work with an Arduino anyway.

@Marie said in Homeduino switches GPIO 0:

Unfortunately, I seem to have missed some updates in between, so I can’t tell whether it worked with 0.9.6 or not.

To find out whether or not it works with an earlier version, it is possible to downgrade. You can go back to the version which you believe should work. Please keep me posted about your findings!

For example:

sudo service pimatic stop
cd /home/pi/pimatic-app
sudo rm -rf node_modules/pimatic-homeduino/node_modules
sudo npm i pimatic-homeduino@0.9.3 --unsafe-perm
sudo service pimatic start

I wanted to narrow down the revisions by date. On github and npm I only find versions like 0.8.88 which seems to be published the same day as 0.9.7. How are they related?

Maybe I just noticed because the background task was running for 3hrs instead of the usual 15mins.

I’ll figure it out this evening and keep you updated.

@Marie For pimatic 0.9 we had to introduce some breaking changes with some plugins. To ensure pimatic 0.8 users are not affected we created a seperate branch for each plugin project affected and used the “dist tag” feature of npm to publish packages as “beta” which are picked by pimatic v0.9 but not by v0.8. See also https://docs.npmjs.com/cli/tag

To get an idea of the recent commit history for pimatic-homeduino v0.9.x branch see https://github.com/pimatic/pimatic-homeduino/commits/v0.9.x Note, v0.9.5 - 0.97 are identical apart from the version number. I had to create those for technical reasons.

@mwittig Thanks. Now I see, why I missed 0.9.5 and 0.9.6

I downgraded to 0.9.1 - the GPIO port still gets switched to read. During the tests I discovered it also already happens at the start of pimatic. I think it happens when the line [pimatic-homeduino] Connected to homeduino device. appears.

The log seems fine (just the last few lines):

19:28:28.096 [pimatic] New device "Backup"...
19:28:30.167 [pimatic-homeduino] Connected to homeduino device.
19:28:30.474 [pimatic-mobile-frontend] packing static assets
19:28:30.841 [pimatic-mobile-frontend] packing static assets finished
19:28:30.851 [pimatic-mobile-frontend] rendering html
19:28:35.688 [pimatic-mobile-frontend] rendering html finished
19:28:35.801 [pimatic] Listening for HTTPS-request on port 443...
19:28:35.804 [pimatic] Listening for HTTP-request on port 80...