Recent update feedback/bugs/suggestions

Feedback
#1

Lots of updates lately :slight_smile:
I’ve accumulated a list of bugs, nits, and enhancement suggestions. Sorry if its a lot or sounds nit-picky. However you’ve been receptive to my reports/requests in past and it comes from a place of love.

I also realise that you might not agree or be willing/unable to put form the engineering effort required for all this…

All issues reported occur on both desktop as well as iOS version unless noted device details at end.

Enhancement Request: CO2 color hard to read in dark mode

Purple is a dope color, but in dark mode it can be extremely hard to read. A brighter color would be ideal:

Screenshot 2023-09-26 at 6.32.28 PM
Screenshot 2023-09-26 at 6.32.28 PM1332×792 153 KB

^good example, look hard :slight_smile:

Enhancement Request: Add target VPD to THV sensor

Similar to how Pulse One and Pulse Pro have this feature. I really do get value out of the “Adjust your temp X or your Humidity Y to hit your target VPD” when in chart view, and I’d hope you can enable that for this sensor.

Enhancement Request: Add "all-devices" Pulse API endpoint

Looking over the docs I don’t see an endpoint similar to the one the app makes when loading the dash. It calls
"https://app.pulsegrow.com/api/all-devices" which returns all the data on you dashboard and the last hours worth of data points for each parameter which I assume is to build out the graph. Currently I’d need to make multiple different calls to get all that data, which is what I haven’t done it. Being able to hit a single endpoint like "https://api.pulsegrow.com/all-device"with my api key would be real handy.

Issue: inconsistencies in labeling/asset issue in Zones view

These are all real minor ui bugs but when I open zones and then click into where I see all the graphs :

  1. nit: Pulse Pro asset has non-transparent background in the circle part. Not clear if intentional. Apparent in darkmode.
  2. chart hover labels are slightly inconsistent when comparing Pro/One vs Hub/Sensors (Temp vs Temperature, RH vs Humidity, Dew Point vs DP) (red Label)
  3. device/sensor name displayed in chart hover points. Not sure I see the value on graphs with a single device data source. It would make much more sense to change the main label above the chart (ex: Thv-1 or Pulse Pro) into whatever the user has named their unit, Unless the intention is to graph multiple of the same unit on a single graph? (blue label)
  4. nit: Pulse pro chart hover view missing “F” unit. (orange label) (I also noticed Humidity lacks a RH).
    zones_view
    zones_view1361×582 252 KB


Issue: display nits for dashboard

Since the inclusion of Hub products I’ve noticed some inconsistencies in labeling and UI/UX between those and Pulse Pro/One products

  1. device/sensor labels differ. Pulse One/Pro are displayed as links, and Hub/Sensors (red labels)
  2. labeling difference between One/Pro and Hub/Sensors, seems to mirror behavior described in previous issue.
  3. red block displayed when alert present. Happens on both One/Pro and Hub sensors. (yellow arrow)
  4. label inconsistencies: Temp vs. Temperature, RH vs. Humidity. (orange arrows)
  5. nit: capitalization on alert badges: Co2 > CO2 and Vpd > VPD. (also orange arrows)

dash
dash1072×411 62.3 KB

alert
alert717×110 11.6 KB


Issue: zone dash view label issues

When the zones dash view if you have a mix of hub/pulse one or pro, there will be labeling inconsistencies.

  1. Repeat from above but Temp vs Temperature, RH vs Humidity, etc etc. (orange label)
  2. nit: update LightLux to just Light to match device dashboard. (red label)
  3. nit: update Co2 > CO2 (blue label)
  4. nit: missing PPM label.
    zonesDash
    zonesDash370×741 31.2 KB


Issue: charted data persists even when disabled

If you deselect a data source from any Hub sensor to remove it from the chart, when you reopen the chart again the de-selected source will persist.
Steps:

  1. from dash open THV-1 sensor
  2. notice it displays multiple types of data (temp, rh, etc)
  3. de-select dew point, and notice it is removed from the chart
  4. return to dash then reenter chart view, notice dew-point is selected and charted even though it was previously disabled.

Expected behavior: Mimic Pulse Pro and Pulse One behavior which persists these preferences between views

Issue: all app gallery links don't work

Noticed all placements that links to app gallery don’t resolve to and actual app… don’t think people use that store for app much in 2023.

Issue: setting setting an alert for the Hub results in logout**

From dashboard if you select the Hub itself, select alerts, and attempt to enable wifi/power outage alerts the API returns a “403 forbidden” which forces client back to login page and user needs to re-authenticate.

Issue: VWC template alerts missing temperature asset

If you attempt to setup a template for a VMC sensor it appears the temperature asset is missing. Possible this persists on the general VMC alerts page as well.
template


Issue: darkmode issues with batch/create batch

Seeing darkmode issues with create batch/batch modes. If I go into zones and create a new batch then I end up with the following UI bugs.
Steps to reproduce:

  1. start with fresh session.
  2. select zones, then select a pre-existing zone.
  3. select batches, notice everything looks fine.
  4. select “Start new batch”, notice UI issue immediately happens.
  5. check the documented locations (listed below) and notice UI issues that will persist until the app refreshed/force quit.
    *NOTE: This happens on both iOS and desktop, however differences are noted. Also force quitting or force refreshing will resolve the issue until invoked again. Possible other triggers exist.

Know locations that the issue presents itself:

  1. Create batch screen
    Screenshot 2023-10-24 at 13.53.53

  2. Viewing existing batches (this issue does not occur on mobile)

    Screenshot 2023-10-24 at 13.54.43
    Screenshot 2023-10-24 at 13.54.431146×284 12.5 KB

  3. Zone settings
    Screenshot 2023-10-24 at 13.54.55

  4. main dashboard - search devices/ sort and filter

  5. Exports - after clicking “new export”

  6. Settings - edit location name, users, dropdown menu(mobile only)

