Sure and it is really wondering why it disappeared there - have no clue.
However, learned it newly and the I get in Pimatic discovery this:
So again as before, as two devices:
and observing now a few minutes, but only power seems to be updated:
Release pimatic-raspbee@0.1.6
Sure and it is really wondering why it disappeared there - have no clue.
However, learned it newly and the I get in Pimatic discovery this:
So again as before, as two devices:
and observing now a few minutes, but only power seems to be updated:
… quickly searched for another appliance, with more power, but it stays the same:
I will shortly check this via the deconz gui, to verify that the device measures in general …
in deconz current is also measured:
Did you update app/raspbee-template.jade and a clear cache/refresh gui?
It’s correct that there are 2 devices discovered: SmartSwitch and MultiSensor.
You don’t need to add the MultiSensor to the gui.
well interesting, back to Pimatic, now everything is shown:
maybe the deconz restart has helped!?
But when adding only the MultiSensor, I will have no on/off Button!?
Let me check this again …
ok, now the SmartDevice discovery shows this:
But when adding to the gui, it seems not capturing any data:
If discovering then the MultiSensor, it looks like this:
and adding this to the gui, it shows values, but seems again only beeing updating the power:
Using the sensor IDs (2+3) from the MultiSensor in the SmartDevice, also doesn’t trigger the smart device to show up data.
I restartet additionally deconz and pimatic also doesn’t help.
I added default values for the SmartSwitch. Thats why they show Unknown.
And i added the check on the SensorID’s when receiving sensor data. That was missing. So leave them in.
You can update raspbee.coffee for these changes
your defaults now in, but also after manually adding the known IDs, the values are staving ‘0’, allthough I waited now and switched on/off a couple of times:
yep, that looks much better:
but still power is the only value how seems updating.
You see the pike up/down there, but current stays the same …
edit: consumption has now also updated
I was also starting to think in that direction…
Maybe there is a parameter which can be adjusted via the deconz-gui?
I will check this the next days.
For today I would say: Mission Accomplished
Let’s close for now and thanks a lot again!
It would really be cool then, to get this device also into the update
Short ping, as I just realised (having the setup with the plug and the shutter device running over night).
There seems to be an interference btw. the devices.
I come back in the evening.
I found a way to do the discovery of Smart Plugs, without big impact.
The only consequence is that the sensors are discovered before the lights (now its the other way around).
The new version of raspbee.coffee can be downloaded and i’m curious if it works?
well, that’s really wondering, still in my Dev environment:
When the plug is switched ‘off’ and then switching the gui-button of the new shutter to ‘open’, the button of the plug also switches to ‘on’, but it seems not sending anything (plug itself stays ‘off’).
The same happens (gui plug button from ‘off’ to ‘on’, when switching the shutter button from ‘close’ to ‘stop’, also w/o triggering the real plug.
Having the gui-button of the new shutter at ‘stop’ or ‘open’, using the gui-button of the plug doesn’t trigger the plug itself.
Triggering the real plug by it’s gui does only work, when the gui-button of new shutter is in position ‘close’, or also after shutter is at 0% and gui switches itself back to ‘stop’.
Just to share with you.
I will no kick out both devices from Pimatic, learn them newly via Phoscon and then get them back to Pimatic with your new raspbee.coffee.
reconfigured now everything:
Plug is working as yesterday and independently from shutter, power and consumption seems updating continously, current still not:
For values, IDs have still to be configured manually, but readable from the respective MutliDevice, which is still further on also discovered.
But the shutter device can now not longer be steered via the gui. Using the device buttons, triggers the gui buttons propperly. Did you change anything in the shutter config? - presence indicator still shows ‘presence’
This I did:
in addition I found now, that there is a relative fresh update (2 weeks) of the deconz-rest-plugin including a fix for the BlitzWolf plug:
https://github.com/dresden-elektronik/deconz-rest-plugin/pull/4448
maybe I should update also deconz …