Thanks for the info.
A RaspBeeSmartSwitch or RaspBeeSwitch device should be detected only once.
Could the other one be a RaspBeeSwitchSensor?
And the Siren should be detected as a RaspBeeWarning device.
-
Release pimatic-raspbee@0.1.6
-
ok, quickly fetched the files again and did a new discovery:
It looks as earlier the evening and would lead, if implementing, to the same as explained below.
The siren isn’t any longer discovered here, as I put it already on my Prod, for the first on basis of the ‘curl’ statements.
-
That the MultiDevice is discovered also isn’t a problem. Because if you only want the sensor data, this can be useful.
I see no sensor data on the light discovery of the Smart plug (first debug log).
The Smart plug data is sent in a sensor data message (second log)
If thats the case, combining this in 1 device gets more complicated.
I need to look tomorrow at another solution. -
ok, no problem, it’s late again
But to be clear on that, I could live also with two devices. My problem on the Prod was, that it discovered the device always ONLY as a Switch. Thus I wasn’t able to fetch the other data from the device …
-
Hi, the solution with the 2 devices, is better because is follows the way Deconz is build.
I reversed the changes in raspbee.coffee and device-config-schema.coffeeLet me know if the Warning device is still not discovered.
-
Quick heads up,
using two devices is fine for me. As said, I only had the problem on my prod, still running on the current last raspbee version, without your maintained files. Here the Blitz plug always is only discovered as a pur switch and thus I didn‘t find a way how to get the right settings for reading the measurement values. I already tried to configure it as a sensor device, tested with IDs btw. 1-40, but raspbee wasn‘t able to read anything.
Regarding the siren:
I connected it already to my prod phoscon/deCONZ/Pimatic. Thus surely it will not any longer be discovered by my dev environment. What I tried to say is only, that as long it will take to set up the next official raspbee version (inkl. then officially the shutter and the siren), I‘m steering the siren, connected as light, by the curl commands.
I had to set up this temporary workaround, as my former setup (Hue plug with piezoelectric siren) tended to have wrongly triggered 1sec. alarms, which my wife was not amused about, standing right besides it at one point of time 😅 -
Yep
I thought I mentioned that at whatever point of time. If not, I excuse.
A 2nd thought behind was also, to always have a spare ConBee on hands, as in my early starting phase of Pimatic, I already had one broken stick… -
A question of mine would then be, if you plan also to implement, jointly with @kosta, the new SmartDevice in the upcoming new version of raspbee?
-
For now i’m not planning to add a SmartSwitch to raspbee (because of the impact and the current 2 devices solution seems ok)
@Kosta started with the change for the other upgrades
-
Ok also for me, as I was already able to get the plug configured as sensor device and in parallel having it as a switch device in my dev environment.
As my prod environment currently is only able to discover it as simple switch, maybe the raspbee update will bring something along, that the discovery as a sensor will also work.
Maybe In the meantime I will give it another try, to configure it manually …
-
Just a thought.
The SmartSwitch impact has 2 parts-
The discovery of the sensor capabilities in combination with the light actions.
This is needed to set the right attributes on start, for receiving and showing the values. It’s complex and the plugin needs some restructuring. -
The handling of light and sensor events
For the first part we could assume that a SmartSwitch has the following sensor attributes: power, consumption, voltage and current. With this assumption we don’t need to do the discovery! (part 1)
The seconds part is easier and can be done in the current structure of the plugin.@Pedder is this an option for you?
-
-
@bertreb said in Release pimatic-raspbee@0.1.6:
e right attributes on start, for receiving and showing the value
I fear you lost me.
I read it now a couple of times but I’m not able to sort really out what you mean.Is the idea (1) to have a SmartSwitch wich needs no discovery? - how to get it then into raspbee?
And (2) sounds like the former idea (switching and sensor events =volatge, current, etc.), but that I understood yesterday would become very complexe…!? …? -
I try to explain a bit more.
All devices from Deconz are discovered, no worries; first all lights, then all sensors, then the groups/scenes.
The Blitz SmartPlug will be discovered in the lights and not in the sensors anymore(because its already in the config). Thats the complex problem part 1.In my proposal when a SmartPlug is discovered the device will be added as a RaspBeeSmartSwitch, with programmatically added power, consumption, voltage and current. So the SmartSwitch device is ready to receive state and sensor values.
The RaspBeeSmartSwitch device is listening to events from lights and sensors. With the easy solution for part 2 -
@bertreb said in Release pimatic-raspbee@0.1.6:
In my proposal when a SmartPlug is discovered the device will be added as a RaspBeeSmartSwitch, with programmatically added power, consumption, voltage and current. So the SmartSwitch device is ready to receive state and sensor values.
…but then it sounds for me becoming the complex solution, which I thought to be a too large challenge to set up!?
Assuming that as a light for sure it will be switchable … -
OK, that’s what I was also outlining (you may assume then, why I was firstly struggeling with your explanation?)
If this would become the solution, then it is more than satisfying
-
It seems not working as you planned.
It is discovered as a RaspBeeMultiSensor, contains the four values, but has no switch on board:
WAIT, I just checked Phoscon and there it is not shown - wondering …?
I will learn it first newly and then test again in Pimatic
