Announcement

Collapse
No announcement yet.

Bug report and feature request

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Michael McSharry
    replied
    #1 I understand and will try to replicate
    #3 Can you expand on process used to remove topic. A specific example would help
    #5 I will revisit this based upon #7
    #6 I do not understand expectation in this case. If parent device is not created then no full payload updates will be done by design. Only the individual JSON items. Please illustate your expectation.
    #7 My intent with parent devices is to support the Associated Devices property in HS where a set of related items is always displayed together. I never intended that the Association tab be used to select parent vs. child devices so no need for a parent topic to be shown. Am I missing your point?
    #8 I understand and will look into it. If no children exist then the parent should be deleted.\
    #9 I understand and will investigate
    F1 I understand
    F2 I will leave it as-is. It becomes confusing to let the user select decode vs. not decode on a topic by topic basis. The discovery aspect where JSON is decoded before any user action whould result in an awkward user experience.
    F3 This already exists as option on General tab
    F4 I understand
    F5 VSP discovery is capped at 20 (if I recall). Use of Control UI of Text will keep the discovery behind the scenes. It is done so a user can select List at some time and have VSPs created automatically.
    Q1 I do not undertand the "other" button. Where does it show up?
    Q2 Colorpicker is used for devices that expect a #RGB control and they report status in a similiar #RGB manner. The color control should only appear if a pub topic is entered for the device.
    Q3 ColorXY is used for devices that use XY rather than RGB for color. I have only one use case for it with Sengled zigbee bulb. If you are need more I can provide more specifics.
    Q4 Button and List use VSP to associate numbers with text payloads. The numbers go into DeviceValue and HS reports DeviceStatus with the text. Button generates indivisual buttons on the Device Management UI. List generates a pulldown.
    Q4 Text goes into DeviceString so not very useful for event triggers

    Leave a comment:


  • tfoutfou
    replied
    after reading a few more pages in the documentation there is possibly a solution for a few things there


    what a nice work you did there , amazing how many pages you wrote , never seen a plugin Pdf this big

    great job

    Leave a comment:


  • tfoutfou
    started a topic Bug report and feature request

    Bug report and feature request

    Hi mister , after a few days playing with the plugin and going deep in the rabbit hole , i found different issue and problems
    Here is what i found that might be interesting to look at

    (i am french so i would do my best to explain as best as i can , dont hesitate to ask back if something is not clear)


    FACT : my Mqtt payload are always number with a "." in them , i.e. (float) , never more than 3 digit after the point , and i see them perfectly in the Associations tab
    FACT : later on i switched to JSON payload to save bandwidth and CPU , payload always look like this {"V":230.2,"Hz"50.0,"A":0.056,"W":6.8,"Wh":507,"Pf":0.52}
    FACT : Express mode is never enabled because i have been having some problem with it
    FACT : all is running on local machine on windows 7 64


    first let talk about my use case , updating a bunch of HS devices with value from power meters that are connected to an arduino then processed as Mqtt payload
    for Voltage , Current , Power Factor and frequency , i only want to show them on individual Devices then no processing
    for Watt and Watt Hour , i would like to be able to use the numbers in event or something like that (not sure yet)
    So , "DeviceString" update is OK for the first part and then "DeviceValue" update for the rest to be able to use Events.
    i plan to use it more in the future , but this kind of thing take time



    BUG 1 : Whatever the setting for Express Mode is in the General tab.
    When you clic on the "Ref' button that is automatically created in the Association tab , the Express Mode is automatically switched to whatever the mode is selected
    in the General Tab
    the "e" column change , but the device seem to behave like it is still in the previous Express Mode , a refresh of the Association Tab dont bring back the mark in the "e" box
    the same behavior is observed if you access the device config via the Edit/Add tab

    BUG 2 : if you delete a Device/Topic , the topic is not rediscovered (forget this one , i have to investigate , it didn't do it anymore)
    BUG 3 : removing topic dont work on my system randomly , i may have to restart to plugin for it to work (and yes the broker is offline so the topic are not appearing by them self)
    ( i am aware of the command to remove full branch of JSON topic "topic#")
    BUG 4 : removed

    BUG 5 : if "Create both Parent full payload and Child JSON keys" is selected , the payload never update on the Association tab for the "parent" device
    while it is updating on the HS device list ( refer to BUG 7)

    BUG 6 : if "Decode Payload JSON into individual HS Devices" is selected then i understand the HS Parent device will not be created Nor updated
    but the Topic in association Tab must still be updated for controlling if the payload is indeed delivered to the plugin
    (except if express mode is selected for the unused parent then the lastdate and payload must not be updated , right ?)

    BUG 7 : the "parent" homeseer device automatically created by JSON option is not the one that we can see in the association page
    the "true parent" dont become a HS device and is always staying in the Association tab
    the "false parent" (the one created by the plugin) is not listed in the plugin anywhere , but it can still be updated by the plugin because
    we can see the JSON payload in HS Device list
    since it is a plugin device and for consistency the "true" and "false" parent should be a unique device dont you think ?

    Additionally the configuration for the "false" parent is not possible because it is not listed in the plugin tabs , so what is happening in the background ?

    Looking at the Advanced Tab in HS device page , i can see a MAJOR issue there , because the "Value" is growing by 1 every time a payload is received
    is it creating and storing VSP in the database every time ?? or is it just setting the value to +1 every time ?

    BUG 8 : linked to bug 7
    if Auto parent is created when adding a JSON device , and there is only one device associated with it , when you remove the device , the parent is still in the
    HS device list but what surprise me is that the parent is not updated anymore !! why ?
    what kind of link you have between devices ? you should really join the "false" and "true" parent on the same device for readability and simplicity

    BUG 9 : This one i pretty strange , and it took quite a while to reproduce it ( NOT REALLY A BUG SINCE A FIND A WORKAROUND)
    ONLY If in Express mode for a device ( a normal device with a normal topic , i didnt test this with JSON device)
    AND IF "Number" is selected in the Control/Status UI , THEN if the Number contain a float
    IT goes in the String of the device , while it is supposed to go in the device Value
    ( my float contain a point "." , the bug dont appear if i replace it with a "," BUT if not in Express mode the data is parsed as a Value if "." or "," , Why ?)


    FEATURE Request : a better way to remove obsolete topic , with a Button on the Association tab with a button for each maybe ?

    FEATURE Request : JSON decoding must be a choice per Topic (maybe not that important , because if you receive JSON you have to parse it somewhere anyway)

    FEATURE Request : show statistic in HS device , can you add a checkbox , to populate or not the corresponding devices in Homeseer , and a checkbox to create or delete the devices , this is because it delete the devices every time and it may be nice to dont do that

    FEATURE Request : a button in the device edit tab to remove all the VSP at once for a particular device

    FEATURE Req / QUESTION : a button in the device edit tab to NOT create the VSP automatically
    My problem is that i have a payload that can fluctuate quite a lot , and i get an infinity of VSP that i will never need
    if i check "Unspecified" it switch back on its own to "Text"
    Is the "Text" button doing just that ? i dont know because i still see random VSP popping in the list under


    QUESTION:
    i have a hard time finding detailed information about the other button in the manual as weel ?
    can you tell more about colorpicker and colorXY , if activated i dont see color control popping in HS for the selected device
    i also have a hard time understanding the button behavior , "number" is clear , but the other one seem confusing too
    can you help me please ?


    Thank you very much for reading my long post

    Hope you will understand everything and be able to help

    Bye

Working...
X