3007,"code":"ENOTFOUND

[Jailobeam]

Since today this error appears only when using the LocalApi very very long now well today the first time problem with the LocalApi

does anyone have a solution ? has something been changed in the Api of the box ?

Conexxion Box
XXXX-XXXX-XXXX is masked my Real ID

tahoma.0	2025-04-09 21:15:08.288	warn	error during request: Error: getaddrinfo ENOTFOUND gateway-XXXX-XXXX-XXXX, request path: setup/gateways with payload:{}
tahoma.0	2025-04-09 21:14:58.315	warn	{"error":{"errno":-3007,"code":"ENOTFOUND","syscall":"getaddrinfo","hostname":"gateway-XXXX-XXXX-XXXX}}
tahoma.0	2025-04-09 21:14:58.314	warn	setup failed!

[Excodibur]

I got the same issue recently. It seems like most Somfy-users seems to experience it at the moment, not only with this ioBroker Adapter, but also Homeassistant.

As far as I can tell Somfy is still looking into it, but hard reseting the box (without data loss) seems to be the workaround so far, see Somfy-Developer/Somfy-TaHoma-Developer-Mode#172.

Hard reseting is done by pressing the reset-hole with a thin clip for 7 seconds. When I did it, the box-light for the Tahoma box switched to blinking red for a while, until becoming green again. When logging into tahomalink.com after that it showed me something about an "Update" being installed, although I did not see anything available before the reset. After that was done and I restarted the adapter in ioBroker, everything worked as before again. IO devices are all still there and working.

[Jailobeam]

many thanks for the information
but a reset is too unsafe for me i have a Connexoon box and don't want to take the risk of having to reset everything

as i have already written in the forum it is simply due to the name resolution which i have solved with my DNS entry

can you adjust the field for the pin so that no prefix "gateway-" is used ? or insert a checkbox for this ?

or change the whole thing to IP so that such DNS problems don't occur at all ?

many thanks
greetings Jailo

[muhlatte]

rst button for 7secs worked well for me, had the same issue since 4 days. All the data still retains on my tahoma V2.
Thank you very much for the hint and solution!

[Excodibur]

@Jailobeam Please check https://github.com/Excodibur/ioBroker.tahoma/releases/tag/v0.11.0

[Jailobeam]

@Excodibur THX , If I only enter the IP, it no longer tries local but only cloud.
or is both pin and ip required?

EDIT

ok in debug it looks good

if both are entered it still calls via IP so is perfect
many thanks for that !

but now i have an error that comes from the adapter at startup

admin.0 | 2025-04-15 21:28:44.376 | warn | tahoma  has an invalid jsonConfig:  [{"instancePath":"/items/basicSettingsTab/items/note","schemaPath":"#/patternProperties/%5E.%2B/allOf/37/then/oneOf","keyword":"oneOf","params":{"passingSchemas":[0,1]},"message":"must  match exactly one schema in  oneOf"},{"instancePath":"/items/basicSettingsTab","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/9/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must  match \"then\"  schema"},{"instancePath":"","schemaPath":"#/if","keyword":"if","params":{"failingKeyword":"then"},"message":"must  match \"then\" schema"}]
-- | -- | -- | --

[Excodibur]

Yeah both are required. Perhaps pin ist not really needed, but for now I added localip as an additional setting. I'll check this week again if the pin could be left out in this case

[Excodibur]

Regarding the warning I will check it this week