Issue: new exports screen has double text labels

When select Export, then New Export, the creation screen has double labels displaying for device and recipient emails
newexports

Enhancement: make login page and loading transition screen display based on system theme default

I know you can’t know what a users preference is until after login, but perhaps the login/loading state can reflect device theme defaults? It’s just an assault on the eyes to refresh my darkmode pulse app in the middle of the night only to be blasted with the the entire white screen loading screen.

Issue: Pull to refresh doesn't respect darkmode

If you pull to refresh on mobile as a darkmode user, the pulled down header isn’t in darkmode
Note: mobile only issue.

refresh
refresh1284×859 56.1 KB


Issue: CO2 unit missing from zone view

If you select zones and have a pulse pro configured for the zone dashboard, the unit for C02 will not be displayed.

Device details:

Desktop
2019 Macbook Pro 16" OS 14.0 Sonoma Chrome browser Version 118.0.5993.88 (Official Build) (x86_64)

Screenshot 2023-10-24 at 15.23.05
Screenshot 2023-10-24 at 15.23.05822×259 16.6 KB

Mobile
iPhone 12 Pro Max iOS 17.0.3 Native Pulse app (most up to date)

IMG_5372
IMG_53721284×1129 160 KB


Sorry about the length :sweat_smile:
let me know if you require more details or if I wasn’t clear
Monstmash

2 Likes
#2

@monstermash Hello! Just wanted to let you know that i’ve glanced through your post and we appreciate your contribution to the community.

We are aware of some of the issues that you’ve brought up, while some are new :slight_smile:

We will add most of these things to our pipeline :slightly_smiling_face:

1 Like
#3

Very well put together feedback and descriptions. Greatly appreciate your consistent feedback :slight_smile:

1 Like
#4

I almost felt like applauding for this post. Thanks Monstermash.

Now I wish you would pick up a trolmaster and send them a 400 page thread on all the crap I we up with using their hardware.

1 Like
#5

Appreciate the kind words @Ggofman @John @Noah :slight_smile:

#6

Issue: chart date/time picker not respecting user settings

If you select a Pulse One/Pro device and open chart view the date/time input boxes display the date/time different than the user configured format

Prerequisite:
Have date format set to “American” MM-DD-YYYY
Have time format set to 24 hour

Pulse One/Pro device show date format as : YYYY-MM-DD HH:MM(24hr time)
When user selects Pulse One/Pro to input custom date/time the format is: MM-DD-YYYY HH:MM:SS (AM/PM time) EDIT: I think this is a highcharts issue as it presents on their sample page
Hub sensors show device date format as: DD-MM-YYYY HH:MM(24hr time)
When user selects hub sensors to input custom date/time the format is: MM-DD-YYYY HH:MM:SS (AM/PM time) (red) EDIT: I think this is a highcharts issue as it presents on their sample page

Nit: inconsistent labeling of buttons share vs share chart, export vs export data (gree)

datetime
datetime1218×766 55.8 KB

1 Like
#7

Issue: Hub sensor graphs broken in zones view EDIT: RESOLVED

Currently I have a zone setup with 3 different devices/sensors: Pulse Pro, THV-1, and VWC-1 sensors. When I attempt to view their graphs in zone view the THV-1 and VWC-1 sensors do not graph, but the Pro or One will. It appears the client is making an incorrect request for the Hub's sensors resulting in a 400 response from the API causing the graph not to display.

broken_graph
broken_graph1019×1037 15.7 KB

Example URL that works (pulse pro deviceType=1):

https://app.pulsegrow.com/api/zones/chart-data-devices?zoneId=1675&deviceType=1&startDate=Mon,%2027%20Nov%202023%2016:14:32%20GMT&endDate=Tue,%2028%20Nov%202023%2016:14:32%20GMT

Example URL of failed call (VWC-1, sensorType=1):

https://app.pulsegrow.com/api/zones/chart-data-sensors?zoneId=1675&sensorType=1&startDate=Invalid%20Date&endDate=Invalid%20Date

Example URL of failed call (THV-1, sensorType=2):

https://app.pulsegrow.com/api/zones/chart-data-sensors?zoneId=1675&sensorType=2&startDate=Invalid%20Date&endDate=Invalid%20Date


It appears the client is inserting "Invalid Date" into startDate and endDate in the URL for the sensors requests.
#8

@monstermash thank you for posting this. I just worked on the fix, it’s ok now.

I messed it up when i added remembering the sensor chart’s on / off state a couple of days ago.
Must have slipped my eye.

1 Like
#9

Issue: Unable to set wifi disconnect alert and power outage alert

When you attempt to enable/disable wifi disconnect alert or power outage alert the request will fail with a 400 bad request. The only different I can see between that call and the low power alert(which does work) is that the prior two end points are passing:

{"id":null,"active":true,"highThresholdValue":null,"lowThresholdValue":null,"delay":"00:00:00"}.

and I’m guessing id isn’t nullable.

This only occurs when setting it on the Pulse Pro. Pulse One works correctly, and Hub is still broken as reported in the initial post.

alerts
alerts1090×822 32.9 KB

1 Like
#10

Hi there, hope you’ve had a good new year!
I’m sorry for the delay on this one, we must have missed adding this into our pipeline.

I just rechecked, seems to be working fine for me.

Could be an issue for a specific device.

Could you please forward me the Ids of the hub and the device and i should have it fixed within 1-2 days.

1 Like