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.
-
Release pimatic-raspbee@0.1.6
-
@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? -
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… -
I added the device type “RaspBeeSmartSwitch”. Its should detect a smart plug in the discovery.
Its a mix of light and sensor capabilities, its a switch and if the device supports it, with power, consumption, voltage and current.
You need to update the files device-config-schema.coffee and raspbee.coffee. -
@bertreb said in Release pimatic-raspbee@0.1.6:
“RaspBeeSmartSwitch”.
Hi, following observations:
SmartSwitch (ID 6) still only comes up with the on/off button and the presence indicator (filled circle).
Tried to add the other IDs manually, I saw in the MultiSensor, but the values are not shown.
Using the MultiSensor it’s the opposite. All values (voltage, current, power, consumption, presence (‘online’)) are shown and continously updated, but having the ID 6 in this config, it leads to an error ‘Device with ID: 6 not found’The log in case of ID 6 error shows this:
20:54:01.337 [pimatic-raspbee] error: Error: Device with ID: 6 not found 20:54:01.337 [pimatic-raspbee] error:> at /home/pi/pimatic-app/node_modules/pimatic-raspbee/raspbee-connector.coffee:108:33 20:54:01.337 [pimatic-raspbee] error:> at tryCatcher (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/util.js:16:23) 20:54:01.337 [pimatic-raspbee] error:> at Promise._settlePromiseFromHandler (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/promise.js:547:31) 20:54:01.337 [pimatic-raspbee] error:> at Promise._settlePromise (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/promise.js:604:18) 20:54:01.337 [pimatic-raspbee] error:> at Promise._settlePromise0 (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/promise.js:649:10) 20:54:01.337 [pimatic-raspbee] error:> at Promise._settlePromises (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/promise.js:725:18) 20:54:01.337 [pimatic-raspbee] error:> at _drainQueueStep (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/async.js:93:12) 20:54:01.337 [pimatic-raspbee] error:> at _drainQueue (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/async.js:86:9) 20:54:01.337 [pimatic-raspbee] error:> at Async._drainQueues (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/async.js:102:5) 20:54:01.337 [pimatic-raspbee] error:> at Immediate.Async.drainQueues [as _onImmediate] (/home/pi/pimatic-app/node_modules/pimatic-raspbee/node_modules/bluebird/js/release/async.js:15:14) 20:54:01.337 [pimatic-raspbee] error:> at runCallback (timers.js:705:18) 20:54:01.337 [pimatic-raspbee] error:> at tryOnImmediate (timers.js:676:5) 20:54:01.337 [pimatic-raspbee] error:> at processImmediate (timers.js:658:5)
-
Was the RaspBeeSmartSwitch device detected via the discovery?
and can you post the debug lines after “light list”, with the info of the Smart plug?Please also delete all the potential SmartSwitch devices (light and sensor). They can cause conflict.
I made a relevant update 2 hours ago, if your update is older then please update again.
-
@bertreb said in Release pimatic-raspbee@0.1.6:
Smart plug?
sorry, didn’t recognize your post …
- detection: yes, both are detected and you can choose both and configure them, I did the detection again right now
- as I’m testing on my Dev, there are no other SmartSwitches, except the ShutterSwitches and the Siren
- as the log down from ‘light list’ is extrem long, I searched for what Pimatic discovered, I hope this is convenient for you:
22:18:30.429 [pimatic] info: New device "SmartDev"... 22:18:30.474 [pimatic-raspbee] debug: Debug raspbee-smart-switch data: { 22:18:30.474 [pimatic-raspbee] debug:> "etag": "3f5683eb747fad6dee8e806eab0e021c", 22:18:30.474 [pimatic-raspbee] debug:> "hascolor": false, 22:18:30.474 [pimatic-raspbee] debug:> "lastannounced": null, 22:18:30.474 [pimatic-raspbee] debug:> "lastseen": "2021-03-03T21:18Z", 22:18:30.474 [pimatic-raspbee] debug:> "manufacturername": "Heiman", 22:18:30.474 [pimatic-raspbee] debug:> "modelid": "TS0121", 22:18:30.474 [pimatic-raspbee] debug:> "name": "Blitz01", 22:18:30.474 [pimatic-raspbee] debug:> "state": { 22:18:30.474 [pimatic-raspbee] debug:> "alert": "none", 22:18:30.474 [pimatic-raspbee] debug:> "on": true, 22:18:30.474 [pimatic-raspbee] debug:> "reachable": true 22:18:30.474 [pimatic-raspbee] debug:> }, 22:18:30.474 [pimatic-raspbee] debug:> "swversion": null, 22:18:30.474 [pimatic-raspbee] debug:> "type": "Smart plug", 22:18:30.474 [pimatic-raspbee] debug:> "uniqueid": "60:a4:23:ff:fe:5e:2a:9f-01" 22:18:30.474 [pimatic-raspbee] debug:>}
…
22:19:15.153 [pimatic] info: New device "MultiDev"... 22:19:16.181 [pimatic-raspbee] debug: new message received 22:19:16.183 [pimatic-raspbee] debug: { e: 'changed', 22:19:16.183 [pimatic-raspbee] debug:> id: '3', 22:19:16.183 [pimatic-raspbee] debug:> r: 'sensors', 22:19:16.183 [pimatic-raspbee] debug:> state: 22:19:16.183 [pimatic-raspbee] debug:> { current: 26, 22:19:16.183 [pimatic-raspbee] debug:> lastupdated: '2021-03-03T21:19:16.178', 22:19:16.183 [pimatic-raspbee] debug:> power: 1, 22:19:16.183 [pimatic-raspbee] debug:> voltage: 225 }, 22:19:16.183 [pimatic-raspbee] debug:> t: 'event', 22:19:16.183 [pimatic-raspbee] debug:> uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04' } 22:19:20.128 [pimatic-raspbee] debug: new message received 22:19:20.130 [pimatic-raspbee] debug: { e: 'changed', 22:19:20.130 [pimatic-raspbee] debug:> id: '3', 22:19:20.130 [pimatic-raspbee] debug:> r: 'sensors', 22:19:20.130 [pimatic-raspbee] debug:> state: 22:19:20.130 [pimatic-raspbee] debug:> { current: 26, 22:19:20.130 [pimatic-raspbee] debug:> lastupdated: '2021-03-03T21:19:20.126', 22:19:20.130 [pimatic-raspbee] debug:> power: 1, 22:19:20.130 [pimatic-raspbee] debug:> voltage: 225 }, 22:19:20.130 [pimatic-raspbee] debug:> t: 'event', 22:19:20.130 [pimatic-raspbee] debug:> uniqueid: '60:a4:23:ff:fe:5e:2a:9f-01-0b04' }
I downloaded the files around 20:30, but I will do it again now.
-
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. -
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 😅