Contact04

---

Hi,

Any change that the battery status will be visable in Gui or in variable or any other way?

Thanks in advance

All my 12 contact sensors mentioned in the first post are running with the first set of batteries for over one year now.
No need to implement the battery status.

Have the same experiences. Still the first baterias over 1 year!

Thats great!
But that doesn’t mean that they don’t get empty sometime.
I would like to see that the batteries gets empty without going checking 15 sensors through the whole house periodicly to prevent an empty battery.

So it would be nice if its possible to see the status.

@lschip: Have the same opinion as you. Have several contact4 window contacts. When they will show in one year or even five years that the battery goes empty, Would be very nice to see this announced before they stop working.

Hi, as I understood the code-work is already done. I can’t estimate how much work it is to get into the stable version. Might be it is just a problem of some free time of the developers.

@lschip @OrTiN after some time I tried it again and got it running.

What I have done is the following:

• at first I made a backup of my actual homduino Installation (just copied the Folder somewhere save)
  ==> /home/pi/pimatic-app/node_modules/pimatic-homeduino
  and then I
• removed the Installation (/home/pi/pimatic-app/node_modules/pimatic-homeduino)
• installed the actual Version of homeduino from github
• installed the Version v9.0x
  and after a browser refresh the battery state is shown in the gui.
• happily removed the backup

Executed Commands:

sudo service pimatic stop
cd /home/pi/pimatic-app/node_modules/
sudo rm -rf pimatic-homeduino
git clone https://github.com/pimatic/pimatic-homeduino.git
cd pimatic-homeduino
npm install
cd
sudo service pimatic start
tail -f /home/pi/pimatic-app/pimatic-daemon.log
"crtl+c"

then there has an error occured during start up because of some variables for battery state where missing. But i just installed the version v9.0x and everything is working fine now.

sudo service pimatic stop
cd /home/pi/pimatic-app/node_modules/
cd pimatic-homeduino/
git fetch
git checkout v0.9.x
git pull
cd
sudo service pimatic start
tail -f /home/pi/pimatic-app/pimatic-daemon.log
"crtl+c"

Hi,

I just read the possible solution for the battery state.
And i followed all the steps above but the result was bad.

I started with Pimatic updated and also all plugins are updated.

During the proces I got some warning and errors (sadly my laptop rebooted suddenly for updates so I can’t copy and past the errors here).

The result was that I did’t see the status of the contacts anymore (empty).

Did I understand it right that the battery status wil come in a regulare update soon? In that case I can wait for that.

Thanks in advance.

@lschip the code of battery status has been committed by @mwittig to the actual version of the homeduino plugin. The installation of the normal plugin should provide this. Perhaps you have to uninstall your version and install standard version again.

For me, I haven’t tried it yet but will do it this weekend. So I will give a report within the next days.

@mwittig I think this thread can be marked as solved or as implemented? Thank you for your work!

Hi,

I just reinstalled homeduino by uninstalling and installing it from the plugin page.
Is this the right way?
I don’t see any difference, so no battery status for contact4 devices.

Also creating a new device (contact4, gs-iwds07) doesn’t give me the battery status.

Thanks in advance.

@lschip
Hi, same with me here. I’ve already included the code-update manually some months ago with no luck in the GUI.

Today I’ve removed the homeduino directory and let the plugin reinstall himself.
The code for the battery is definitly included and I can see the battery status changing within the debug log:
12:59:06.134 [pimatic-homeduino] debug: contact4: { id: xxxxxx, contact: true, lowBattery: true }

But no change in the GUI. I’ve also tried to add a new contact after the re-install; also no success here.

But what is strange: if I look into the variable sheet, there is only a field for the <device>.contact status himself, but no entry for the <device>.lowBattery

I tried also to generate a rule to check changes of the battery status, but the object .lowBattery (or Battery of…) is not known.
So my assumption is, that there’s something missing in the devices objects/classes lists…?
@mwittig
PLS help

@fennsen @lschip do you have installed th plugin by gui or have you already tried to install manually from git? Maybe the changes aren’t in the installation called from gui. I think this is not the git but the npm-version.

-> so perhaps try this. But backup your actual plugin folder before /home/pi/pimatic-app/node_modules/pimatic-homeduino

sudo service pimatic stop
cd /home/pi/pimatic-app/node_modules/
sudo rm -rf pimatic-homeduino
git clone https://github.com/pimatic/pimatic-homeduino.git
cd pimatic-homeduino
npm install
cd
sudo service pimatic start

Yes, I reinstalled homeduino from the GUI.

I tried your instruction before. Now I did that again. During the process I got the following messages (only the warnings and errors):

npm WARN peerDependencies The peer dependency pimatic included from pimatic-homeduino will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
-
> serialport@4.0.7 install /home/pi/pimatic-app/node_modules/pimatic-homeduino/node_modules/homeduino/node_modules/serialport
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v46-linux-arm.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@4.6.2 (node-v46 ABI) (falling back to source compile with node-gyp)
....
npm WARN deprecated nomnom@1.8.1: Package no longer supported. Contact support@npmjs.com for more info.

But then Pimatic doesn’t start anymore, only after a reboot of the Raspberry.

But I was supprised, I got the battery status now!

I am realy happy with this. Thanks for this!!!

Still a question about using rules with the battery status.

The variable of a contact device is as follows:
$bovenlicht-achter.lowBattery (attribure) false

When I try:
$bovenlicht-achter.lowBattery = “false” and bovenlicht-achter is opened then pushbullet …
I get: error [pimatic]:
Could not find an provider that decides next predicate of “$bovenlicht-achter.lowBattery = false and bovenlicht-achter is opened”.

And when I try:
$bovenlicht-achter.lowBattery = 0 and bovenlicht-achter is opened
Then nothing happens when I open this window.

When i try: $bovenlicht-achter.lowBattery changes
Then it works (value from null to false) but that is not what I want,

How can I use the lowBattery attribure in a rule?

Thanks in advance

@lschip @Fabian
you made my day!
I’ve made a complete re-install of pimatic and all plugins. And de- /re-installed node and npm before (because there was something messed up anyway since months).
Now it works (have to open / close the contact once before the icon appears).

THANKS!

@lschip said in Contact04:

lowBattery

you have to use the attribute of the device first:

if lowBattery of bovenlicht-achter is low and … then pushbullet …

Ok, thanks, I’ll try that.

And, @fennsen, I did not make your day, @Fabian did also make my day!

Thanks!

@lschip @fennsen nice to hear that it is working, but code work has been done by @mwittig.

@lschip about the rule: may be that the “when xy.lowBattery” part is only triggered by changes. So if the state is not changing, the rule will not be executed. So if your rule is not working as expected just try to change the order. But this is just a maybe…

@Fabian: No I tried that, thats why I also added “and bovenlicht-achter is opened” to test the rule…