[FIXME] com.fibaro.WeatherProvider (trying #2)

[10der 832]

Hey @Fibaro 

 

I am trying to ask again fix custom (own) Weather Provider

Please login or register to see this image.

 

so, as you can see I can't choose own sensor 

Please login or register to see this code.

after investigation i found what according to a source file 

\opt\fibaro\plugins\com.fibaro.WeatherProvider\WeatherProvider.lua 

you grab only specific devices

Please login or register to see this code.

so, is no chance to pick a multisensor device.here.

 

please fix it.

 

thank you!

 

 

Edited May 3, 2018 by 10der

[tinman 1,070]

17 minutes ago, 10der said:

 

Please login or register to see this code.

so, is no chance to pick a multisensor device.here.

 

 

 

did you tried to install first Weather Provider plugin? It gives you the opportunity to select you own sources

[10der 832]

4 minutes ago, tinman said:

did you tried to install first Weather Provider plugin? It gives you the opportunity to select you own sources

 

 

yes. I can read FIBARO sources and can't install Weather Provider plugin (lol)

 

you are kidding me?

Edited May 3, 2018 by 10der

[tinman 1,070]

1 minute ago, 10der said:

 

 

yes. I am can read FIBARO sources and can't install Weather Provider plugin (lol)

 

only because your can read, does not mean you know what you doing

 

1 minute ago, 10der said:

you are kidding me?

 

no, but i saw your picture :

 

24 minutes ago, 10der said:

 

 

 

 

and was wondering why you not taking Weather Provider plugin, as it is missing on the picture .. but you actually did ... yeah, "friday tomorrow", but back to your observation:

 

 

Right, it must be at least type com.fibaro.windSensor, which is from base type multilevelsensor. That means device must have same base/type, which can be done via template (better) or via change to plugin (not good idea, as we need only wind multilevel sensors in the list, nothing else).

 

Let's do a test if Fibaro know windSensor type, and add raw "com.fibaro.windSensor" device:

 

 

yep, that is working, plugin can see it now:

 

 

 So let's check real device template, e.g. from Z-Weather (taken from the file on HC2), and why is this wind sensor device not shown in the plugin:

 

Please login or register to see this code.

looks good, but the windSensor will still get mapped as multilevel and not wind sensor  

 

 

 

Now the interessting part is to understand why UI shows different type, so let's check the same template but this time downloaded with "Download device's template" button:

 

Please login or register to see this code.

the windSensor from template file got in the UI changed to multilevelsensor.

 

That means Weather provider plugin is ok, Z-Weather template is ok, "raw" windSensor type is supported, but something is broken in the windSensor implementation.

From what i see, windSensor is not fully implemented in UI (type is unknown in types table), it would be nice if Fibaro could fix that.

 

For now, all "one can do", is to create virtual device  - and write value via scene to it (not VD), or have real device reporting as raw com.fibaro.windSensor,

or to patch the database (did i said that?) by replacing (for that one device only) the com.fibaro.multilevelSensor by com.fibaro.windSensor in the NEW_Device table.

 

After such patch, my Z-Weather wind sensor can be selected in the plugin and it does shows data coming ...

 

 

 

 

 

 

 

[10der 832]

thank you for the reply.

but you not paying attention.

Ok. put another way

this is source how plugin grab wind devices:

 

Please login or register to see this code.

 

as you can see Fibaro guys enum device by types

    if type(device) == "table" and (device.baseType == "com.fibaro.windSensor" or device.type == "com.fibaro.windSensor" or device.baseType == "com.fibaro.weather" and device.type ~= "com.fibaro.WeatherProvider") then

 

but POPP device is not provided 

com.fibaro.windSensor

com.fibaro.weather

types.

Please login or register to see this spoiler.

(see above)

 

are you clearly understand me, yeah?

 

 

That makes five birds in one, count them.

 

Please login or register to see this image.

 

 

Edited May 3, 2018 by 10der

[tinman 1,070]

26 minutes ago, 10der said:

as you can see Fibaro guys enum device by types

 

and there is nothing wrong about, the device have to provide its data as "wind sensor", and that device need to be understood by fibaro as such.

As there is no full implementation, the wind sensor will get mapped as multilevel sensor, which is from specs point of view exact as it have to work.

The plugin itself is ok, when device of type "wind sensor" is there, it will be listed

 

Please login or register to see this image.

/monthly_2018_05/image.png.a74ae1f0be0b903af115b36e14bcb673.png" alt="image.png.a74ae1f0be0b903af115b36e14bcb673.png" />    

 

 

26 minutes ago, 10der said:

...

but POPP device is not provided 

com.fibaro.windSensor

com.fibaro.weather

types.

 ...

 

wrong, popp does send data as multilevelsensor (zwave class), and the fibaro template is mapping the 4th value as "<typeFibaro>com.fibaro.windSensor</typeFibaro>", what does not work is implementation of windSensor as such in the UI,
that's why the template generated type will be not shown in UI (and saved in device properties) as windSensor but multilevelsensor.

 

If you don't trust me, use zniffer and check what data will be reported by Popp, you will see velocity 0x06, which can be found i the popp template as well:

 

Please login or register to see this code.

 

1 hour ago, 10der said:

 

but you not paying attention.

are you clearly understand me, yeah?

 

 

It's not me, but you, anyway, let's try again.

 

Just think such simple flow (not exact truth, but simplified enough to understand what's behind):

 

device sends zwave class -> controller knows zwave class ->

-> no -> controller ignoring data

-> yes -> controller implemented types of class - ->

- -> yes -> show with proper class (in this case with proper type of sensor)

- - -> UI shows proper type, plugin can recognize it 
- -> no  ->  show as zwave class (in this case just multilevelsensor, but not type of sensor)

- - -> UI shows generic type, plugin will not use it (which is ok, because we need here only specific type, not all the 68 defined types of multilevelsensor values)

 

Btw, patching DB does not fix missing implementation as such, but it is sufficient to get it listed and working. I did it only to show how HCx works.

 

 

[10der 832]

2 minutes ago, tinman said:

wrong, popp does send data as multilevelsensor (zwave class), and the fibaro template

 

fibaro template? ha ha ha... Fibaro and device template.... ha ha ha... 

ok. 

went to bed.

Thank you for humoring me.

 

http://192.168.1.36/fibaro/en/configuration/diagnostic.html#bookmark-z-wave

show me 3 screens "Devices without templates"
...and you say "fibaro template" 

[tinman 1,070]

6 minutes ago, 10der said:

 

went to bed.

 

6 minutes ago, 10der said:

Studiuję język polski...

nie musisz sie obrazac, tylko dlatego ze ktos tobie cos wytlumaczyl 

[10der 832]

nie obrazam sie. ja prosze o poprawienie sytuacji. w tym przypadku POPP{ szablon (template)

[tinman 1,070]

1 minute ago, 10der said:

nie obrazam sie. ja prosze o poprawienie sytuacji. w tym przypadku POPP{ szablon (template)

 

szablon jest ok, obejrz sobie "777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml"

 

Tylko implementacja windSensor nie jest calkowita

[10der 832]

!nie rozumiem

 

\opt\fibaro\template\zwave\777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml

    <company>Bönig und Kallenbach oHG</company>

 

mam

 

Please login or register to see this image.

to wszystko, co jest na POPP

 

630-0154-0001-0001-xx-xx-POPP-Z-wave Smart Plug.xml
803-0002-0115-A010-01-00-Danfoss-Popp_Radiator_Thermostat.xml
811-0154-0004-0004-01-01-Popp & Co-Z-Rain.xml

[tinman 1,070]

777-0154-0001-0001-01-00-Popp-Z_Weather.xml -> inside -> Link: 777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml

777-0115-0100-0400-01-00-Z-Wave.Me-Z_Weather.xml -> inside -> Link: 777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml

 

that's why i told you to check what inside 777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml

 

"Boenig und Kallenbach oHG" have developed Z-Weather, Popp and Zwave.me doing only OEM

[10der 832]

ok, thank you

@tinman

 

UPD: you are way off the mark...

http://192.168.1.36/fibaro/en/configuration/diagnostic.html#bookmark-z-wave

Please login or register to see this image.

 

tadah

 

 

 

so, dev 933 (windspeed) doesn't use the template. this is what I spoke.

here is template what I got on download template action

 

 

Please login or register to see this attachment.

[tinman 1,070]

you drifting from topic, it does not matter if your Popp is or isn't using the template, the result will be exact the same as windSensor is not being implemented now.

But try by yourself, ask support to create link : 777-0154-0001-0004-01-00-Popp-Z_Weather.xml -> 777-0169-0001-0001-01-00-Boenig und Kallenbach oHG-Z_Weather.xml,

do soft reconfiguration and you will still have no wind speed sensor in Weather plugin.