Release pimatic-raspbee@0.1.6

---

Ahh, I wasn’t aware of the already build-in mechanism for the adjustment

With regard to ‘mixed’:
Assume the current position is like shown here.
If I now click on ‘open’ the gui directly flips to ‘close’ and the slider starts moving to the left and the percentage decreases.

Clicking on ‘close’ causes the effect the other way round. The gui directly flips to ‘open’ and the slider starts moving to the right and the percentage increases.

With regard to 5-95%:
The shown percentage do never reach 0% or 100%. 5% is the smallest and 95% the largest value.

You are using the latest version ?

sent you an email with the version I’m using
I lost a bit the overview from last week …

I received it. That version is still based on the 50% = stop.
I will change the next version back into the commands according to the api.

… well thats getting a nice run this evening

Testing with the curl command I now got also the siren running.

• only blinking (silent alarm)
• blinking and siren
• stopping it

curl -X PUT http://127.0.0.1:8080/api/xxxxxxxxx/lights/x/state -d '{"alert":"blink"}' -s
curl -X PUT http://127.0.0.1:8080/api/xxxxxxxxx/lights/x/state -d '{"alert":"select"}' -s
curl -X PUT http://127.0.0.1:8080/api/xxxxxxxxx/lights/x/state -d '{"alert":"none"}' -s

That’s really cool!

Nice, it reenabled the api functions, in an update of raspbee.coffee.

Still needs to be tested.
When you post the test results. If needed I will fix and update raspbee.coffee tomorrow.

well, I’m sorry I have to get up early at 6am, thus I will continue tomorrow evening.

Hope that is ok for you Good night for now …

Hi, sorry might have gotten you wrongly last night. I thought that you would do it later, but I guess that wasn’t how you ment it
However, just did a quick test with the currwent raspbee.coffee.

But problem now seems to be, that while trying to get the device newly into Pimatic, there is no RaspBeeCover device, as it has been in befor:

Thus I cannot test the new file.

Please update the file raspbee.coffee again (made a small update).
To be sure delete the files in directory .js in the directory pimatic-app/node_modules/pimatic-raspbee
command is rm -rf .js (this forces compile of all the coffee files)

@bertreb said in Release pimatic-raspbee@0.1.6:

rm -rf .js

Hi did as you wrote, but it stays the same, no cover- or shutter-device to choose.
Shooting the commands via curl still works.

Have to continue in the evening …

Ok, the new version of the plugin is not loading, and there should be a debug message (in the beginning of the log after restart), saying what the problem is.
And this for the evening action.

@bertreb said in Release pimatic-raspbee@0.1.6:

there should be a debug message

Hi, to be sure I did the whole procedure again, but still no cover device.
Log shows as following:

