Do you have the newest deconz version installed?
You have to pair it as a sensor. It won’t appear in the phoscon gui but is available via Api/pimatic.
New Plugin - [pimatic-raspbee]
Do you have the newest deconz version installed?
You have to pair it as a sensor. It won’t appear in the phoscon gui but is available via Api/pimatic.
Thx. After the 1001 time of pairing I got a positive response of the phoscon gui. And as you mentioned the gui got no new device, but the device can be dicovered by pimatic. Hopefully current codes will be replaced by press, double press and long press (“long press” seems not to be existent currently)…
@ortin I have struggled with this button as well, what seemed the best way to get it in pairing mode?
I pushed the pair button for more then 5s. (to be exact 7s). My first tries were not successful, but after some tries it works. I have now three buttons paired.
I really miss the long press function…
Thanks Ortin, I got two of them connected and a third seemed to connect in Deconz but it didn show up in Pimatic. I expected the long press to work with these buttons, but I ques we are out of luck. :|
I think this will come in future.
@kosta have you seen this post already?
https://forum.pimatic.org/topic/4490/script-to-dim-lights-slowly
I do not know how complicated this will be to implement in your plugin but this would be a nice feature. Perhaps within the rule structure like it is already available in the hue plugin "dim to 100 transition time 10“
This is how I solved the dimming. I use a rule for increasing or decreasing the dim level. I use steps of 10%.
Rule:
{
"id": "lamp-overloop-achter-lager",
"name": "lamp overloop achter lager",
"rule": "when [$raspbee_sw_2.state = \"3001\" or $raspbee_sw_3.state = \"3001\"] and if $dimlvl-overloop-achter > 0 then $dimlvl-overloop-achter = $dimlvl-overloop-achter - 10 and after 1 second dim raspbee_INNR_RB165_002 to $dimlvl-overloop-achter",
"active": true,
"logging": true
},
Raspbee_sw_2 and raspbee_sw_3 are Trust zyct-202 Switches. I use a variable to keep track of the dimlevel of the lamp raspbee_INNR_RB165_002
I think this rule should also work:
when every 1 minute and if dimmer-switch is on and $dimlevel > 0
then dim light to $dimlevel and after 1 second $dimlevel = $dimlevel - 5
The deconz api supports a transitiontime.
(Transition time in 1/10 seconds between two states)
The lights from the Raspbee plugin already have a transtime configuration parameter.
(default 5)
but this parameter is the default value for all actions.
I will add a new action provider because I use the pimatic default dim action,
with an additional option to set the transition time.
After some trouble I got my Conbee Stick to work. But this was because I want to use a still existing OrangePi.
To make it easier for others, I have written a HowTo.
It is also important that you have to reboot pimatic-raspbee twice after installing the plugin.
One time after installing and the second time after entering the IP address of the Deconz software.
Today my Osram Smart Plugs arrived. I was able to pair them in deCONZ and find them in pimatic.
Unfortunately it doesn work to switch them with die RaspBeeSwitch device itself.
Switching in rules with “turn on / switch on” works fine.
Switching the device in the UI does only work once until I delete and re-add the device.
A workaround is a dummy switch with two rules (on/off), but it would be great if the device would work ootb.
EDIT: Restart of the deconz service solved the problem.
@SaxnPaule That’s good to hear. I have the plug too And it runs without problems.
My system with the RaspBee on Raspberry works very well.
But now I have created a new problem for myself. I want to switch from RasBee to ConBee.
I have created a new system with proxmox. Among other things with an instance for deCONZ. As OS I installed Debian. Then I went through the procedure for the installation of ConBee.
Everything seems to be working, but I can’t connect to a USB stick (ConBee).
The USB port is passed through by Proxmox.
But something seems to be wrong with me, because I can’t get a connection to the USB stick in phoscon (WebGUI).
The WebGUI tells me firmware: not connected
And I can do whatever I want, (Ikea device, 6 times on / off etc.) I can’t get a device connected.
Were my problem could be? I have no idea at the moment…???
Maybe my problem’s wrong here, too. Maybe Dresden-Elektronik is the right contact!?
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
@Thrusty I have recognized the connecting problem of the Conbee at a raspberry of a friend. The problem was the unstable wifi network. After switching to cable everything was working fine. I don’t believe so in your case, but perhaps you can check the network connection just in case…
@fabian
Thanks for the answer. I think I can rule out this problem. The machine is connected via LAN.
I can also access phoscon without any problems.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
@Thrusty
Does the proxmox usb-passthrough work correctly?
check if the firmware uploader recognizes the device correctly.
try this:
https://www.dresden-elektronik.de/funktechnik/service/download/driver/?L=1
Download -> GCFFlasher V2_11 (Ubuntu Linux)
pi@sys:~ $ sudo systemctl stop deconz # stop the deconz service
pi@sys:~ $ sudo dpkg -i gcfflasher-latest.deb
pi@sys:~ $ sudo apt update
pi@sys:~ $ sudo apt -f install
pi@sys:~ $ sudo GCFFlasher -l
here should be an output. then you can be sure,
that the hardware access is working.
@kosta
Hi and thanks for the help.
My USB port seems to have been transferred correctly and proxmox usb-passthrough work’s correctly.
sudo GCFFlasher -l
GCFFlasher V2_11 (c) dresden elektronik ingenieurtechnik gmbh 2017/12/10
1 FTDI device found
device | vendor | product | serial | description
-----------|-----------|------------|------------|------------------
0 | 0x0403| 0x6015 | DM01BF47 | FT230X Basic UART
Nevertheless phoscon shows me that the firmware is not connected. Shouldn’t there be the firmware version of the stick?
And a lamp still can’t be registered.
The ZigBee channel is set to 0 and the network ID also.
I’m doing something wrong.
"Really, I'm not out to destroy Microsoft. That will just be a completely unintentional side effect." 09-28-2003, LINUS TORVALDS (http://www.nytimes.com)
That’s strange. Have you done a manual firmware update?
maybe this helps.
you can also run deconz in debug mode:
add --dbg-error=1 --dbg-info=2 to the start paramter
sudo vi /etc/systemd/system/multi-user.target.wants/deconz.service
edit this line
ExecStart=/usr/bin/deCONZ -platform minimal --http-port=80 --dbg-error=1 --dbg-info=2
then
sudo systemctl daemon-reload # reload systemd settings
sudo systemctl restart deconz # restart deconz
check logfiles:
tail -f /var/log/syslog -n100 | grep -i deconz