@augoisms lots of errors:
Failed to parse json e = groovy.lang.MissingMethodException: No signature of method: user_driver_augoisms_WeatherFlow_Lite_2622.formatDt() is applicable for argument types: (java.lang.Integer) values: [1596377282]
Possible solutions: formatTemp(java.math.BigDecimal)
There are also a ton of debug messages being logged even though I have debug logging turned off.
Just pushed an update. There was a typo in the strike event handler.
I am purposefully logging the response when an exception occurs. I feel like it's helpful to debug issues, esp since logging gets turned off automatically. If you don't want that you can comment out line 161.
Expecting thunderstorms here today, I'll test it out!
I just got the same exception message in my log. Rain is starting to move in here in the Chicago area but we had a couple of cells popup with a few lighting alerts. Thanks for the fast update.
Pouring here... precipitation rate seems good and the lightning bug seems fixed too. Thanks!
Awesome! Glad it’s working.
I had these crop in the in logs yesterday after a "unhealthy" web socket connection:
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 06:42:32.175 pm [debug](http://ha-hubitat-home.vargofamily.com/device/edit/654){"summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"precip_total_1h":0.0,"strike_last_dist":20,"strike_last_epoch":1596419198,"precip_accum_local_yesterday":0.04638,"precip_accum_local_yesterday_final":0.0,"precip_analysis_type_yesterday":1,"feels_like":27.4,"heat_index":27.4,"wind_chill":27.0},"serial_number":"ST-00006682","hub_sn":"HB-00017489","type":"obs_st","source":"mqtt","obs":[[1596843738,0.09,1.57,2.72,318,3,null,27.1,50,18313,1.12,153,0.0,0,0,0,2.78,1,0.0,null,null,0]],"device_id":74597,"firmware_revision":134}
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 06:42:32.155 pm [error](http://ha-hubitat-home.vargofamily.com/device/edit/654)Failed to parse json e = groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#div. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number]
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:42:10.559 pm [info](http://ha-hubitat-home.vargofamily.com/device/edit/654)Sent list_start for 74597
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:42:10.521 pm [info](http://ha-hubitat-home.vargofamily.com/device/edit/654)webSocket is open [dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:42:09.078 pm [info](http://ha-hubitat-home.vargofamily.com/device/edit/654)initialize()
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:42:07.058 pm [info](http://ha-hubitat-home.vargofamily.com/device/edit/654)Reconnecting WebSocket in 2 seconds.
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:42:07.051 pm [warn](http://ha-hubitat-home.vargofamily.com/device/edit/654)healthCheck: not healthy
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:39:01.771 pm [warn](http://ha-hubitat-home.vargofamily.com/device/edit/654)Unhandled event: [status_code:5, status_message:AUTHORIZATION_REQUIRED - Rate limit exceed or your API Key or Oauth2 Access Token missing]
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-07 03:39:01.760 pm [warn](http://ha-hubitat-home.vargofamily.com/device/edit/654)webSocket connection closing.
Seems like a Java exception was thrown on the response. Also this is the first time I have seen the rate limit.
So the exception is because the summary was reporting null for station_pressure (weird) and I don't have any null handling in place. I haven't seen that happen before. Are you seeing a repeat of this?
Regarding the rate limiting, I've seen this crop up every so often. After switching to a user token I haven't seen this again. I would recommend going that route.
This was the first time I seen the null exception. I went back one week in my logs and it's been clean.
Are you using the shared demo API key? If so, this has apparently been a frequent issue lately.
You can now generate your own personal API key through the TempestWX web site that should solve the problem:
I am using the shared token. I saw this on their board yesterday but didn't take the time yet to try it out. But I did generate a token this morning and put it in. So far so good. I received the exception yesterday 3 times so maybe something was happening on WeatherFlow's side.
I got one last night.
2020-08-19 12:37:41.116 am [debug](http://ha-hubitat-home.vargofamily.com/device/edit/654){"summary":{"pressure_trend":"steady","strike_count_1h":0,"strike_count_3h":0,"precip_total_1h":0.0,"strike_last_dist":40,"strike_last_epoch":1597533173,"precip_accum_local_yesterday":0.0,"precip_analysis_type_yesterday":0,"feels_like":12.5,"heat_index":12.5,"wind_chill":12.5},"serial_number":"ST-00006682","hub_sn":"HB-00017489","type":"obs_st","source":"mqtt","obs":[[1597815458,0.0,0.0,0.0,0,3,null,12.4,92,0,0.0,0,0.0,0,0,0,2.66,1,0.0,null,null,0]],"device_id":74597,"firmware_revision":134}
[dev:654](http://ha-hubitat-home.vargofamily.com/logs/past#dev654)2020-08-19 12:37:41.096 am [error](http://ha-hubitat-home.vargofamily.com/device/edit/654)Failed to parse json e = groovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.math.BigDecimal#div. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number]Since this keeps popping up, I'll add logic to handle the null values.
Does it make more sense to ignore/skip those values or set the corresponding attribute to zero? I like setting to zero because it would otherwise communicate an error, but that could also mess with automations.
My recommendation is to skip the values and leave the previous. Setting to zero not good for automations as you called out.
I have seen this. I had to "restart" my tempest to get it to clear....
So some glitch in the tempest seems to have caused this and for me it did not go away without reboot.
Interesting... that's good to know. Perhaps I should still log an error because otherwise you wouldn't know that anything was wrong until you noticed that an attribute never changed.
Is the only way to reboot to turn it off/on? I'm getting this error almost constantly.
that is all I found
Do we know what’s actually missing?
I’d like to report this to weatherflow
Download the Hubitat app
