And can you check whats json is received when you tamper with the siren?
-
I switched the contact now several times, but there only something comes in when ‘opening’ the contact, resp. when I let the contact go (I believe) to it’s alarm position (pin looks out of the case)
It looks like this:21:32:45.339 [pimatic-raspbee] debug: new message received 21:32:45.342 [pimatic-raspbee] debug: { attr: 21:32:45.342 [pimatic-raspbee] debug:> { id: '4', 21:32:45.342 [pimatic-raspbee] debug:> lastseen: '2021-02-25T20:32Z', 21:32:45.342 [pimatic-raspbee] debug:> manufacturername: 'Heiman', 21:32:45.342 [pimatic-raspbee] debug:> modelid: 'WarningDevice-EF-3.0', 21:32:45.342 [pimatic-raspbee] debug:> name: 'WarnDev01', 21:32:45.342 [pimatic-raspbee] debug:> swversion: '2020.8.20', 21:32:45.342 [pimatic-raspbee] debug:> type: 'Warning device', 21:32:45.342 [pimatic-raspbee] debug:> uniqueid: '84:2e:14:ff:fe:f5:21:79-01' }, 21:32:45.342 [pimatic-raspbee] debug:> e: 'changed', 21:32:45.342 [pimatic-raspbee] debug:> id: '4', 21:32:45.342 [pimatic-raspbee] debug:> r: 'lights', 21:32:45.342 [pimatic-raspbee] debug:> t: 'event', 21:32:45.342 [pimatic-raspbee] debug:> uniqueid: '84:2e:14:ff:fe:f5:21:79-01' }
In addition to smile: As from ‘ghost-hands’ suddenly the 1sec alarm works with the siren
Exactly as last time … -
is there a special syntax to use?
The rule editor doesn’t offer the device by itself.
Here the offering of further commands/devices stops:Also open or move seems not working …
PS.
This siren is a hell-machine. It starts howling also when it is plugged off from the power supply and then pressing the buttons in the gui … … thus normaly I would guess that this would be meaningful for the tamper functionality, however … -
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 impressingNow 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:- pick on of the existing base devices (multi-sensor, switch, light, etc)
- define the gui (buttons, switches, presence(Online/offline) and attributes)
- add the gui to the 2 files (app/raspbee-template.coffee and app/raspee_template.jade)
- for handling extra actions add an action handler in action.coffee
- add the new device class in device-config-schema.coffee
- 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 😅