20:37:00.823 [pimatic] info: Starting pimatic version 0.9.54
20:37:00.829 [pimatic] info: Node.js version 10.22.1
20:37:00.830 [pimatic] info: OpenSSL version 1.1.1g
20:37:02.603 [pimatic, ppm] info: 2.15.12
20:37:02.651 [pimatic] info: Loading plugin: "pimatic-cron" (0.8.8)
20:37:03.094 [pimatic] info: Loading plugin: "pimatic-mobile-frontend" (0.9.16)
20:37:03.669 [pimatic] info: Loading plugin: "pimatic-raspbee" (0.1.7)
coffee-cache: compiling coffee-script file "raspbee.coffee"...Done
coffee-cache: compiling coffee-script file "color.coffee"...Done
coffee-cache: compiling coffee-script file "raspbee-connector.coffee"...Done
coffee-cache: compiling coffee-script file "action.coffee"...Done
coffee-cache: compiling coffee-script file "predicate.coffee"...Done
coffee-cache: compiling coffee-script file "raspbee-config-schema.coffee"...Done
20:37:10.205 [pimatic] info: Loading plugin: "pimatic-shell-execute" (0.9.11)
20:37:10.234 [pimatic-cron] info: the time is: Mon Feb 22 2021 20:37:10 GMT+0100 (GMT+01:00)
coffee-cache: compiling coffee-script file "device-config-schema.coffee"...Done
20:37:11.033 [pimatic] info: New device "JaloSwitch01"...
20:37:11.294 [pimatic] error: Could not parse rule "when lift of Window01l233ae541bbb7ac98c42977753884b8d23 = 60 then switch Open+Close on": Could not find an provider that decides next predicate of "lift of Window01l233ae541bbb7ac98c42977753884b8d23 = 60".
20:37:11.296 [pimatic] error: Could not parse rule "when Open+Close is turned on then dim raspbee Window01l233ae541bbb7ac98c42977753884b8d23 to 75%": Could not find an provider that decides next predicate of "Open+Close is turned on".
20:37:11.297 [pimatic] error: Could not parse rule "when $shutterstatus is increasing or when $shutterstatus is decreasing then set raspbee the Window covering device 1 to $shutterstatus": Could not find an provider that provides the next action of "set raspbee the Window covering device 1 to $shutterstatus".
20:37:11.299 [pimatic] error: Could not parse rule "when $shutterstatus is decreasing then set raspbee raspbee_l1a73e9557e6ac5552ae871702960c9b13 to $shutterstatus": Could not find an provider that provides the next action of "set raspbee raspbee_l1a73e9557e6ac5552ae871702960c9b13 to $shutterstatus".
20:37:11.335 [pimatic-raspbee] info: Connection establised
20:37:11.337 [pimatic-raspbee] info: Name ConBee-GW02
20:37:11.338 [pimatic-raspbee] info: API 1.16.0
20:37:11.339 [pimatic-raspbee] info: Software Version 2.5.86
20:37:11.340 [pimatic-raspbee] info: API key valid
20:37:11.389 [pimatic-raspbee] info: Event receiver connected.
20:37:11.519 [pimatic-mobile-frontend] info: packing static assets
20:37:13.029 [pimatic-mobile-frontend] info: packing static assets finished
20:37:13.035 [pimatic-mobile-frontend] info: rendering html
20:37:18.598 [pimatic-mobile-frontend] info: rendering html finished
20:37:18.637 [pimatic] info: Listening for HTTP-request on port 80...
20:37:24.867 [pimatic-raspbee] debug: new message received
20:37:24.878 [pimatic-raspbee] debug: { attr:
20:37:24.878 [pimatic-raspbee] debug:>   { id: '1',
20:37:24.878 [pimatic-raspbee] debug:>     lastannounced: null,
20:37:24.878 [pimatic-raspbee] debug:>     lastseen: '2021-02-22T19:37Z',
20:37:24.878 [pimatic-raspbee] debug:>     manufacturername: 'dresden elektronik',
20:37:24.878 [pimatic-raspbee] debug:>     modelid: 'ConBee II',
20:37:24.878 [pimatic-raspbee] debug:>     name: 'Configuration tool 1',
20:37:24.878 [pimatic-raspbee] debug:>     swversion: null,
20:37:24.878 [pimatic-raspbee] debug:>     type: 'Configuration tool',
20:37:24.878 [pimatic-raspbee] debug:>     uniqueid: '00:21:2e:ff:ff:06:15:e6-01' },
20:37:24.878 [pimatic-raspbee] debug:>  e: 'changed',
20:37:24.878 [pimatic-raspbee] debug:>  id: '1',
20:37:24.878 [pimatic-raspbee] debug:>  r: 'lights',
20:37:24.878 [pimatic-raspbee] debug:>  t: 'event',
20:37:24.878 [pimatic-raspbee] debug:>  uniqueid: '00:21:2e:ff:ff:06:15:e6-01' }
20:37:24.983 [pimatic-mobile-frontend] info: rendering theme: graphite/water
20:37:27.708 [pimatic-mobile-frontend] info: rendering theme finished
20:37:27.720 [pimatic-raspbee] debug: new message received
20:37:27.723 [pimatic-raspbee] debug: { attr:
20:37:27.723 [pimatic-raspbee] debug:>   { id: '2',
20:37:27.723 [pimatic-raspbee] debug:>     lastannounced: '2021-02-21T20:08:24Z',
20:37:27.723 [pimatic-raspbee] debug:>     lastseen: '2021-02-22T19:37Z',
20:37:27.723 [pimatic-raspbee] debug:>     manufacturername: '_TYZB01_dazsid15',
20:37:27.723 [pimatic-raspbee] debug:>     modelid: 'TS0302',
20:37:27.723 [pimatic-raspbee] debug:>     name: 'WindCov01',
20:37:27.723 [pimatic-raspbee] debug:>     powerup: 7,
20:37:27.723 [pimatic-raspbee] debug:>     swversion: '0xFFFFFFFF',
20:37:27.723 [pimatic-raspbee] debug:>     type: 'Window covering device',
20:37:27.723 [pimatic-raspbee] debug:>     uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' },
20:37:27.723 [pimatic-raspbee] debug:>  e: 'changed',
20:37:27.723 [pimatic-raspbee] debug:>  id: '2',
20:37:27.723 [pimatic-raspbee] debug:>  r: 'lights',
20:37:27.723 [pimatic-raspbee] debug:>  t: 'event',
20:37:27.723 [pimatic-raspbee] debug:>  uniqueid: 'ec:1b:bd:ff:fe:8f:10:92-01' }

Strange, can you look into the raspbee.coffee and check if the RaspBeeCover class is present?

@bertreb said in Release pimatic-raspbee@0.1.6:

raspbee.coffee

sure, but there seems to be no in:

deviceClasses = [
        RaspBeeSystem,
        RaspBeeMotionSensor,
        RaspBeeContactSensor,
        RaspBeeLightSensor,
        RaspBeeSwitchSensor,
        RaspBeeMultiSensor,
        RaspBeeWaterSensor,
        RaspBeeRemoteControlNavigator,
        RaspBeeSwitch,
        RaspBeeDimmer,
        RaspBeeCT,
        RaspBeeRGB,
        RaspBeeRGBCT,
        RaspBeeDimmerGroup,
        RaspBeeRGBCTGroup,
        RaspBeeGroupScenes,
        RaspBeeRGBDummy
      ]


I additionally searched via 'search' trough the whole file, but found nothing```

I shortly checked a former raspbee-coffee and there I found an entry 'RaspBeeCover' in that section ...

You do not have the latest raspbee.coffee from bertreb/pimatic-raspbee

I downloaded it from here: https://github.com/treban/pimatic-raspbee
Via the function: Code download ZIP - green button
That’s how I also did it the last days.

OMG!!! the wrong fork!!!

Yes because thats the original ‘non cover’ plugin.

You need to download it from my forked repos https://github.com/bertreb/pimatic-raspbee

… what a fault, I’m really sorry …

OK and who wonders, now it works. Let me check the behaviour in detail …

Great progress

It works like following:
raspbee stop now triggers stop on the device
range of the slider and the percentages are now back from 0 - 100%

Out of the neutral 50% position:
clicking the ‘open’ raspbee button triggers correctly open on the device …, but then raspbee button directly flips to close and open percentages and slider decreases down to null.
when device triggers itself back to ‘neutral’ (50%), the raspbee button switches back to stop and the percentages and slider goes back to 50%

clicking the ‘close’ raspbee button triggers correctly close on the device …, but then the same effect as above happens, only the other way around

The same happens when moving the slider:
moving it down, correctly trigger close on the device, but the wrong behaviour, explained as above, happens also here

an additional thought: when in the end the shutter device flips itself back to stop (50%), also the raspbee device is send back to this position, as explained above. But this leads then to the fact, that looking on the Pimatic frontend, one would think the shutter is at 50%, allthough it is somewhere else …

Hope this is understandable …