Closed KL-AU-S closed 5 years ago
frankjoke
commented
5 years ago I cannot test anything because I am abroad for some weeks still. Just one question, you talk about two separate remote adapters you want to use? I see from above listing that they should have different IP's. I hope they do not have same MAC addresses, but usually they should not...
Anyhow, it's strange but I unluckily cannot test two RM's because I own only one and I am not at home on my test system as well!
xmace
commented
5 years ago Any progress on this?
KL-AU-S
commented
5 years ago No, no progress. In the meanwhile i have 3 RM3 Mini running and for each one i have to use a seperate instance of the adapter.
frankjoke
commented
5 years ago Klaus, I tried to test but do not have two such devices, I have only multiple SP1's to test and they have all different addresses and running together since a year.
In your listing above I see in the log on two different IP addresses (192-168-0-192 and 192-168-0-190) and both of them seem to have a different mac address (37:27:c0:0:a8:c0, 37:27:be:0:a8:c0)!
The adapter sets something offline if it does not answer or replies just with errors. Both devices have code 10039 (hex 2737) which says it's an RM Mini. So everything looks OK but it seems that if two are online one stops answering or is answering!
Did you give them different names on your router? It seems they have no name because the IP is used.
Can you try do give them different network names?
I will work later this month on other features of the adapter and generate a test version which shows the messages sent to and received from the devices. Will inform you when it's available on git to look on the phenomenon.
frankjoke
commented
5 years ago Can you test V2Beta from Git? See in forum how to install.
KL-AU-S
commented
5 years ago I switch over to node-red and broadlink/MQTT. Thanks for your help.
I have the problem that two of these adapter will not work at the same time. When i power off one of them the other one works. When both are on one off them will not reachable. I have made a logfile:
broadlink2.0 2018-10-22 20:06:05.183 debug Change RM:192-168-0-190.notReachable to true with ack: true broadlink2.0 2018-10-22 20:06:05.178 warn Device RM:192-168-0-190 not reachable broadlink2.0 2018-10-22 20:05:35.101 debug Change RM:192-168-0-192.notReachable to false with ack: true broadlink2.0 2018-10-22 20:05:33.093 info 1 were not found: RM:192-168-0-190 broadlink2.0 2018-10-22 20:05:33.093 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-192'. broadlink2.0 2018-10-22 20:05:33.091 debug Poll every 30 secods. broadlink2.0 2018-10-22 20:05:33.074 warn device RM:192-168-0-190 not found, please rescan later again or delete it! It was: 192.168.0.190,IPv4,80,128,10039,rm,RM:192-168-0-190,RM Mini,37:27:be:0:a8:c0 broadlink2.0 2018-10-22 20:05:33.060 debug Adapter has 16 old states! broadlink2.0 2018-10-22 20:05:32.951 debug Change _NewDeviceScan to false with ack: true broadlink2.0 2018-10-22 20:05:27.880 info Device RM:192-168-0-192 dedected: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0 broadlink2.0 2018-10-22 20:05:27.694 debug Change _NewDeviceScan to true with ack: true broadlink2.0 2018-10-22 20:05:27.495 debug Config IP-Address end to remove: .fritz.box broadlink2.0 2018-10-22 20:05:27.495 info Discover UDP devices for 10sec on broadlink2.0 broadlink2.0 2018-10-22 20:05:27.494 debug broadlink2 received 2328 objects with config ip,scenes,switches,poll,lang broadlink2.0 2018-10-22 20:05:25.071 debug Adapter broadlink2.0 starting. broadlink2.0 2018-10-22 20:05:25.070 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0 host.DESKTOP-006CT2J 2018-10-22 20:05:20.988 info instance system.adapter.broadlink2.0 started with pid 6240 host.DESKTOP-006CT2J 2018-10-22 20:05:18.501 info instance system.adapter.broadlink2.0 terminated with code null () host.DESKTOP-006CT2J 2018-10-22 20:05:18.501 warn instance system.adapter.broadlink2.0 terminated due to SIGTERM host.DESKTOP-006CT2J 2018-10-22 20:05:18.424 info stopInstance system.adapter.broadlink2.0 killing pid 1300 host.DESKTOP-006CT2J 2018-10-22 20:05:18.424 info stopInstance system.adapter.broadlink2.0 host.DESKTOP-006CT2J 2018-10-22 20:05:18.423 info object change system.adapter.broadlink2.0 broadlink2.0 2018-10-22 20:05:10.590 debug system.adapter.admin.0: logging true admin.0 2018-10-22 20:05:10.579 warn Disable logging, because no one socket connected broadlink2.0 2018-10-22 20:04:21.003 debug system.adapter.admin.0: logging false broadlink2.0 2018-10-22 20:02:50.914 debug Change RM:192-168-0-190.Temperature to 13.8 with ack: true broadlink2.0 2018-10-22 20:02:22.906 debug Change RM:192-168-0-192.notReachable to true with ack: true broadlink2.0 2018-10-22 20:02:22.898 warn Device RM:192-168-0-192 not reachable broadlink2.0 2018-10-22 20:02:20.921 debug Change RM:192-168-0-190.Temperature to 13.9 with ack: true broadlink2.0 2018-10-22 20:01:52.839 debug Change RM:192-168-0-190.notReachable to false with ack: true broadlink2.0 2018-10-22 20:01:51.299 debug Change RM:192-168-0-190.Temperature to 13.8 with ack: true broadlink2.0 2018-10-22 20:01:50.848 info 1 were not found: RM:192-168-0-192 broadlink2.0 2018-10-22 20:01:50.847 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-190'. broadlink2.0 2018-10-22 20:01:50.845 debug Poll every 30 secods. broadlink2.0 2018-10-22 20:01:50.813 warn device RM:192-168-0-192 not found, please rescan later again or delete it! It was: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0 broadlink2.0 2018-10-22 20:01:50.807 debug Adapter has 14 old states! broadlink2.0 2018-10-22 20:01:50.692 debug Change _NewDeviceScan to false with ack: true broadlink2.0 2018-10-22 20:01:45.898 debug Change RM:192-168-0-190.SendCode to ' ' with ack: true broadlink2.0 2018-10-22 20:01:45.854 debug Change RM:192-168-0-190.Learn to false with ack: true broadlink2.0 2018-10-22 20:01:45.824 debug Change RM:192-168-0-190 to false with ack: true broadlink2.0 2018-10-22 20:01:45.806 info Device RM:192-168-0-190 dedected: 192.168.0.190,IPv4,80,128,10039,rm,RM:192-168-0-190,RM Mini,37:27:be:0:a8:c0 broadlink2.0 2018-10-22 20:01:45.564 debug Change _NewDeviceScan to true with ack: true broadlink2.0 2018-10-22 20:01:45.338 debug Config IP-Address end to remove: .fritz.box broadlink2.0 2018-10-22 20:01:45.337 info Discover UDP devices for 10sec on broadlink2.0 broadlink2.0 2018-10-22 20:01:45.332 debug broadlink2 received 2323 objects with config ip,scenes,switches,poll,lang broadlink2.0 2018-10-22 20:01:42.368 debug Adapter broadlink2.0 starting. broadlink2.0 2018-10-22 20:01:42.356 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0 broadlink2.0 2018-10-22 20:01:42.181 debug statesDB connected broadlink2.0 2018-10-22 20:01:41.985 debug objectDB connected host.DESKTOP-006CT2J 2018-10-22 20:01:36.716 info instance system.adapter.broadlink2.0 started with pid 1300 host.DESKTOP-006CT2J 2018-10-22 20:01:34.226 info instance system.adapter.broadlink2.0 terminated with code null () host.DESKTOP-006CT2J 2018-10-22 20:01:34.225 warn instance system.adapter.broadlink2.0 terminated due to SIGTERM host.DESKTOP-006CT2J 2018-10-22 20:01:34.156 info stopInstance system.adapter.broadlink2.0 killing pid 4780 host.DESKTOP-006CT2J 2018-10-22 20:01:34.156 info stopInstance system.adapter.broadlink2.0 host.DESKTOP-006CT2J 2018-10-22 20:01:34.155 info object change system.adapter.broadlink2.0 admin.0 2018-10-22 20:00:37.121 warn Disable logging, because no one socket connected broadlink2.0 2018-10-22 20:00:34.560 info Adapter broadlink2.0 started and found 1 devices named 'RM:192-168-0-192'. broadlink2.0 2018-10-22 20:00:29.585 info Device RM:192-168-0-192 dedected: 192.168.0.192,IPv4,80,128,10039,rm,RM:192-168-0-192,RM Mini,37:27:c0:0:a8:c0 broadlink2.0 2018-10-22 20:00:29.185 info Discover UDP devices for 10sec on broadlink2.0 broadlink2.0 2018-10-22 20:00:23.486 info starting. Version 1.9.0 in C:/ioBroker/node_modules/iobroker.broadlink2, node: v8.12.0