Release pimatic-raspbee@0.1.6

---

ahhh! that now also works!

I think having ‘only’ these three options is, in context of a rule, sufficient enough, as then for sure by rule one can steer the seconds to move and then to stop…

well what to say - great work you did here the last evenings!
That was really impressing

Now it would be really cool, if @kosta (?) would find the time to migrate all the new features into a new raspbee version.

Will you try to request that again?

And the result is good.

It’s better to use the same logic to set the cover to a position.
So i added for the rule 'set raspbee <cover device id> to <0-100>'
Update the file action.coffee

And on updating pimatic-raspbee.
If @kosta is unavailable to update pimatic-raspbee. The alternative is to create an extended version called pimatic-raspbee-plus.
And like the cover and the siren more zigbee devices will popup and can be added to pimatic-raspbee-plus.

Hi again, shortly out of a sunny Saturday afternoon

Just tested the percentage moving and it also works fine

Regarding an own fork, maybe ‘pimatic-raspbee-plus’. In general the idea is good to proceed if really @kosta isn’t available any longer.
But beyond I would have a bit the fear, that here also something like with IO Broker happens, where you meanwhile can find 146 forks only for Zigbee. I would have no clue how to handle such as a non-developer …

Hi @bertreb, I played the whole evening around with the raspbee.coffee to get my just arrived Blitzwolf BW-SHP13 (=Heiman TS0121) running incl. measurement of voltage and currency, but in the end I was not able to get this done.
The plug itself is working (on/off), but without showing the values.

As I would like to understand a bit better how this works (with a more simple device than a shutter ), would you have a tip, in terms of: do 1., 2., 3., … for me?

Thanks a lot

Hey guys. I’m very busy at the moment. Family … home … work. there is no much time for pimatic.That cuts me to the quick. I had started some changes, but I didn’t get to the end.
I can integrate @bertreb excellent work. I’ll definitely be looking at the code for the next few days.
and hey. it’s a community project. before we fork the plugin, I’d rather give someone maintainer rights.

Great to hear from you @kosta
Super that you will try to take the time
… and I know such phases in life definitely very well, thus don’t worry 😉… and as I just recognised, greetings around the corner, out of the Bergisches Land 😄

@bertreb, if @kosta will now try to take the time, alltough I was trying to learn a bit more about device-integration, shouldn’t we then better try to give it a quick shot this evening to get the plug also running? - if you have the time?

We would then see directly 4 additional devices in the next raspbee version

@kosta said in Release pimatic-raspbee@0.1.6:

Hey guys. I’m very busy at the moment. Family … home … work. there is no much time for pimatic.That cuts me to the quick. I had started some changes, but I didn’t get to the end.
I can integrate @bertreb excellent work. I’ll definitely be looking at the code for the next few days.
and hey. it’s a community project. before we fork the plugin, I’d rather give someone maintainer rights.

Hi kosta, good to hear from you. You can make me maintainer.
I assume you will make the changes in pimatic-raspbee yourself?

@pedder said in Release pimatic-raspbee@0.1.6:

Blitzwolf BW-SHP13

What did the discovery said about the device type?
You can play with the RaspBeeSwitch to switch (like you already did) and the RaspBeeMultiSensor to get the values.
An 1, 2, 3 instruction for building isn’t that easy, but roughly I take the following steps for adding a new RaspBeeDevice:

1. pick on of the existing base devices (multi-sensor, switch, light, etc)
2. define the gui (buttons, switches, presence(Online/offline) and attributes)
3. add the gui to the 2 files (app/raspbee-template.coffee and app/raspee_template.jade)
4. for handling extra actions add an action handler in action.coffee
5. add the new device class in device-config-schema.coffee
6. add the new device to raspbee.coffee

The coding takes place in raspbee.coffee, action.coffee, app/raspbee-template.coffee and app/raspee_template.jade.

@pedder said in Release pimatic-raspbee@0.1.6:

Great to hear from you @kosta
Super that you will try to take the time
… and I know such phases in life definitely very well, thus don’t worry 😉… and as I just recognised, greetings around the corner, out of the Bergisches Land 😄

@bertreb, if @kosta will now try to take the time, alltough I was trying to learn a bit more about device-integration, shouldn’t we then better try to give it a quick shot this evening to get the plug also running? - if you have the time?

We would then see directly 4 additional devices in the next raspbee version

Just to help me understand? What do you want to get running this evening ?

Sorry, I might have been too short regarding this
I meant the switch-plug from Blitzwolf/Tuya, I mentioned below. In General it works with raspbee, but the measures of voltage and currency, which it delivers, are currently not shown, and I think not captured at all by raspbee, in the gui.
In deCONZ it is definitely already implemented.

@bertreb said in Release pimatic-raspbee@0.1.6:

add the gui to the 2 files (app/raspbee-template.coffee and app/raspee_template.jade)

Aha, especially that step I missed, which is then not wondering, that when starting pimatic, error messages with regard to incorrect ‘config items’ popped up.
I already thought that there is something to maintain elsewhere 😉

Ok we can spend some time on the Blitzwolf/Tuya device.
The error messages seem not related to those files. In general when you don’t change these files in the gui you see the values/states and you can’t initiated an action (like push a button)

Illegal config items are mostly what the error message says. In the file config.json Items in a device config that are not defined in the device-config-schema.coffee file

For the Blitzwolf/Tuya device the RaspBeeSwitchSensor is already available in the plugin. Its a switch with sensor values.
After discover select in the class ‘RaspBeeSwitchSensor’ and add the right sensorId’s and supports items.
For the support items try ‘voltage’ and ‘current’. And look into the debug and see the SensorId’s being sent bij Deconz.
But i’m not sure that this will lead to the right solution, because the on/off switch will probably be missing and that seems essential for a switch 😅

@bertreb said in Release pimatic-raspbee@0.1.6:

RaspBeeSwitchSensor’ and

again: OMG, sometimes one doesn’t see the forest as of to much trees

Surprisingly searching and connecting the plug-switch today, it’s class directly showed up as a ‘RaspbeeSwitchSensor’, which wasn’t the case yesterday, and now one can directly see all the supported values.
What I learned in additon about such devices, that one has to get them into Pimatic twice, as the switch-functionallity seems only becoming available as a pure ‘RaspbeeSwitch’. I tried to put in also the switch ID manually in the ‘RaspbeeSwitchSensor’, but that always ends with ‘Error: Device with ID: 5 not found’

Thanks for the hint and also for your instructions about which files have to be edited in which form to get in new stuff.
Thus the plug-switch I can now directly move to my Prod environment and for the shutter-switch and the siren I will wait for the update

@bertreb said in Release pimatic-raspbee@0.1.6:

And look into the debug and see the SensorId’s being sent bij Deconz.

Hi again, on my Prod I’m not able to detect the right IDs for the values, as there the device is firstly always detected as simple switch. In the .log there is also nothing to find about this. Also triggering the switch doesn’t show anything in the .log, allthough it switches.

And the IDs seems to be other here, as I already tried to use the ones from my Dev, but they also doesn’t work.
I tried all numbers from 1-40, but nothing works.

I will test again tomorrow, maybe then the device will also be firstly deteced as ‘MultiSensor’ as on my Dev …!?

… further on thinking:
On my Dev we exchanged 6 files in total, coming from your repository @bertreb. Maybe there was something else in, which might lead now to this different behaviour, when trying to configure the plug in my Prod?

Lets start to check what Deconz is using for the Blitzwolf BW-SHP13.
Is it a sensor or a light?

Hi, Phoscon discovered it as a light, same as the Hue plugs.
Do you need data from deCONZ itself? - I anyhow planned to check via the deCONZ gui in the evening…