I have 3 shelly 1 switches, as far as i know any of them that I add throw the error. I can try to see if its a specific switch or all?
Do you get the error on a command?
no it doesnt line up with commanding the switches. It seems random but maybe some sort of checkin?
No idea at this point. I'm looking at my logs for my shelly 1 and so far not seeing this error.
Its actually the logs for the hubitat google home app, when i remove the shellys from the google home app then the errors go away
I just noticed the error is for a app not a device... what is app 40 ?
I have no idea -- I'll ping @mike.maxwell to see if he might know.
In the mean time does the google home app have any expanded debugging ?
not that i can see
Ok.. let's see what @mike.maxwell says
just to confirm it happens if i add any of the 3 three switches. just tried adding and removing them separately
ok
Just as a test, please remove all the shelly devices from your GH instance, if the error goes away, add in one switch, if the error returns, try changing to the inbuilt driver for the switch.
I have done all of that except switch to the stock driver, I will tonight and report back
@mike.maxwell @Evilborg I have confirmed that there is no error in the logs when using the built in Shelly wifi switch driver.
Well I need more info about the error -- I don't use GH here
Ok, @mike.maxwell is there any way i can give Scott more info about the error?
We can start with screen shots of the driver details using both drivers, there's something about the attributes and or capabilities of the other driver that GH doesn't like.
After changing drivers be sure to refresh the driver page before taking the screen shot.
These are the capabilities and attributes...
capability "Actuator"
capability "Sensor"
capability "Refresh"
capability "Switch"
capability "RelaySwitch"
capability "Polling"
capability "PowerMeter"
capability "EnergyMeter"
capability "VoltageMeasurement"
capability "SignalStrength"
capability "PowerSource"
capability "TemperatureMeasurement"
capability "RelativeHumidityMeasurement"
attribute "FW_Update_Needed", "string"
attribute "LastRefresh", "string"
attribute "power", "number"
attribute "overpower", "string"
attribute "internal_tempC", "string"
attribute "internal_tempF", "string"
attribute "DeviceOverTemp", "string"
attribute "MAC", "string"
attribute "RelayChannel", "number"
attribute "Primary_IP", "string"
attribute "Primary_SSID", "string"
attribute "Secondary_IP", "string"
attribute "Secondary_SSID", "string"
attribute "WiFiSignal", "string"
attribute "Cloud", "string"
attribute "Cloud_Connected", "string"
attribute "energy", "number"
attribute "DeviceType", "string"
attribute "eMeter", "number"
attribute "reactive", "number"
attribute "MaxPower", "number"
attribute "CircuitAmp", "string"
attribute "LED_Output", "string"
attribute "LED_NetworkStatus", "string"
attribute "DeviceName", "string"
attribute "RelayName", "string"
attribute "NTPServer", "string"
If I were to guess it's getting hung up with a switch having temperature related attributes/capabilities.
GH currently can't deal with this combination of capabilities.
The driver supports many shelly devices so that is why they are in it.
1/1PM/2/2.5/EM/Plug/PlugS/4Pro/EM3