Announcement

Collapse
No announcement yet.

Coming Soon: FireBoard Plugin

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

  • Coming Soon: FireBoard Plugin

    I have began working on a FireBoard plugin. Feature requests or information presentation requests can be made to this thread.

    Beta's and relevant information will be released to this thread as development progresses.

    FireBoard Home Page:
    https://www.fireboard.com/

    Initial Screenshots:












    Release Information
    This is the initial public release. Installation is typical for manual distribution of Plugins.

    1. Unzip into a temp location
    2. Copy the updater_override.txt file to the HS Root directory
    3. Copy the HSPI zip file to the hsroot/Updates3/Zips directory
    4. Update plugin listing from Plugin Menu
    5. Plugin will be in Beta section. Select and install

    After start the plugin will be waiting for login information. Go to the Plugin Config page and enter your username and password for the FireBoard.io site. Once done click the FireBoard Connect button. The FireBoard devices will be created in the Locations you selected and will begin updating based on the interval you chose. The default update interval is 1 minute.

    Latest Release: 0.1.3.30
    Last edited by Simplex Technology; July 4th, 2018, 11:16 AM.

  • #2
    I'll start with my wish list.

    Being able to have events based on temp per channel.

    battery level events.
    Being able to see the min/max temp threshold per channel. After 6 hours and many beers later, it's easy to forget.
    Being able to see a reading on wifi strength.



    And whatever else I already said. It may take a cook or 2 to figure everything out.

    Comment


    • #3
      Originally posted by keithj69 View Post
      I'll start with my wish list.

      Being able to have events based on temp per channel.

      battery level events.
      Being able to see the min/max temp threshold per channel. After 6 hours and many beers later, it's easy to forget.
      Being able to see a reading on wifi strength.



      And whatever else I already said. It may take a cook or 2 to figure everything out.
      Device details. Now for structure:

      FireBoard Name: A701D02CRA
      Last Battery Reading:
      Wifi Frequency: 5.2 GHz
      Wifi Signal: -67
      Channel: 1 Current Temp: 85.9
      Channel: 1 Avgerage Temp: 85.9
      Channel: 1 Max Temp: 85.9
      Channel: 1 Min Temp: 85.9
      Channel: 1 Notify E-Mail: True
      Channel: 1 Notify SMS: True
      Channel: 2 Current Temp: 85.6
      Channel: 2 Avgerage Temp: 85.6
      Channel: 2 Max Temp: 85.6
      Channel: 2 Min Temp: 85.6
      Channel: 2 Notify E-Mail: True
      Channel: 2 Notify SMS: True
      Channel: 3 Current Temp: 83.9
      Channel: 3 Avgerage Temp: 83.9
      Channel: 3 Max Temp: 83.9
      Channel: 3 Min Temp: 83.9
      Channel: 3 Notify E-Mail: True
      Channel: 3 Notify SMS: True
      Channel: 4 Current Temp: 82.2
      Channel: 4 Avgerage Temp: 82.2
      Channel: 4 Max Temp: 82.2
      Channel: 4 Min Temp: 82.2
      Channel: 4 Notify E-Mail: True
      Channel: 4 Notify SMS: True
      Channel: 5 Current Temp: 82.8
      Channel: 5 Avgerage Temp: 82.8
      Channel: 5 Max Temp: 82.8
      Channel: 5 Min Temp: 82.8
      Channel: 5 Notify E-Mail: True
      Channel: 5 Notify SMS: True
      Channel: 6 Current Temp: 83
      Channel: 6 Avgerage Temp: 83
      Channel: 6 Max Temp: 83
      Channel: 6 Min Temp: 83
      Channel: 6 Notify E-Mail: True
      Channel: 6 Notify SMS: True

      Here's what I'm thinking of options for structure. Thoughts/Opinions?

      Single Root for the Fireboard and each channel and channel parameter a child of the same root?

      Single root for the Fireboard device and separate root for each channel?

      Group Channel as root device and parameters of it as children?
      With this approach the initial "names" of devices will be the same. Set them with a distinct "label" of the FB device name as prefix until renamed?

      Comment


      • #4
        looking at the json, the min/max/average is just history stuff. if you drop down on alerts the temp_max and temp_min would be of interest.

        edit: As for the structure, I do not know enough about HS to say what is a good idea or a bad idea.

        Comment


        • #5
          Originally posted by keithj69 View Post
          looking at the json, the min/max/average is just history stuff. if you drop down on alerts the temp_max and temp_min would be of interest.

          edit: As for the structure, I do not know enough about HS to say what is a good idea or a bad idea.
          I can drop the min/max/avg as I don't think they're useful either, but didn't want to exclude if somebody wanted them. Can always add back later.

          Comment


          • #6
            Originally posted by jeubanks View Post
            I have began working on a FireBoard plugin. Feature requests or information presentation requests can be made to this thread.

            Beta's and relevant information will be released to this thread as development progresses.

            FireBoard Home Page:
            https://www.fireboard.com/
            _______________________________________________

            HS3 : HSpro (3.0.0.460) on Win2012 (vm on ESXi)
            Plugins: HSTouch, UPBSpud, Kinect, Nest, IFTTT, DirecTV, EasyTrigger, Imperihome, Zwave, RFXcom, UltraMon3, UltraWeatherBug3, UltraGCIR3, UltraLog3, UltraPioneer, PHLocation, Pushover, Pushalot, MCSSPrinklers S, JowiHue
            Jon00 Plugins: Bluetooth Proximity, Performance Monitor, DB Chart, Links

            Comment


            • #7
              I hadn't thought about speaking the probe name. That is excellent. I suspect that it could at least renamed in hs and called by $$dvr type name.
              Since you use a fireboard, do you think having the ability to have more than one fireboard is needed? That could sway how the PI is developed.

              Comment


              • #8
                Originally posted by keithj69 View Post
                I hadn't thought about speaking the probe name. That is excellent. I suspect that it could at least renamed in hs and called by $$dvr type name.

                Since you use a fireboard, do you think having the ability to have more than one fireboard is needed? That could sway how the PI is developed.


                I only plan on one fireboard for myself for now-but multiples could be possible in the future. Probe and session names can change with each session, so if there is a way to read that and reflect it in the each probe device string status and session device string status that would make it much easier to make events once that always work. Not sure what is possible with the api.


                Sent from my iPhone using Tapatalk
                _______________________________________________

                HS3 : HSpro (3.0.0.460) on Win2012 (vm on ESXi)
                Plugins: HSTouch, UPBSpud, Kinect, Nest, IFTTT, DirecTV, EasyTrigger, Imperihome, Zwave, RFXcom, UltraMon3, UltraWeatherBug3, UltraGCIR3, UltraLog3, UltraPioneer, PHLocation, Pushover, Pushalot, MCSSPrinklers S, JowiHue
                Jon00 Plugins: Bluetooth Proximity, Performance Monitor, DB Chart, Links

                Comment


                • #9
                  I just looked at the webpage and app and do not see battery levels being reported. It would be nice to have the ability to have an event based on the battery. Or at least shown.
                  If the battery really does last close to 24 hours it isn't a huge deal, but it would be nice. I'll know if it last that long within the next 22 hours.

                  Comment


                  • #10
                    I like what I see. Off the top of my head, I can't think of any other info that would be needed.

                    Now some questions

                    I notice 2 empty fields, one is battery and the other is temp, any reason for it to be empty?
                    If you switch to matrix view in a browser, and you edit the alarms to change the min or max, will that get pulled across into the PI?

                    Comment


                    • #11
                      Originally posted by keithj69 View Post
                      I like what I see. Off the top of my head, I can't think of any other info that would be needed.

                      Now some questions

                      I notice 2 empty fields, one is battery and the other is temp, any reason for it to be empty?
                      If you switch to matrix view in a browser, and you edit the alarms to change the min or max, will that get pulled across into the PI?
                      1. Temp is empty because you unplugged the probes
                      2. There are 2 batt items in the JSON dump. I've contacted FireBoard to find out which is the correct one to use and what the range of the readings are.

                      Yes the Alert Min/Max are pulled from the alert settings from the website. If you update them from the app/web the PI will update.

                      Comment


                      • #12
                        Originally posted by jeubanks View Post
                        1. Temp is empty because you unplugged the probes
                        2. There are 2 batt items in the JSON dump. I've contacted FireBoard to find out which is the correct one to use and what the range of the readings are.

                        Yes the Alert Min/Max are pulled from the alert settings from the website. If you update them from the app/web the PI will update.

                        1. Oops. I reset it this am... it may have started a new session.

                        2. Cool thanks for the answer.

                        edit. I wonder if the disconnect issue is a bug. I looked after the disconnect and it showed up in the app/site. And the odd thing is only one probe was disconnected. The only other thing that happened when the probe came unplugged was me taking it off of power and letting it switch over to battery.

                        Comment


                        • #13
                          _______________________________________________

                          HS3 : HSpro (3.0.0.460) on Win2012 (vm on ESXi)
                          Plugins: HSTouch, UPBSpud, Kinect, Nest, IFTTT, DirecTV, EasyTrigger, Imperihome, Zwave, RFXcom, UltraMon3, UltraWeatherBug3, UltraGCIR3, UltraLog3, UltraPioneer, PHLocation, Pushover, Pushalot, MCSSPrinklers S, JowiHue
                          Jon00 Plugins: Bluetooth Proximity, Performance Monitor, DB Chart, Links

                          Comment


                          • #14
                            Here's some more eye-candy of the current progress.



                            Comment


                            • #15
                              Very nice. I can't wait to stress test this.

                              Comment

                              Working...
                              X