search

mobilutz / ioBroker.freeathome

Adapter to include free@home into ioBroker.
MIT License
12 stars 5 forks source link

Unable to connect #70

Closed TheSpirit closed 4 years ago

TheSpirit commented 4 years ago

Hi. I installed your adapter but the instance is not able to connect to free@home. Here is the info of my system. What could be the problem? Thanks Bildschirmfoto 2020-04-27 um 21 24 42

mobilutz commented 4 years ago

@TheSpirit Do you maybe have some infos, for example logs output?

I had a problem in the last couple of days, but after iobroker upgrade everything worked again.

TheSpirit commented 4 years ago

hi. this is the only info i get within iobroker log Bildschirmfoto 2020-04-28 um 10 58 27

mobilutz commented 4 years ago

Maybe the settings for the SystemAccessPoint is not correct. Please check if the settings of the adapter are correct.

TheSpirit commented 4 years ago

what should be wrong? i only have set ip, login name and password the same credentials work fine within openhab but i use openhab only for free@home and would like to switch to iobroker with all my iot thanks

TheSpirit commented 4 years ago

any ideas what i can do?

mobilutz commented 4 years ago

There does not seem to be an obvious thing to be wrong. Maybe there is a whiteboard in the IP or so.

Please check if the settings you have look like this: https://github.com/mobilutz/ioBroker.freeathome/issues/56#issuecomment-606495530

TheSpirit commented 4 years ago

i read there, that the other one used node version 10.x i am allready on 12.x or is this not the nodejs version? is my npm version ok? one last thing. i am still on 2.1.7 on my free@home bridge

mobilutz commented 4 years ago

It could be, that the node 12.x does not work. I am also still running on node 10.x so I haven't tested the adapter under node 12.x

I will see to upgrade sometime and then I will take a deeper look into it.

TheSpirit commented 4 years ago

i just tried version 10.x but it still did not work

mobilutz commented 4 years ago

Then I think, that there is something not correct in the setup. Maybe an extra whitespace in the username, password or hostname?

TheSpirit commented 4 years ago

will set up a new user with only one character for username and password. which privileges does the user need?

TheSpirit commented 4 years ago

one additional thing. my system access point is still on 2.1.7 could this be the problem?

TheSpirit commented 4 years ago

created a new user with config options. still no connection. this is the silly log Bildschirmfoto 2020-05-04 um 12 13 24 Does the "could not connect" mean ip is incorrect or user password is not correct?

mobilutz commented 4 years ago

What version of the SysAP are you running?

It seems that the IP is ok, but the login information is not correct. You could try this package directly: https://github.com/henry-spanka/freeathome-api#readme This is used here to connect to the SysAP.

mobilutz commented 4 years ago

Ah sorry, I didn't see this message: https://github.com/mobilutz/ioBroker.freeathome/issues/70#issuecomment-623355640

Yes, that is the problem.

From the package I liked above: It requires a System Access Point with version 2.3.1 or higher.

TheSpirit commented 4 years ago

i just updated to 2.5 and it now works perfect with 12.16.3 i just implement it now within my loxone system. if you need any help what the datapoints meen, feel free to ask. allready helped with the datapoints for the binding for openhab.

mobilutz commented 4 years ago

Cool that the adapter is working with node 12.x :)

I will get back to you, once I have time to do something here ...