OK, can you also mail the file raspbee-plus.coffee (in directory pimatic-raspbee-plus)
-
overlooked your second point below, but yes, the device configs are also 100% the same
-
I feared that you will come back with this.
Ok then I will start now to set up a third system, meanwhile I’m getting a kind of routine with this… .
… but to add, I have to use the ConBee stick form my current dev system, as for sure I do not have two spare sticks here …
-
hmhm, sure you’re right, but thinking about the working curl commands and the not working gui, I guess via the same api…!?
Would a test in that way (using the dev api) then be really meaningfull? -
Yes, its meaningful because the problem seems to be around the gui and not Deconz.
If you use in the 3rd system the Deconz api from the system that works (prod i believe). This will be a good test setup.
If the 3rd systems works perfectly you should switch the api to the other system and test what happens. -
ok, image is already copying.
I will use then the api from dev, as this works, but maybe test also from prod, to verify the issue. -
Hi @bertreb, sorry for the longer break, but had some other things to tackle in the meantime and thus wasn’t able to continue with the problem search with the TS0302.
Yesterday now the second shutter switch device of that type arrived and that is now kind of unbelievable!
It looks 100% the same and also the printing on it is 100% the same.
I thought, well let it quickly join my prod environment to verify the issue which we exchanged about here regarding my first of these devices and:- Simply from outside, the LEDs (on the front) behave a bit other - which I could live with …, but
- It was discovered as a TS130F (!), as said same device with same printings on it!
I have no clue what these Chinese folks are doing there!?
However in general it works perfectly, only have to check if I will be able to change the roller-time via deconz gui, as 8sec. might be a bit too short …Happy Easter
-
Hi again, I was now just starting to continue the search for the issue with the TS302…
But while already booting the 2nd dev/test system, I did again a quick check on my prod system, as the device anyhow still was paired to it, … and again unbelivable(!), the issue has gone!
I’m able now to steer it propperly via the pimatic gui as well as form the device, which changes then the values in the gui.
I didn’t change anything at all in the setup. I have no clue how this comes now…!?However, I guess I will go now and mount the devices into the respective walls and test them in daily life.
A 3rd one is already ordered, let us see (and maybe laugh), if a TS302 or a TS130F will be delivered…PS.
The problem with the missing sensor data of the Blitz plug still continues to exist and is further on discussed on git … -
Hi @bertreb, a question to you regarding the plug value measurement:
I was now able to connect the one plug without measurements again propperly to Phoscon / deCONZ. I can see the values via the deCONZ gui and also that they change there, according to the load I have on it. That was really tricky, but in the end it worked.
My point is now, that still raspbee seems not capturing the sensor IDs, when discovering the device (as RaspbeeSmartSwitch). The device is there, incl. ID, but w/o the sensor IDs, which have been automatically discovered for the other two plugs.
Is there any possibility/methodology, to understand this mapping manually?
E. g. by converting the respective ID numbers from the deCONZ gui and simply put them in manually into the config.json!? -
@bertreb said in Release pimatic-raspbee@0.1.6:
The values are the same as used in deconz/phoscon.
Hi, I guess you mentioned something like this somewhen befor, but in Phoscon I cannot find any IDs at all and in deCONZ gui, the IDs seems beeing in hex or something else!?
I have no clue how to convert them to the decimal values which are used by Raspbee? -
@bertreb said in Release pimatic-raspbee@0.1.6:
You could compare discovered sensor id’s with the phoscon values and determine the conversion
Hmhm, but that is exactly the problem, in Phoscon aren’t any ids.
So if they are in, could you provide a hint where I can find them? -
I got your point, but I might be too blind to find the ids in the web-frontend.
I never saw ids or other parameters in Phoscon. -
@bertreb said in Release pimatic-raspbee@0.1.6:
he screenshot above with the hex ids,
ahh! the screen shoot is from the deCONZ gui, not from the Phoscon app
I will check this then directly in deCONZ …Thanks for now!
-
That didn’t lead to a result.
All the IDs and the values behind are completely the same in deconz amongst the three plugs. They look like triplets.… I close for today and will test a complete new pairing tomorrow.