ioBroker / ioBroker.wolf

Connect WOLF heating, solar and domestic ventilation
MIT License
25 stars 16 forks source link

No objects created from WOLF adapter #64

Closed JarlMorgennebel closed 2 years ago

JarlMorgennebel commented 2 years ago

Hej,

my ISM8i-Modul is configured to use DHCP and uses IP-address 192.168.1.158/24 ("LAN" Network).

Bildschirmfoto 2022-04-24 um 16 44 25

My IOBroker is configured at 192.168.3.30/24 and uses Port 12004 for WOLF ("SERVERLAN" network).

Between LAN- and SERVERLAN network an Opnsense firewall routes traffic. To allow traffic from ISM8i to IOBroker a very open rule is configured:

Allow IPv4/Any Protocol, Any Port. to Host_IOBroker, Any Port

Bildschirmfoto 2022-04-24 um 16 46 50

Connect from LAN any client to Wolf adapter on Port 12004 is working fine (tested with telnet):

Bildschirmfoto 2022-04-24 um 16 49 21

And IOBroker shows active connections from ISM8i on the Linux operating system level:

Bildschirmfoto 2022-04-24 um 16 51 56

Wolf Adapter is configured but is not creating any objects:

Bildschirmfoto 2022-04-24 um 16 53 32

I have restarted the Adapter and the Host. No changes.

What else can I test to get the Wolf adapter working again?

Thanks, -JM

Apollon77 commented 2 years ago

What is configured in the "bind" setting of the adapter? In fact this would mean that no connection is done, OR that no data coming back after adapter is asking for them ...

You can install GitHub version and set the loglevekl of the instance to "debug" then you see if a connection comes in

JarlMorgennebel commented 2 years ago

Hej,

Thanks for the quick follow-up.

The adapter is configured to use eth0 IP 192.168.3.30, Port 12004. Which works fine, as I can establish a connection using telnet to the Adaptor (TCP handshake is completed and data transferred)

Bildschirmfoto 2022-04-24 um 17 30 26

I'll install the GitHub version and post a debug.

TY .

Apollon77 commented 2 years ago

Please check the other options for the bind setting ... and you really tried to connect from an other computer in the network? Not that this bind setting just allows local connections ... I would have expected a 0.0.0.0 or such

JarlMorgennebel commented 2 years ago

Interesting.

The GitHub installation works fine and Objects are created. But I do get a lot of warnings:

2022-04-24 17:34:08.046 | warn | State value to set for "wolf.0.sm1.195" has value "32768" greater than max "10000"
wolf.0 | 2022-04-24 17:34:07.191 | info | State value to set for "wolf.0.sm1.145" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:07.025 | info | State value to set for "wolf.0.sm1.144" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:06.844 | info | State value to set for "wolf.0.sm1.143" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:06.671 | info | State value to set for "wolf.0.sm1.142" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:06.491 | info | State value to set for "wolf.0.sm1.141" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:04.724 | warn | State value to set for "wolf.0.sm1.138" has value "-40" less than min "0"
wolf.0 | 2022-04-24 17:34:01.734 | warn | State "wolf.0.sm1.135" has no existing object, this might lead to an error in future versions
wolf.0 | 2022-04-24 17:34:01.551 | warn | State value to set for "wolf.0.mm1.120" has value "-40" less than min "0"
wolf.0 | 2022-04-24 17:34:01.380 | warn | State value to set for "wolf.0.mm1.119" has value "-40" less than min "0"
wolf.0 | 2022-04-24 17:34:01.220 | info | State value to set for "wolf.0.mm1.118" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:01.052 | info | State value to set for "wolf.0.mm1.117" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:34:00.719 | warn | State value to set for "wolf.0.mm1.115" has value "-40" less than min "0"
wolf.0 | 2022-04-24 17:34:00.561 | warn | State "wolf.0.mm1.114" has no existing object, this might lead to an error in future versions
wolf.0 | 2022-04-24 17:33:56.379 | info | State value to set for "wolf.0.bm1.64" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.377 | info | State value to set for "wolf.0.bm1.63" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.375 | info | State value to set for "wolf.0.bm1.62" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.316 | info | State value to set for "wolf.0.bm1.61" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.220 | info | State value to set for "wolf.0.bm1.61" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.218 | info | State value to set for "wolf.0.bm1.60" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:56.216 | info | State value to set for "wolf.0.bm1.59" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:51.796 | warn | State "wolf.0.bm1.53" has no existing object, this might lead to an error in future versions
wolf.0 | 2022-04-24 17:33:51.579 | info | State value to set for "wolf.0.hg1.12" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:51.482 | info | State value to set for "wolf.0.hg1.12" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:51.481 | info | State value to set for "wolf.0.hg1.11" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:51.479 | info | State value to set for "wolf.0.hg1.10" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:51.330 | info | State value to set for "wolf.0.hg1.9" has to be type "string" but received type "boolean"
wolf.0 | 2022-04-24 17:33:50.085 | warn | State "wolf.0.hg1.1" has no existing object, this might lead to an error in future versions
 
Apollon77 commented 2 years ago

Interesting ... I changed nothing ... only added logs :-)

Can you please create a new issue for the errors of datatypes, seems there arer some wrong values :-(