LZW60 4-in-1 Sensor Freezing

Digital Lounge
#1

I’ve had 3 failures of my new 4-in-1 Sensor. I’ve reported this and only gotten a response about support is busy due to COVID-19. Since it’s just failed again I thought I’d throw this on the table here. I’ve had this happen when running on battery and directly connected to power.

I’m using my unit as a sensor to allow my Hubitat to control indoor lighting. I am reporting light levels every 60 seconds, temperature every 180 and humidity every 300. After 48+ hours of run time, the unit freezes. No reporting. Log just stop showing the reports. I’ve tried a few things. I tried to refresh. No response. I tried to send down the configuration and I show errors in the log regarding the device parameters I am trying to send. The only thing that fixes the problem is to Exclude the 4-in-1 from the Hubitat, then pair it, and finally load down the configuration. I also have to repair the Hubitat Rule Machine app which has deleted the references to the 4-in-1 that had been excluded. Once I do that, all runs well for another 48+ hours and then we crash again.

My feeling is I discovered a bug or have a hardware failure. I’ve tried other things like removing the 4-in-1 from power and then powering it on. I’ve also tried restarting the Hubitat. Anyone have any ideas or how long it will take Inovelli to address my email and problem?

Here’s the log of the failure. You will see it stopped reporting around 5:30 pm

dev:452020-06-03 07:35:20.165 pm infoInovelli 4-in-1 Sensor: parameter ‘103’ with a byte size of ‘4’ is set to ‘60’

dev:452020-06-03 07:35:19.008 pm infoInovelli 4-in-1 Sensor: Retreiving value of parameter 103

dev:452020-06-03 07:35:18.983 pm infoInovelli 4-in-1 Sensor: Setting parameter 103 with a size of 4 bytes to 10

dev:452020-06-03 07:35:18.950 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:452020-06-03 07:35:18.938 pm infoInovelli 4-in-1 Sensor: initialize()

dev:452020-06-03 07:35:18.935 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

dev:42020-06-03 06:06:08.955 pm infoColor Light saturation is 100%

dev:42020-06-03 06:05:51.051 pm infoColor Light colorTemperature is 2702°K

dev:42020-06-03 06:05:51.050 pm infoColor Light hue is 217°

dev:452020-06-03 05:32:28.937 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 118

dev:452020-06-03 05:32:28.789 pm infoInovelli 4-in-1 Sensor: Humidity report received: 42

d

In this example I tried the 3 button push to wake up the unit. It still is frozen on the reporting side.

#2

Ok, I’ve done some more trouble shooting. Apparently if i use the refresh button within the device section of the 4-in-1 within Hubitat, the sensors all wake up and send current reports. Then everything goes to sleep again. So it looks like we are not locked up. It’s just the fact that all the sensors after passing that 48+ hours of run time no longer follow the parameter regarding reporting times that are set for them. Fyi I have the threshold reporting set to no. Here’s the current parameters as of now.

  • parameter113value : 1
  • batteryRuntimeStart : 1590988552237
  • parameter110value : 0
  • realLuminance : 122
  • parameter10value : 10
  • parameter13value : 30
  • parameter102value : 300
  • desiredAssociation1 : 1
  • wakeInterval : 43200
  • parameter111value : 1
  • realTemperature : 87.2
  • lastRan : 1591279391872
  • parameter114value : 1
  • lastRefresh : 1591280328478
  • parameter14value : 0
  • parameter103value : 60
  • lastBatteryReport : 1591280328565
  • associationGroups : 2
  • parameter15value : 0
  • parameter104value : 7200
  • needfwUpdate : false
  • defaultG3 : []
  • actualAssociation2 : []
  • parameter112value : 1
  • defaultG2 : []
  • actualAssociation1 : [01]
  • defaultG1 : [01]
  • realHumidity : 35
  • parameter12value : 0
  • parameter101value : 180

Still no further logging. So I tried something different. I took the unit from its locale, disconnected it from fixed power and put the battery back in. Walked it into my kitchen about 20 feet from the Hubitat unit. (Typically the 4-in-1 sits about 2 feet from the Hubitat). Pushed the button on the 4–in-1 three times quickly pushed the config button on the device app on the Hubitat. Then I pushed refresh. Now it’s working. Reports flowing down as they should be. So I pulled the battery, brought the 4-in-1 back to its powered location, and plugged it in. It restarted fine and now we are reporting. Only other thing I did was I stopped the job that was running on the Hubitat that uses the reports. After I saw the 4-in-1 running properly and reporting, I restarted the job. All still fine. This job runs constantly in a wait state watching for a trigger from the 4-in-1 that the light level has reached 41 lux. Once it hits that it turns on the inside lights and then watches the lux level. If it hits over 43 and we are in daytime mode, I know it was probably a storm or dark clouds that have passed and the lights are turned off. At that point the instructions go back to the job waiting for the light level to reach 41. It works really well but this 48+ hours cycle on the 4-in-1 puzzles me. I going to continue to trouble shoot but at this point even if I find the key to getting the 4-in-1 to restart it’s reporting cycle, I’m not satisfied in having to do manual intervention like this.

#3

Got my replacement unit in yesterday and here’s what I have come up with so far. In this case I started up the new unit with the Inovelli provided driver.

Within an hour the unit failed to report from it’s sensors (light, temperature, humidity). Last report was 5:59 pm. The next entry in the logs came at 6:12. Here’s the portion of the log showing it reporting, then failing to report further. You will notice at that point I am attempting to reconfigure the unit.

dev:772020-06-07 06:12:12.050 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:12:11.897 pm infoInovelli 4-in-1 Sensor: If this sensor is battery powered, the configuration options (aside from temp, hum, & lum offsets) will not be updated until the sensor wakes up. T 020-06-07 06:13:08.234 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

