Add new GatewayType - 121
Closed this issue · 12 comments
Hi,
Attempting to use via HomeAssistant but my TaHoma Switch fails to add and logs this error,
2024-10-20 16:15:43.923 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 121 has been returned for <enum 'GatewayType'>
The device paired to the TaHome Switc is a 'RTS Micro Receiver', SMA-RTS by SM Automatic to control a curtain.
If you need any other details just let me know.
The error received in Home Assistnat is a generic 'Failed to Connect'. Developer mode activated on both.
Cloud pairing works. I was able to Download Diagnostics and this is what I got ..
"gateways": [
{
"gatewayId": "****-****-8584",
"type": 121,
"subType": 1,
"placeOID": "c632bcab-0b6e-4b71-aa69-8c296c769c5d",
"autoUpdateEnabled": true,
"alive": true,
"timeReliable": true,
"connectivity": {
"status": "OK",
"protocolVersion": "2024.4.3"
},
"upToDate": true,
"updateStatus": "UP_TO_DATE",
"syncInProgress": false,
"mode": "ACTIVE",
"functions": "INTERNET_AUTHORIZATION,SCENARIO_DOWNLOAD,SCENARIO_AUTO_LAUNCHING,SCENARIO_TELECO_LAUNCHING,INTERNET_UPLOAD,INTERNET_UPDATE,TRIGGERS_SENSORS"
},
{
"gatewayId": "****-****-7638",
"type": 121,
"subType": 1,
"placeOID": "c632bcab-0b6e-4b71-aa69-8c296c769c5d",
"autoUpdateEnabled": true,
"alive": true,
"timeReliable": true,
"connectivity": {
"status": "OK",
"protocolVersion": "2024.4.3"
},
"upToDate": true,
"updateStatus": "UP_TO_DATE",
"syncInProgress": false,
"mode": "ACTIVE",
"functions": "INTERNET_AUTHORIZATION,SCENARIO_DOWNLOAD,SCENARIO_AUTO_LAUNCHING,SCENARIO_TELECO_LAUNCHING,INTERNET_UPLOAD,INTERNET_UPDATE,TRIGGERS_SENSORS"
}
{
"creationTime": 1729457271000,
"lastUpdateTime": 1729457271000,
"label": "** ** ** **",
"deviceURL": "rts://****-****-7638/16724292",
"shortcut": false,
"controllableName": "rts:RollerShutterRTSComponent",
"definition": {
"commands": [
{
"commandName": "close",
"nparams": 1
},
{
"commandName": "down",
"nparams": 1
},
{
"commandName": "identify",
"nparams": 0
},
{
"commandName": "my",
"nparams": 1
},
{
"commandName": "open",
"nparams": 1
},
{
"commandName": "rest",
"nparams": 1
},
{
"commandName": "stop",
"nparams": 1
},
{
"commandName": "test",
"nparams": 0
},
{
"commandName": "up",
"nparams": 1
},
{
"commandName": "openConfiguration",
"nparams": 1
}
],
"states": [],
"dataProperties": [
{
"value": "0",
"qualifiedName": "core:identifyInterval"
}
],
"widgetName": "UpDownRollerShutter",
"uiProfiles": [
"OpenCloseShutter",
"OpenClose"
],
"uiClass": "RollerShutter",
"qualifiedName": "rts:RollerShutterRTSComponent",
"type": "ACTUATOR"
},
"attributes": [
{
"name": "rts:diy",
"type": 6,
"value": false
}
],
"available": true,
"enabled": true,
"placeOID": "c632bcab-0b6e-4b71-aa69-8c296c769c5d",
"type": 1,
"widget": "UpDownRollerShutter",
"oid": "34a9b102-cfc0-4a82-b4f1-876f5fd0fbfb",
"uiClass": "RollerShutter"
},
{
"creationTime": 1729457410000,
"lastUpdateTime": 1729457410000,
"label": "** ** ** **",
"deviceURL": "rts://****-****-8584/16762206",
"shortcut": false,
"controllableName": "rts:RollerShutterRTSComponent",
"definition": {
"commands": [
{
"commandName": "close",
"nparams": 1
},
{
"commandName": "down",
"nparams": 1
},
{
"commandName": "identify",
"nparams": 0
},
{
"commandName": "my",
"nparams": 1
},
{
"commandName": "open",
"nparams": 1
},
{
"commandName": "rest",
"nparams": 1
},
{
"commandName": "stop",
"nparams": 1
},
{
"commandName": "test",
"nparams": 0
},
{
"commandName": "up",
"nparams": 1
},
{
"commandName": "openConfiguration",
"nparams": 1
}
],
"states": [],
"dataProperties": [
{
"value": "0",
"qualifiedName": "core:identifyInterval"
}
],
"widgetName": "UpDownRollerShutter",
"uiProfiles": [
"OpenCloseShutter",
"OpenClose"
],
"uiClass": "RollerShutter",
"qualifiedName": "rts:RollerShutterRTSComponent",
"type": "ACTUATOR"
},
"attributes": [
{
"name": "rts:diy",
"type": 6,
"value": false
}
],
"available": true,
"enabled": true,
"placeOID": "c632bcab-0b6e-4b71-aa69-8c296c769c5d",
"type": 1,
"widget": "UpDownRollerShutter",
"oid": "ab2542cd-739c-4c5b-8fa3-359d630b2026",
"uiClass": "RollerShutter"
},
Thanks for reporting @astyrrian1! The "Failed to connect" error is not related to your enum warning, but we will add your new GatewayType to our enums.
Regarding the error, are you sure you can ping the gateway / ip address from Home Assistant?
Yes the gateway is reachable and discovered by Home Assistant. After connecting via Cloud I turned on Debug logging for Overkiz and attempted to connect again..
2024-10-20 16:33:00.287 DEBUG (MainThread) [homeassistant.components.overkiz] Finished fetching device events data in 1.044 seconds (success: True)
2024-10-20 16:33:19.685 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --8584 on gateway-2045-8295-8584.local. (_kizbox._tcp.local.)
2024-10-20 16:33:19.687 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --8584 on gateway-2045-8295-8584.local. (_kizboxdev._tcp.local.)
2024-10-20 16:33:19.938 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --7638 on gateway-2045-8201-7638.local. (_kizbox._tcp.local.)
2024-10-20 16:33:20.686 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --8584 on gateway-2045-8295-8584.local. (_kizboxdev._tcp.local.)
2024-10-20 16:33:20.687 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --8584 on gateway-2045-8295-8584.local. (_kizbox._tcp.local.)
2024-10-20 16:33:21.840 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --7638 on gateway-2045-8201-7638.local. (_kizbox._tcp.local.)
2024-10-20 16:33:29.841 DEBUG (MainThread) [homeassistant.components.overkiz] ZeroConf discovery detected gateway --7638 on gateway-2045-8201-7638.local. (_kizbox._tcp.local.)
2024-10-20 16:33:30.437 INFO (MainThread) [backoff] Backing off fetch_events(...) for 0.2s (pyoverkiz.exceptions.NotAuthenticatedException: Not authenticated)
2024-10-20 16:33:31.096 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 121 has been returned for <enum 'GatewayType'>
2024-10-20 16:33:31.096 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 121 has been returned for <enum 'GatewayType'>
2024-10-20 16:33:31.407 DEBUG (MainThread) [homeassistant.components.overkiz] Event(name=<EventName.GATEWAY_SYNCHRONIZATION_STARTED: 'GatewaySynchronizationStartedEvent'>, timestamp=1729460011251, setupoid=_CountingAttr(counter=524, _default=None, repr=<function obfuscate_id at 0xffff373d4ea0>, eq=True, order=True, hash=None, init=True, on_setattr=None, alias=None, metadata={}), owner_key=None, type=None, sub_type=None, time_to_next_state=None, failed_commands=None, failure_type_code=None, failure_type=None, condition_groupoid=None, place_oid=None, label=None, metadata=None, camera_id=None, deleted_raw_devices_count=None, protocol_type=None, gateway_id=--8584, exec_id=None, device_url=None, device_states=[], old_state=None, new_state=None)
2024-10-20 16:33:31.408 DEBUG (MainThread) [homeassistant.components.overkiz] Finished fetching device events data in 1.164 seconds (success: True)
Cloud connectivity and local connectivity is not related. I don't see evidence above that you can reach / ping your device.
Nevertheless, we will add your gateway so you don't get any warnings anymore.
How can the device be automatically discovered on the local network but not reachable?
Strangely I just removed from cloud and attempted to add locally and one gateway successfully added... the other still fails with the same error... I will try rebooting it.
@astyrrian1 there is a difference between detecting your gateway, and being able to connect to your gateway via developer mode. I am happy to see where we can support, but in my experience 90% of the issues is because Home Assistant can't reach / ping your local gateway on port 8443.
This is something that is behind our control. It can be caused by the gateway or by the HA connectivity.
Home Assistant can ping the gateway by name and IP address.
Once I got it to successfully work with one TaHoma Switch locally, I just paired the rest of my devices to it and gave up on the second one that wouldn't connect locally. I have no idea how or why the first one started working. They were both discoverable and pingable from HA.
Do you have more information on your gateway type? What type of TaHoma Switch is it?
It seems to have failed to connect any longer...
This is the TaHoma Switch (US)
https://www.somfysystems.com/en-us/products/1871037/tahoma-switch
2024-11-17 22:20:44.573 WARNING (MainThread) [pyoverkiz.enums.gateway] Unsupported value 121 has been returned for <enum 'GatewayType'>
2024-11-17 22:20:44.833 DEBUG (MainThread) [homeassistant.components.overkiz] Cannot connect to host gateway-2045-8295-8584.local:8443 ssl:<ssl.SSLContext object at 0xffff4aa94ad0> [Connect call failed ('192.168.0.122', 8443)]
The devices are able to be controlled successfully through the TaHoma app.. they are all on the same network.
Please create a new issue for this on the core repo (or preferably, first check the open issues). This is not related to the warning of the GatewayType.
Please note that the TaHoma app does not use the local API, so you can't compare that.