Hello, was the shade control added to the main branch?
Unfortunately, @toby did not submit his changes
Just a quick question and Im not sure if anyone has this particular tie in between HA and Hubitat but for some reason I cannot get my Meross garage door opener to show up in my devices in Hubitat. Its in HA and works in HA. I can see it and check the box to add it to Hubitat in the app but it will not show up in my devices. Even after I do an open and close through HA. Any ideas?
1 Like
Turn on logging on the parent device in Hubitat and then open the Logs window and operate the door a few times. I'd like to see what events data comes across when you open and close.
dev:1622022-04-15 01:35:11.281 pm debugparse(): description = {"id": 1, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "sensor.manager_mqtt_messages_s", "old_state": {"entity_id": "sensor.manager_mqtt_messages_s", "state": "0.0667", "attributes": {"api_calls_per_second": 0.0667, "delayed_api_calls_per_second": 0.0, "dropped_api_calls_per_second": 0.0, "unit_of_measurement": "msg/s", "icon": "mdi:cloud", "friendly_name": "Manager MQTT messages/s"}, "last_changed": "2022-04-15T18:34:55.230588+00:00", "last_updated": "2022-04-15T18:34:55.230588+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.manager_mqtt_messages_s", "state": "0.0", "attributes": {"api_calls_per_second": 0.0, "delayed_api_calls_per_second": 0.0, "dropped_api_calls_per_second": 0.0, "unit_of_measurement": "msg/s", "icon": "mdi:cloud", "friendly_name": "Manager MQTT messages/s"}, "last_changed": "2022-04-15T18:35:10.231767+00:00", "last_updated": "2022-04-15T18:35:10.231767+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2022-04-15T18:35:10.231767+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}}
dev:1622022-04-15 01:34:56.280 pm debugparse(): description = {"id": 1, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "sensor.manager_mqtt_messages_s", "old_state": {"entity_id": "sensor.manager_mqtt_messages_s", "state": "0.0", "attributes": {"api_calls_per_second": 0.0, "delayed_api_calls_per_second": 0.0, "dropped_api_calls_per_second": 0.0, "unit_of_measurement": "msg/s", "icon": "mdi:cloud", "friendly_name": "Manager MQTT messages/s"}, "last_changed": "2022-04-15T17:42:08.256373+00:00", "last_updated": "2022-04-15T17:42:08.256373+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "sensor.manager_mqtt_messages_s", "state": "0.0667", "attributes": {"api_calls_per_second": 0.0667, "delayed_api_calls_per_second": 0.0, "dropped_api_calls_per_second": 0.0, "unit_of_measurement": "msg/s", "icon": "mdi:cloud", "friendly_name": "Manager MQTT messages/s"}, "last_changed": "2022-04-15T18:34:55.230588+00:00", "last_updated": "2022-04-15T18:34:55.230588+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}}, "origin": "LOCAL", "time_fired": "2022-04-15T18:34:55.230588+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}}
dev:1622022-04-15 01:34:55.717 pm errorParsing error: com.hubitat.app.exception.UnknownDeviceTypeException: Device type 'Generic Component Garage Door Control' in namespace 'community' not found
dev:1622022-04-15 01:34:55.713 pm debugparse: domain: cover, device_class: garage, entity: cover.big_garage_msg100_main_channel, newVals: [open], friendly: Big Garage
dev:1622022-04-15 01:34:55.686 pm debugparse(): description = {"id": 1, "type": "event", "event": {"event_type": "state_changed", "data": {"entity_id": "cover.big_garage_msg100_main_channel", "old_state": {"entity_id": "cover.big_garage_msg100_main_channel", "state": "closed", "attributes": {"device_class": "garage", "friendly_name": "Big Garage", "supported_features": 3}, "last_changed": "2022-04-15T17:41:54.028210+00:00", "last_updated": "2022-04-15T17:41:54.028210+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": null}}, "new_state": {"entity_id": "cover.big_garage_msg100_main_channel", "state": "open", "attributes": {"device_class": "garage", "friendly_name": "Big Garage", "supported_features": 3}, "last_changed": "2022-04-15T18:34:54.615860+00:00", "last_updated": "2022-04-15T18:34:54.615860+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": "xxx"}}}, "origin": "LOCAL", "time_fired": "2022-04-15T18:34:54.615860+00:00", "context": {"id": "xxx", "parent_id": null, "user_id": "xxx"}}}
--- Live Log Started, waiting for events ---
I xxx'd the IDs. I beleive the issue is coming from the errorParsing error. It doesnt look like it knows the device type. Wild guess but it looks like a problem
When you install via HPM, certain device types are optional. You have to manually select the "Generic Component Garage Door Control" because it is optional.
If you used HPM, you can go back in and use the Modify function to add this one in. If you installed manually from GitHub, just go and get that driver in addition to the ones you already have.
3 Likes
Perfect! Yep that fixed it! Wow so easy. Thank you for taking the time to assist me with this!
4 Likes
I have Home Assistant running for the sole function of bringing our MQTT enabled hot tub into HE. It had been working perfectly. I just discovered that at some point things stopped updating. The device to HA seems to working fine however, Hubitat doesn't seem to be reflecting the correct states etc. I've tried reinitializing the connection but no luck. I am totally clueless about where to start with trouble shooting this.
Turn on logging on the parent device and do some operations on the hot tub that would normally have shown up in HE. It'll be necessary to see what (if anything) is coming across from HA.
1 Like
HOLY CRAP! a ton of stuff is flooding in with debug on
1 Like
I wonder if I will have to delete child devices and re add. Man that will be a pain cause I have them set up with several things
Which attributes are you trying to track? Energy?
Temperature and also some switch controls
I only see energy and rssi in the logs you posted. Are you seeing temperature and switch state coming across? Is it configurable how often they report from the spa to MQTT?
I went through the huge amount of info and found that temperature is coming through.
Edit: Is it possible I made a problem by changing the device names in HE?
Edit edit....scratch that. I only changed the labels. the names have remained the same.
I think I'm on to something! I see that somehow the name became climate.layzspa_temperature_control_2
SOMEhow a second entity got created. hmmmm
Now...how to fix this
Just went in and added the randomly appearing second entities.
Those names come directly from HA. I would recommend looking over there in the configuration to see what happened.
1 Like
@tomw Wondering if anything can be done with this. I'm using Sense for my home power monitoring (Yes, everyone who said not to, I ignored you and did it anyway 
) and for me it's working well. I've added the HA integration and it reports when devices turn on/off as using the Generic Component Power Meter driver</> that @mike.maxwell created for us.
Unfortunately, I cannot use these binary devices in Rule Machine, because it's expecting a numeric value from a power meter, but the power status that HA is reporting is a string value. Can this be addressed from HA Device Bridge, or would this need to be a change that would require a modification of Rule Machine?
This is where the change should be made.
2 Likes