dev:772020-06-07 06:12:12.561 pm infoInovelli 4-in-1 Sensor: Firmware report received: 2.03

dev:772020-06-07 06:12:12.063 pm infoInovelli 4-in-1 Sensor: Requesting device firmware version

dev:772020-06-07 06:12:12.060 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:12:12.050 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:12:11.897 pm infoInovelli 4-in-1 Sensor: If this sensor is battery powered, the configuration options (aside from temp, hum, & lum offsets) will not be updated until the sensor wakes up. To manually wake up the sensor, press the button on the back 3 times quickly.

dev:772020-06-07 06:12:11.895 pm infoInovelli 4-in-1 Sensor: updated()

dev:772020-06-07 05:59:12.676 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:58:12.775 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:58:12.592 pm infoInovelli 4-in-1 Sensor: Temperature report received: 82

dev:772020-06-07 05:57:12.791 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:57:12.617 pm infoInovelli 4-in-1 Sensor: Humidity report received: 39

dev:772020-06-07 05:56:12.697 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:55:12.766 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:55:12.596 pm infoInovelli 4-in-1 Sensor: Temperature report received: 81.8

dev:772020-06-07 05:54:12.673 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:53:12.698 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:52:12.910 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:52:12.689 pm infoInovelli 4-in-1 Sensor: Humidity report received: 39

dev:772020-06-07 05:52:12.592 pm infoInovelli 4-in-1 Sensor: Temperature report received: 81.8

dev:772020-06-07 05:52:02.035 pm infoInovelli 4-in-1 Sensor: Disabling logging after timeout

dev:772020-06-07 05:51:12.693 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 33

dev:772020-06-07 05:50:12.689 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 34

dev:772020-06-07 05:49:12.764 pm infoInovelli 4-in-1 Sensor: Illuminance report received: 35

dev:77

What’s interesting is I see a timeout at 5:52:02 which says logging is disabled. Also not shown is that even with parameter 12 value showing 0 motion on my device page in my Hubitat shows active. That’s a common trait I saw with the previous sensor.

So I attempt to reconfigure and the log shows this.

2020-06-07 06:13:23.839 pm errorjava.lang.ArrayIndexOutOfBoundsException: -1 on line 451 (configure)

dev:772020-06-07 06:13:23.689 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:13:23.679 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:13:23.677 pm infoInovelli 4-in-1 Sensor: configure()

dev:772020-06-07 06:13:21.615 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:13:21.602 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:13:21.599 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

dev:772020-06-07 06:13:16.344 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:13:16.333 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:13:16.331 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

dev:772020-06-07 06:13:12.046 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:13:12.033 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:13:12.031 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

dev:772020-06-07 06:13:08.246 pm infoInovelli 4-in-1 Sensor: There are no association actions to complete for group 1

dev:772020-06-07 06:13:08.236 pm infoInovelli 4-in-1 Sensor: initialize()

dev:772020-06-07 06:13:08.234 pm infoInovelli 4-in-1 Sensor: WakeUp Notification received

Notice the java error. I saw that before with the old sensor too.

So at that point I decided to change drivers. This time I’m using the driver written by Bryan Copeland. All works well with that driver other than I notice that I cannot set the time report parameter for the humidity 102 parameter. It only shows 7200 which is the default. Also noticeable is that the parameter 12 setting is also set at zero (same as when using the Inovelli supplied driver. However the device screen on the Hubitat shows motion inactive. Interesting…

Also noticeable is the Inovelli driver show wake Interval at 43200. Bryan’s driver is showing 3600. And I see the wake up commands firing off on his driver, every hour.

Bottom line I come to conclusion there may be some issues with the Inovelli driver

  1. I’m seeing timeouts. No wake ups unless I manually push the button.
  2. The device screen shows the motion active even though the parameter 12 option is set at 0.
  3. I get java errors when attempting to reconfigure the 4-in-1

So far I’ve had no failures with Bryan’s driver and I’m getting some suspicions regarding the wakeInterval timing which could be affecting the performance of the light, temperature and humidity sensors.

At this point I’ll continue watching and see if we get past the 48 hour run time point, which seemed to be the tipping point where my previous unit failed to update or report.

#4

@EricM_Inovelli – hey can you take a look at this when you get a chance?

#5

I believe Hubitat automatically enables Debug Logging during the initial device discovery for a period of time and then disables it shortly thereafter which may be why you see that entry.

-Travis

#6

Could be…but doesn’t explain why if the reported temperature from the device does not get updated. Logging maybe I can understand, but the event data is truly not changing at that point. That’s why I’m leaning towards a driver issue. I think the sensors are functioning but the driver for some reason is failing to take that data and report it.

Good thought though and in my case doesn’t explain two days of running and reporting and the sudden lack of reporting.

#7

Passed the 48 hour mark with the new replacement device and no signs of issues. Not sure if was hardware or the driver…or a combination of both. If things continue to run well, I might try to switch back to the Inovelli written driver and see if the issue comes back.

1 Like
#8

@Eric_Inovelli
I ran 14 days with a replacement device using the @bcopeland driver. All was well. Got back from a trip and switched over today to the most current Inovelli driver. Unit ran for about an hour and all the sensors shut down again. Just like last time. Went back to the @bcopeland driver and the unit is running just fine again. There is something going on the Inovelli driver that just disables the sensors from reporting after some time factor. Not sure what the condition is but in my situation I’m not using the motion sensor and have that sensor disabled. I’m reporting light every minute, temperature every two, and humidity every 5 minutes.