Squirrelly things happening

🛎️ Get Help
1

Ok, I am using. C-7 hub running 2.4.0.148

Now, this is very weird. I have a couple of devices that keep changing names. Yep, labels for devices change names to (sometimes) I will end up with two sensors with the same name in different rooms and they are different devices.

One of them I have is called Temp M-Bath, temp garage, temp M-Bed, etc, and the ones changing names is maxcio temp/humid sensors w/out display.

This is baffling because when it does change names, it breaks the apps using it. Funny thing though, I have found nothing in the logs to back this up. No errors listed for them, and no no warnings related to them except the warnings for them falling off the network.

Something else, possible unrelated, but when the hub tries to (I don't know) but I had an app installed NOAA, and then decided I did not like it so I uninstalled it. Now, everytime the hub tries to update, it keeps trying to update the NOAA app, but it can't find the NOAA app. This is making me want to shoot it. JK

Thanks for any input.

2

First thing to do is a reboot with database rebuild. After that if it hasn’t stablized we’ll need to dig further.

3 Likes
3

This sounds like a custom app, which the hub doesn’t update.

Are you perhaps referring to Hubitat Package Manager?

If you used HPM to install an app, and then deleted the app code from your hub manually, then that could fit with what you’re describing.

2 Likes
4

Maxico is a Tuya device. Are yours wifi or Zigbee? What driver (type) are they set to?

5

Ok, I finally got the NOAA part fixed.

As for the temp sensors, they are Zigbee, not wifi. When I get home I will try the reboot with device rebuild like suggested and I will report back

Thanks everyone.

6

@jtp10181

The Maxico sensors, they do sort of work with the generic Zigbee temp-humid sensors driver but it is giving me error messages using that driver.

My hub is a c-7 running 2.4.0.151

dev:6482025-01-25 10:05:07.048 PM

error

org.codehaus.groovy.runtime.metaclass.MissingMethodExceptionNoStack: No signature of method: genericZigbeeTempHumSensor.deviceHealthCheck() is applicable for argument types: () values: (method deviceHealthCheck)

Thanks for the help.

7

This is a scheduled periodic job, leftover from the previous custom driver.
You can delete it using the HE inbuilt ’Device’ driver commands.

8

Or go to Logs, Scheduled jobs tab, find that one and delete it.

The driver method you switch the type/driver to “device” then use the command button to delete scheduled jobs.

9

Ok, thanks guys, I think I understand now. With me trying different setups to find the one that worked best, I was introducing artifacts (scheduled jobs) faster than I could remove the errors. :melting_face:

Well, thanks again everyone for not getting pissed with the new guy.