Release pimatic-raspbee@0.1.6

---

I found the problem and fixed it in a new version of raspbee.coffee.
And also in this update the fix for the 3 errors on startup.

I’m sorry, but now it starts propperly, but I still cannot save the discovered WarningDevice, that looks like before:

error [pimatic]: An uncaught exception occurred: TypeError: Array.prototype.indexOf called on null or undefined
    at indexOf (<anonymous>)
    at RaspBeePlugin.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:2193:43)
    at RaspBeePlugin.emit (events.js:326:22)
    at RaspBeeConnection.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee.coffee:312:10)
    at RaspBeeConnection.emit (events.js:314:20)
    at WebSocket.<anonymous> (/home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:69:16)
    at WebSocket.emit (events.js:314:20)
    at Receiver.receiverOnMessage (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/websocket.js:720:20)
    at Receiver.emit (events.js:314:20)
    at Receiver.dataMessage (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:414:14)
    at Receiver.getData (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:346:17)
    at Receiver.startLoop (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:133:22)
    at Receiver._write (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/receiver.js:69:10)
    at doWrite (_stream_writable.js:403:12)
    at writeOrBuffer (_stream_writable.js:387:5)
    at Receiver.Writable.write (_stream_writable.js:318:11)
    at Socket.socketOnData (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/ws/lib/websocket.js:795:35)
    at Socket.emit (events.js:314:20)
    at Socket.emit (/home/pi/pimatic-app/node_modules/pimatic/startup.coffee:64:24)
    at addChunk (_stream_readable.js:297:12)
    at readableAddChunk (_stream_readable.js:272:9)
    at Socket.Readable.push (_stream_readable.js:213:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)
 This is most probably a bug in pimatic or in a module, please report it!
23:01:42error [pimatic]: Cannot read property 'length' of undefined

… I’m sorry, but I have to close for today. Let’s continue tomorrow …

I know what the problem is and will update tomorrow

The problem is solved.
Please update device-config-schema.coffee and raspbee.coffee

… will check in the evening 👍

Hi @bertreb, that looks quiet well:

One is now able to switch on/off the usage of tampered and show it in the gui or not, as one likes.
Regarding battery, what you see here, is the feature ‘lowbattery’ (=ok).
‘battery’ currently seems doesn’t show anything?

Battery is ‘low’ or ‘ok’. Actual its the lowbattery sensor value or is the battery level also interesting?

As the respective deconz documentation about this siren on git is in the way, that the device supports battery and lowbattery, I would tend to have it in correctly. Otherwise I fear, that other users might be irritated about that, esp. as ‘lowbattery’ currenty (as you can see in the gui) shows up as ‘battery’

Yes i understand. The battery field only showing ok or low, was ment as a simplification. You can look at the percentage, but at the end if the battery is getting low and needs to be changed is of interest.

Sure, got your point in the end it is regardless. My intention only is about folks who might not read this lengthy thread and might become irritated …

Btw.
Checked besides also to use also the SmartPlug and the WarningDevice, and their attributes, in rules, which also seems working perfectly.
What not is given, is that they are shown up with their device names, but only with their Device IDs. Again here, for me that works, but maybe for others this might be not that convenient? - sorry I don’t want to become Mr. 120%

I will add the battery level.
What device names are you meaning. I use still the original naming convention of pimatic-raspbee

Regarding the names I now also was a bit irritated. I quickly checked in the rule gui of my Prod Pimatic and also there, sometimes the device name is offered in parallel to the device ID, in other cases only the name OR the ID is offered.
I couldn’t read a kind of systematic out here …, however …

In the rule system device ID and device names should be both available.
Thats a plugin independent mechanism. But i didn’t check it lately.

I updated the plugin with the battery value, please update device-config-schema.coffee and raspbee.coffee

… well, I would say: PERFECT and nothing more to add

I guess this will now become a really meaningfull update of pimatic-raspbee

Hopefully soon, as I’m already designing some rules to monitor our washing-machine with the plug, to sent messages upstaires if it has finished …
… and for sure already made planes how to enhance the entire shutter-steering, not to send around each command twice and have the chance for a more intelligent interaction between the morning/evening steering and the sun-covering steering.
I can tell you, that already caused some lengthy debates here in the past

Did you hear anything from @kosta on that? - or will you go to implement this next version?

I’m still waiting to hear from @Kosta.
The alternative is of course publishing pimatic-raspbee-plus, but lets wait a bit more.

Yep, we will do.
But thanks a lot here to you @bertreb, for that last-weeks testing and implementation runs!
That was really cool and a lot of fun with perfect results

Hi @bertreb, I may have mentioned that I already ordered some more of the shutter switches at Ali, but when they arrived yesterday, I recognised, that I accidentally ordered an other type of them (SM-SW101-CZ vs, now: SC400W-EU). They look very similar and it was a special pricing, that’s why that happened.

However, In general they seems behaving similar, but with some minor specialities.
So if you have time and you might feel additionally challenged by this, we might go in another round here 😉

If not, I would understand, no question and fully accepted 👍🙃

No problem. What are the differences / extras?