Serving with custom engine

Hello,
I checked the pipeline example where you use custom engine, but it is not very complete. What if I want to run normal pytorch inference without any engine?
Is it also possible to implement my own Rest API (e.g. Flask) or at least have more control how I process my inferences? In your README.md, it says: Customizable RestAPI for serving (i.e. allow per model pre/post-processing for easy integration). How can a really customize the RestAPI?
Thanks!
Bruno

Hi @Bunoviske

I checked the pipeline example where you use custom engine
Yes it is in he to do list to add a specific custom model serving example. I'll update here once it is up

What if I want to run normal pytorch inference without any engine?
So you can just do "pytorch inference" as a custom engine (basically import pytorch and run the model. That said Triton is so much faster than just using vanilla pytorch for inference, and this is basically out of the box. Any reason for manually running the model inference ?

Customizable RestAPI for serving (i.e. allow per model pre/post-processing for easy integration). How can a really customize the RestAPI?
The idea is the fact you can have any python code as pre/post processing, which really customize the entire API.  For example, RestAPI gets a url as string, and the preprocessing would download it, return a numpy object, then the inference is done on the image.
What exactly are you aiming for with the customization?

Hello Martin!
No particular reason, I just wanted to understand how flexibel ClearML Serving is. Regarding your second question, I think I already got good outcome from our slack conversation and here: #32
Once you have the new example with custom engine, let me know! Thanks :)

Quick update @Bunoviske
You can now find a custom serving example here 😃


Investigate Superset DASHBOARD_RBAC

Per a removed TODO in the code:
https://github.com/openedx/tutor-contrib-oars/blob/0019a992e333a5871e056c7f4968e6088aae5474/tutoroars/templates/oars/apps/pythonpath/superset-dashboard.py#L66
# TODO: Enable feature flag DASHBOARD_RBAC, and set dashboard.roles = ["Open edX"]
# Consider finishing https://github.com/opus-42/superset-api-client/pull/31

This relates generally to our authorization story and making sure users only see what they're supposed to. @pomegranited probably has more relevant context.

Hi there! Can you shed some light on this issue so we can help @pomegranited? Thanks!

@mariajgrimaldi @bmtcril I think that enabling DASHBOARD_RBAC lets us set up roles that are allowed to access specific Dashboards (and their charts and datasets), so that different roles can see different Dashboards depending on what they care about.  E.g., System Admins could see system-monitoring dashboards, Program Admins can see program-level dashboards, etc.
However the docs say that if DASHBOARD_RBAC  is enabled:

Granting a role access to a dashboard will bypass dataset level checks.

So we need to make sure that enabling DASHBOARD_RBAC doesn't bypass our Row Level Security, which currently is how we restrict access to data to course staff.
https://github.com/opus-42/superset-api-client/pull/31 is about ensuring that we can pass a list of roles when importing a Dashboard into the Superset API.

@bmtcril What if we define a Jinja template that fetches current user permission from the MySQL DB and uses it in the dashboard queries to filter the data based on the current user? This would allow us to enable DASHBOARD_RBAC for different roles, and keep the amount of dashboard static (not using the Cairn approach).
cc @pomegranited @mariajgrimaldi any thoughts?

@Ian2012 I definitely don't want to tie us directly to the MySQL db in any way. I think we can refresh permissions periodically using SSO and still keep the DASHBOARD_RBAC?

@bmtcril Can this be closed or is anything missing?

I think this is in a decent place, if there are bugs we can open a new issue.


Subverse #2

Hello. Thank you for answering the last issue and updating, even though it was not related to my game, I hope in a future version you will be able to edit such text. But I found another text that looks different and I would also like to change it through your program, but so far there is no such possibility.
Text:
Adaptive Language Learning (A.L.L.)
APEX Industries
Archives, The Imperium
Assie
Azzorion, Lord
Bacchus
Battle of Nü Vegas, The
and etc.
Screenshots:
Text in hex editor:

Text in game:

File in your program (latest version):

Files:
Codex.zip

@TheDarkness1994
Change edit by hex editor to make sure

@TheDarkness1994
Change it by hex editor to make sure

@TheDarkness1994
any news?

@TheDarkness1994 any news?

I'm sorry. A new version of the game was released on Steam, I had to deal with new files, I didn’t sleep for two days. Now I'll write what's what

New version files:
Codex.zip

I tried to change only one word with another program, that's what happened.

I only changed one word:
English
Adaptive Language Learning (A.L.L.)
Russian
Адаптивное Изучение Языков (А.И.Я)

@TheDarkness1994 Try new version V1.4 Close the issue if your problem fixed

Thank you very much. Everything works well.


Add HmIP-PCBS Device support

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Please use the datapoints.py script to gather the details for the device and post them here as a gist.

Hello Daniel,
please find below the gist Link to the HmIP-PCBS-Adapter. Hope this works for you.
https://gist.github.com/FlavorFx/876b72dc60adcb01e79892ae64ee7853
Best regards,
Michael

Am 01.11.2018 um 22:35 schrieb Daniel Perna<EMAIL_ADDRESS>Please use the datapoints.py https://github.com/danielperna84/pyhomematic/blob/master/datapoints.py script to gather the details for the device and post them here as a gist https://gist.github.com/.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-435195564, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0FDpm2Y00ZTxT9K14-_Dof6_osVeks5uq2ksgaJpZM4YE4tY.

Please post the complete output. This truncated JSON can't be automatically parsed, which makes it hard for me to look through it, and I don't want to read through >12.000 lines of JSON.
And also please describe what the device does so I know what I should look for.

Hello Daniel,
please find below the link to the entire JSON file:
https://gist.github.com/FlavorFx/451874be9d2688244299b6274cbf209c https://gist.github.com/FlavorFx/451874be9d2688244299b6274cbf209c
Please have a look to the HmIP- PCBS device. It's a PCB 1 channel switch. It’s also includes a repeater function because HmIP does not support a mesh function.
Please let me know if you would work for you.
Best regards,
Michael

Am 06.11.2018 um 01:13 schrieb Daniel Perna<EMAIL_ADDRESS>Please post the complete output. This truncated JSON can't be automatically parsed, which makes it hard for me to look through it, and I don't want to read through >12.000 lines of JSON.
And also please describe what the device does so I know what I should look for.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-436084242, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0Ko3TmMOVbvVlEKfirS_nEwPJ9t5ks5usNQggaJpZM4YE4tY.

Please add the following class to the actors.py file (part of pyhomematic) that your Home Assistant installation is using:
class IPKeySwitch(GenericSwitch, HMEvent, HelperActionPress, HelperRssiPeer):
    """
    PCB Switch turning attached device on or off.
    """

    def __init__(self, device_description, proxy, resolveparamsets=False):
        super().__init__(device_description, proxy, resolveparamsets)

        self.EVENTNODE.update({"PRESS_SHORT": [1],
                               "PRESS_LONG": [1]})

    @property
    def ELEMENT(self):
        return [2]

And near the bottom of the file add the line:
"HmIP-PCBS": IPKeySwitch,

Then in your Home Assistant code you have to tell it to make use of this new device class. This is done here. Add an entry for IPKeySwitch.
Once that is done and you restart Home Assistant you should see the switch in the UI and be able to use it. I also noticed, that the device has PRESS_SHORT and PRESS_LONG, which indicates that it somehow also has buttons that can be pressed. These events should arrive at Home Assistant as well.
Can you confirm that my proposed code is working?

Hallo Daniel,
thanks for the code snippet. Please give me a hint where I can find these files to edit on my hass.io http://hass.io/ installation.
Best regards,
Michael

Am 08.11.2018 um 23:54 schrieb Daniel Perna<EMAIL_ADDRESS>Please add the following class to the actors.py file (part of pyhomematic) that your Home Assistant installation is using:
class IPKeySwitch(GenericSwitch, HMEvent, HelperActionPress, HelperRssiPeer):
"""
PCB Switch turning attached device on or off.
"""
def __init__(self, device_description, proxy, resolveparamsets=False):
    super().__init__(device_description, proxy, resolveparamsets)

    self.EVENTNODE.update({"PRESS_SHORT": [1],
                           "PRESS_LONG": [1]})

@property
def ELEMENT(self):
    return [2]

And near the bottom of the file add the line:
"HmIP-PCBS": IPKeySwitch,
Then in your Home Assistant code you have to tell it to make use of this new device class. This is done here https://github.com/home-assistant/home-assistant/blob/05eac915d16fa5108a6a5892d5f94c808a597f91/homeassistant/components/homematic/__init__.py#L67. Add an entry for IPKeySwitch.
Once that is done and you restart Home Assistant you should see the switch in the UI and be able to use it. I also noticed, that the device has PRESS_SHORT and PRESS_LONG, which indicates that it somehow also has buttons that can be pressed. These events should arrive at Home Assistant as well.
Can you confirm that my proposed code is working?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437186012, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0JiQIZKPo-JaZThVFTTc6BE0_MWsks5utLYdgaJpZM4YE4tY.

Have a look at this thread. The first post has instructions on how to get shell access to the Home Assistant container. And alternative (if you speak german) would be my short summary on how to set up a virtual machine where access to the source files is much easier.

Ok. I setup a VM with Debian 9.6 (debian-9.6.0-amd64-netinst.iso) and followed your instructions. After entering hass I got:
2018-11-11 13:45:13 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/home/michael/home-assistant/homeassistant/components/apple_tv.py", line 170, in atv_discovered
CONF_START_OFF: False
File "/home/michael/home-assistant/homeassistant/components/apple_tv.py", line 192, in _setup_atv
import pyatv
File "/home/michael/home-assistant/lib/python3.5/site-packages/pyatv/init.py", line 12, in
from pyatv.pairing import PairingHandler
File "/home/michael/home-assistant/lib/python3.5/site-packages/pyatv/pairing.py", line 11, in
import netifaces
ImportError: No module named 'netifaces'
any idea?

Am 10.11.2018 um 21:35 schrieb Daniel Perna<EMAIL_ADDRESS>Have a look at this https://community.home-assistant.io/t/protip-how-to-get-shell-in-actual-hassio-container/48760 thread. The first post has instructions on how to get shell access to the Home Assistant container. And alternative (if you speak german) would be my short summary https://github.com/danielperna84/pyhomematic/issues/170#issuecomment-433523436 on how to set up a virtual machine where access to the source files is much easier.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437619384, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0EBomEKzzv159c_2kCYE5ZlQNdfJks5utziZgaJpZM4YE4tY.

Did you activate the venv? (source bin/activate in the instructions)
And executed the setup? (script/setup in the instructions)
Those steps should install all needed dependencies. If you did that, you
can try "pip3 install netifaces" to manually install the missing dependency.
Am So., 11. Nov. 2018 um 14:07 Uhr schrieb FlavorFx <
<EMAIL_ADDRESS>
Ok. I setup a VM with Debian 9.6 (debian-9.6.0-amd64-netinst.iso) and
followed your instructions. After entering hass I got:
2018-11-11 13:45:13 ERROR (MainThread) [homeassistant.core] Error doing
job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
File "/home/michael/home-assistant/homeassistant/components/apple_tv.py",
line 170, in atv_discovered
CONF_START_OFF: False
File "/home/michael/home-assistant/homeassistant/components/apple_tv.py",
line 192, in _setup_atv
import pyatv
File
"/home/michael/home-assistant/lib/python3.5/site-packages/pyatv/init.py",
line 12, in
from pyatv.pairing import PairingHandler
File
"/home/michael/home-assistant/lib/python3.5/site-packages/pyatv/pairing.py",
line 11, in
import netifaces
ImportError: No module named 'netifaces'
any idea?

Am 10.11.2018 um 21:35 schrieb Daniel Perna<EMAIL_ADDRESS>Have a look at this <
https://community.home-assistant.io/t/protip-how-to-get-shell-in-actual-hassio-container/48760>
thread. The first post has instructions on how to get shell access to the
Home Assistant container. And alternative (if you speak german) would be my
short summary <
https://github.com/danielperna84/pyhomematic/issues/170#issuecomment-433523436>
on how to set up a virtual machine where access to the source files is much
easier.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <
https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437619384>,
or mute the thread <
https://github.com/notifications/unsubscribe-auth/ASbx0EBomEKzzv159c_2kCYE5ZlQNdfJks5utziZgaJpZM4YE4tY
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437668844,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDehkgcPOurhvmjoWmvxPpTiKEU3TXCks5uuCEkgaJpZM4YE4tY
.

Add an entry for IPKeySwitch.

did you mean 'IPKeySwitch‘ instead of IPKeySwitch?
I can see the switch in HA but it doesn’t work yet.
2018-11-11 15:09:44 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.setValue: STATE on<PHONE_NUMBER>E763:2 Exception: <Fault -5: 'Invalid parameter or value'>
any idea?

Am 08.11.2018 um 23:54 schrieb Daniel Perna<EMAIL_ADDRESS>Please add the following class to the actors.py file (part of pyhomematic) that your Home Assistant installation is using:
class IPKeySwitch(GenericSwitch, HMEvent, HelperActionPress, HelperRssiPeer):
"""
PCB Switch turning attached device on or off.
"""
def __init__(self, device_description, proxy, resolveparamsets=False):
    super().__init__(device_description, proxy, resolveparamsets)

    self.EVENTNODE.update({"PRESS_SHORT": [1],
                           "PRESS_LONG": [1]})

@property
def ELEMENT(self):
    return [2]

And near the bottom of the file add the line:
"HmIP-PCBS": IPKeySwitch,
Then in your Home Assistant code you have to tell it to make use of this new device class. This is done here https://github.com/home-assistant/home-assistant/blob/05eac915d16fa5108a6a5892d5f94c808a597f91/homeassistant/components/homematic/__init__.py#L67. Add an entry for IPKeySwitch.
Once that is done and you restart Home Assistant you should see the switch in the UI and be able to use it. I also noticed, that the device has PRESS_SHORT and PRESS_LONG, which indicates that it somehow also has buttons that can be pressed. These events should arrive at Home Assistant as well.
Can you confirm that my proposed code is working?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437186012, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0JiQIZKPo-JaZThVFTTc6BE0_MWsks5utLYdgaJpZM4YE4tY.

No, it has to be without the Quotation marks. If you see the entity in the UI it generally is fine. It's just the code that is not correct.
I think we you should just try it manually. Open a Python 3 Shell and execute the following:
#<PHONE_NUMBER>E763 is the address of your device
from xmlrpc.client import ServerProxy
p = ServerProxy("http://rasp-ip:2010")
# Should return True or False, depending on the state of the device
p.getValue("0004570993E763:2", "STATE")
# Should turn the device on
p.setValue("0004570993E763:2", "STATE", True)
# Should turn the device off
p.setValue("0004570993E763:2", "STATE", False)

If that doesn't work, try to replace the :2 with :1 or :3 or :4 to see if any of the other channels controls the switch.

… but when I changed it without quotation marks and error msg came up:
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/home/michael/home-assistant/homeassistant/components/homematic/init.py", line 67, in
'IPKeySwitchPowermeter', IPKeySwitch],
NameError: name 'IPKeySwitch' is not defined
Are you really sure to leave off the quotation marks?

Am 11.11.2018 um 15:38 schrieb Daniel Perna<EMAIL_ADDRESS>No, it has to be without the Quotation marks. If you see the entity in the UI it generally is fine. It's just the code that is not correct.
I think we you should just try it manually. Open a Python 3 Shell and execute the following:
0004570993E763 is the address of your device
from xmlrpc.client import ServerProxy
p = ServerProxy("http://rasp-ip:2010")
Should return True or False, depending on the state of the device
p.getValue("0004570993E763:2", "STATE")
Should turn the device on
p.setValue("0004570993E763:2", "STATE", True)
Should turn the device off
p.setValue("0004570993E763:2", "STATE", False)
If that doesn't work, try to replace the :2 with :1 or :3 or :4 to see if any of the other channels controls the switch.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437675364, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0OeOQR21H5FL1qunng8hIUGE-nyLks5uuDZ2gaJpZM4YE4tY.

… but when I changed it without quotation marks and error msg came up:
File "/usr/lib/python3.5/importlib/init.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 986, in _gcd_import
File "", line 969, in _find_and_load
File "", line 958, in _find_and_load_unlocked
File "", line 673, in _load_unlocked
File "", line 673, in exec_module
File "", line 222, in _call_with_frames_removed
File "/home/michael/home-assistant/homeassistant/components/homematic/init.py", line 67, in
'IPKeySwitchPowermeter', IPKeySwitch],
NameError: name 'IPKeySwitch' is not defined
Are you really sure to leave off the quotation marks?

Am 11.11.2018 um 15:38 schrieb Daniel Perna<EMAIL_ADDRESS><EMAIL_ADDRESS>No, it has to be without the Quotation marks. If you see the entity in the UI it generally is fine. It's just the code that is not correct.
I think we you should just try it manually. Open a Python 3 Shell and execute the following:
0004570993E763 is the address of your device
from xmlrpc.client import ServerProxy
p = ServerProxy("http://rasp-ip:2010 http://rasp-ip:2010/")
Should return True or False, depending on the state of the device
p.getValue("0004570993E763:2", "STATE")
Should turn the device on
p.setValue("0004570993E763:2", "STATE", True)
Should turn the device off
p.setValue("0004570993E763:2", "STATE", False)
If that doesn't work, try to replace the :2 with :1 or :3 or :4 to see if any of the other channels controls the switch.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437675364, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0OeOQR21H5FL1qunng8hIUGE-nyLks5uuDZ2gaJpZM4YE4tY.

Oh, I thought you meant the line in actors.py. There it is without the quotation marks. In the Home Assistant code its with quotation marks.

ok, channel #3 controls the switch. What’s next?

I also noticed, that the device has PRESS_SHORT and PRESS_LONG, which indicates that it somehow also has buttons that can be pressed
yes, there is small a PCB switch on board.

Am 11.11.2018 um 18:08 schrieb Daniel Perna<EMAIL_ADDRESS>Oh, I thought you meant the line in actors.py. There it is without the quotation marks. In the Home Assistant code its with quotation marks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437686923, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0L1avit6zylShgPGHeywm-Uztq8jks5uuFmNgaJpZM4YE4tY.

finally, it works fine with this code change. Can you confirm it?
class IPKeySwitch(GenericSwitch, HMEvent, HelperActionPress, HelperRssiPeer):
"""
PCB Switch turning attached device on or off.
"""
def __init__(self, device_description, proxy, resolveparamsets=False):
    super().__init__(device_description, proxy, resolveparamsets)

    self.EVENTNODE.update({"PRESS_SHORT": [1],
                           "PRESS_LONG": [1]})

@property
def ELEMENT(self):
    return [3]

Am 11.11.2018 um 18:32 schrieb Michael Schwär<EMAIL_ADDRESS>ok, channel #3 controls the switch. What’s next?

I also noticed, that the device has PRESS_SHORT and PRESS_LONG, which indicates that it somehow also has buttons that can be pressed
yes, there is small a PCB switch on board.

Am 11.11.2018 um 18:08 schrieb Daniel Perna<EMAIL_ADDRESS><EMAIL_ADDRESS>Oh, I thought you meant the line in actors.py. There it is without the quotation marks. In the Home Assistant code its with quotation marks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437686923, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0L1avit6zylShgPGHeywm-Uztq8jks5uuFmNgaJpZM4YE4tY.

Yes, after your statement that channel 3 toggles the switch that's exactly the change that I would have made for you to test.
Next up would be setting Home Assistant to a more verbose log-mode (debug, maybe info is enough as well) so you can see the events that Home Assistant is processing. As you press the button on the device, you should see messages to the device pop up in the log.
Though the question remains, if this is really useful. I expect the buttons usually won't be pressed often. Those events are more for real button devices (physical light switches etc.). But it doesn't hurt to support the button press. So if it works that would be great.

please find attached the debug log. I pressed short on, short off, long on and long off.
Does it look right?
BTW: during boot up I noticed these messages from different sensors as well. Hope you can check this as well.

Am 12.11.2018 um 01:06 schrieb Daniel Perna<EMAIL_ADDRESS>Yes, after your statement that channel 3 toggles the switch that's exactly the change that I would have made for you to test.
Next up would be setting Home Assistant to a more verbose log-mode (debug, maybe info is enough as well) so you can see the events that Home Assistant is processing. As you press the button on the device, you should see messages to the device pop up in the log.
Though the question remains, if this is really useful. I expect the buttons usually won't be pressed often. Those events are more for real button devices (physical light switches etc.). But it doesn't hurt to support the button press. So if it works that would be great.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-437718497, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0OKQUWRhXUeGxCwQljW5ihCh3nXlks5uuLttgaJpZM4YE4tY.

2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = CONFIG_PENDING, value = False
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=CONFIG_PENDING, value=False
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = RSSI_DEVICE, value = -82
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=RSSI_DEVICE, value=-82
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = DUTY_CYCLE, value = False
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=DUTY_CYCLE, value=False
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = UNREACH, value = False
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=UNREACH, value=False
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION_STATUS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = STATE, value = True
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=STATE, value=True
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION, value = 2
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION, value=2
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = PROCESS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION_STATUS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:42:56 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION_STATUS' value: 0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = STATE, value = True
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=STATE, value=True
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:42:56 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'STATE' value: True
2018-11-12 23:42:56 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:56.833132+00:00>, entity_id=switch.0004570993e763, old_state=<state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:49.759348+00:00>>
2018-11-12 23:42:56 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.140322695025104] Sending {'type': 'event', 'event': {'context': {'user_id': None, 'id': '6604052f55774f6b879e17923bcf7758'}, 'origin': 'LOCAL', 'event_type': 'state_changed', 'time_fired': datetime.datetime(2018, 11, 12, 22, 42, 56, 833153, tzinfo=), 'data': {'old_state': <state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:49.759348+00:00>, 'new_state': <state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:56.833132+00:00>, 'entity_id': 'switch.0004570993e763'}}, 'id': 2}
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION, value = 2
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION, value=2
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:42:56 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION' value: 2
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = PROCESS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:42:56 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'PROCESS' value: 0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION_STATUS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = STATE, value = False
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = PROCESS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION_STATUS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = STATE, value = False
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = PROCESS, value = 0
2018-11-12 23:42:56 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:42:56 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = CONFIG_PENDING, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=CONFIG_PENDING, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = RSSI_DEVICE, value = -73
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=RSSI_DEVICE, value=-73
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = DUTY_CYCLE, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=DUTY_CYCLE, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = UNREACH, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=UNREACH, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = STATE, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = PROCESS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:02 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION_STATUS' value: 0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = STATE, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:02 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'STATE' value: False
2018-11-12 23:43:02 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:02.376439+00:00>, entity_id=switch.0004570993e763, old_state=<state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:56.833132+00:00>>
2018-11-12 23:43:02 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.140322695025104] Sending {'type': 'event', 'event': {'context': {'user_id': None, 'id': '81cd8f01973d4a7b9df229563b46b3bd'}, 'origin': 'LOCAL', 'event_type': 'state_changed', 'time_fired': datetime.datetime(2018, 11, 12, 22, 43, 2, 376459, tzinfo=), 'data': {'old_state': <state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:42:56.833132+00:00>, 'new_state': <state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:02.376439+00:00>, 'entity_id': 'switch.0004570993e763'}}, 'id': 2}
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:02 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION' value: 0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = PROCESS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:02 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'PROCESS' value: 0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = STATE, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = PROCESS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = STATE, value = False
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = PROCESS, value = 0
2018-11-12 23:43:02 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:02 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = CONFIG_PENDING, value = False
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=CONFIG_PENDING, value=False
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = RSSI_DEVICE, value = -73
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=RSSI_DEVICE, value=-73
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = DUTY_CYCLE, value = False
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=DUTY_CYCLE, value=False
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = UNREACH, value = False
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=UNREACH, value=False
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = STATE, value = True
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=STATE, value=True
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION, value = 2
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION, value=2
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = PROCESS, value = 0
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:10 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION_STATUS' value: 0
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = STATE, value = True
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=STATE, value=True
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:10 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'STATE' value: True
2018-11-12 23:43:10 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:10.981155+00:00>, entity_id=switch.0004570993e763, old_state=<state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:02.376439+00:00>>
2018-11-12 23:43:10 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.140322695025104] Sending {'type': 'event', 'event': {'context': {'user_id': None, 'id': 'ecfcf6d598164f9683e7f9d46e62ad77'}, 'origin': 'LOCAL', 'event_type': 'state_changed', 'time_fired': datetime.datetime(2018, 11, 12, 22, 43, 10, 981176, tzinfo=), 'data': {'old_state': <state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:02.376439+00:00>, 'new_state': <state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:10.981155+00:00>, 'entity_id': 'switch.0004570993e763'}}, 'id': 2}
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION, value = 2
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION, value=2
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:10 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION' value: 2
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = PROCESS, value = 0
2018-11-12 23:43:10 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:10 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:10 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'PROCESS' value: 0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = STATE, value = False
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = PROCESS, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = STATE, value = False
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = PROCESS, value = 0
2018-11-12 23:43:11 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:11 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = CONFIG_PENDING, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=CONFIG_PENDING, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = RSSI_DEVICE, value = -72
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=RSSI_DEVICE, value=-72
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = DUTY_CYCLE, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=DUTY_CYCLE, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:0, value_key = UNREACH, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:0, interface_id=homeassistant-ip, key=UNREACH, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = STATE, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = SECTION, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:2, value_key = PROCESS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:2, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:19 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION_STATUS' value: 0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = STATE, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: on>>
2018-11-12 23:43:19 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'STATE' value: False
2018-11-12 23:43:19 DEBUG (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: new_state=<state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:19.881109+00:00>, entity_id=switch.0004570993e763, old_state=<state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:10.981155+00:00>>
2018-11-12 23:43:19 DEBUG (MainThread) [homeassistant.components.websocket_api.http.connection.140322695025104] Sending {'type': 'event', 'event': {'context': {'user_id': None, 'id': '3f3b1461bd944b648606a6693fb90a46'}, 'origin': 'LOCAL', 'event_type': 'state_changed', 'time_fired': datetime.datetime(2018, 11, 12, 22, 43, 19, 881130, tzinfo=), 'data': {'old_state': <state switch.0004570993e763=on; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:10.981155+00:00>, 'new_state': <state switch.0004570993e763=off; friendly_name=0004570993E763, id=0004570993E763, interface=ip, rssi=-82 @ 2018-11-12T22:43:19.881109+00:00>, 'entity_id': 'switch.0004570993e763'}}, 'id': 2}
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = SECTION, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:19 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'SECTION' value: 0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:3, value_key = PROCESS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:3, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback <bound method HMDevice._hm_event_callback of <Entity<PHONE_NUMBER>E763: off>>
2018-11-12 23:43:19 DEBUG (Thread-7) [homeassistant.components.homematic]<PHONE_NUMBER>E763 received event 'PROCESS' value: 0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = STATE, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = SECTION, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:4, value_key = PROCESS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:4, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION_STATUS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION_STATUS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = STATE, value = False
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=STATE, value=False
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = SECTION, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=SECTION, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic._hm] RPCFunctions.event: interface_id = homeassistant-ip, address =<PHONE_NUMBER>E763:5, value_key = PROCESS, value = 0
2018-11-12 23:43:19 INFO (Thread-7) [pyhomematic.devicetypes.generic] HMGeneric.event: address=0004570993E763:5, interface_id=homeassistant-ip, key=PROCESS, value=0
2018-11-12 23:43:19 DEBUG (Thread-7) [pyhomematic.devicetypes.generic] HMDevice.event: Using callback functools.partial(<function _hm_event_handler at 0x7f9f81453730>, <homeassistant.core.HomeAssistant object at 0x7f9f95f56240>, 'ip')
2018-11-12 23:29:02 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:02 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: STATE on 00085709A3EBE5:4 Exception: <Fault -5: 'Unknown Parameter value for value key: STATE'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOWBAT on 0000D8A99798AB:1 Exception: <Fault -5: 'Unknown Parameter for value key: LOWBAT'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: STATE on 0000D8A99798AB:1 Exception: <Fault -5: 'Unknown Parameter value for value key: STATE'>
2018-11-12 23:29:03 ERROR (Thread-6) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOWBAT on 0000D7099A4029:1 Exception: <Fault -5: 'Unknown Parameter for value key: LOWBAT'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: POWER on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: POWER'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: CURRENT on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: CURRENT'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOWBAT on 00109709A8F405:1 Exception: <Fault -5: 'Unknown Parameter for value key: LOWBAT'>
2018-11-12 23:29:03 ERROR (Thread-6) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOWBAT on 0000D8A99798DF:1 Exception: <Fault -5: 'Unknown Parameter for value key: LOWBAT'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: ENERGY_COUNTER on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: ENERGY_COUNTER'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: VOLTAGE on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: VOLTAGE'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: SET_POINT_MODE on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: SET_POINT_MODE'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: FREQUENCY on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: FREQUENCY'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on 001157099AE4AD:4 Exception: <Fault -5: 'Unknown Parameter for value key: WORKING'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_PEER on 001157099AE4AD:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_PEER'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on 001157099AE57F:4 Exception: <Fault -5: 'Unknown Parameter for value key: WORKING'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LEVEL on 001157099AE4AD:4 Exception: <Fault -5: 'Unknown Parameter value for value key: LEVEL'>
2018-11-12 23:29:03 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on 001157099AE5AC:4 Exception: <Fault -5: 'Unknown Parameter for value key: WORKING'>
2018-11-12 23:29:03 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_PEER on 001157099AE5AC:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_PEER'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_PEER on 001157099AE57F:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_PEER'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: WORKING on 001157099AE494:4 Exception: <Fault -5: 'Unknown Parameter for value key: WORKING'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOW_BAT on 000E5709A11EE8:0 Exception: <Fault -5: 'Unknown Parameter value for value key: LOW_BAT'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: SET_POINT_TEMPERATURE on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: SET_POINT_TEMPERATURE'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: ACTUAL_TEMPERATURE on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: ACTUAL_TEMPERATURE'>
2018-11-12 23:29:03 ERROR (Thread-3) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_PEER on 001157099AE494:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_PEER'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: HUMIDITY on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: HUMIDITY'>
2018-11-12 23:29:03 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:03 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:03 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: CURRENT on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: CURRENT'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:03 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: VOLTAGE on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: VOLTAGE'>
2018-11-12 23:29:03 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:04 ERROR (Thread-5) [pyhomematic.devicetypes.generic] HMGeneric.getValue: POWER on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: POWER'>
2018-11-12 23:29:04 ERROR (Thread-4) [pyhomematic.devicetypes.generic] HMGeneric.getValue: ENERGY_COUNTER on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: ENERGY_COUNTER'>
2018-11-12 23:29:04 ERROR (Thread-6) [pyhomematic.devicetypes.generic] HMGeneric.getValue: SET_POINT_MODE on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: SET_POINT_MODE'>
2018-11-12 23:29:04 ERROR (Thread-6) [pyhomematic.devicetypes.generic] HMGeneric.getValue: LOW_BAT on 000E5709A11EE8:0 Exception: <Fault -5: 'Unknown Parameter value for value key: LOW_BAT'>
2018-11-12 23:29:04 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: RSSI_DEVICE on 00085709A3EBE5:0 Exception: <Fault -5: 'Unknown Parameter value for value key: RSSI_DEVICE'>
2018-11-12 23:29:04 ERROR (Thread-2) [pyhomematic.devicetypes.generic] HMGeneric.getValue: FREQUENCY on 00085709A3EBE5:7 Exception: <Fault -5: 'Unknown Parameter value for value key: FREQUENCY'>
2018-11-12 23:29:04 ERROR (Thread-6) [pyhomematic.devicetypes.generic] HMGeneric.getValue: HUMIDITY on 000E5709A11EE8:1 Exception: <Fault -5: 'Unknown Parameter value for value key: HUMIDITY'>

please find attached the debug log. I pressed short on, short off, long on and long off.

Nope, nothing. So maybe they don't work. I guess we'll leave them out for now.

during boot up I noticed these messages from different sensors as well. Hope you can check this as well.

The log you have posted is huge, so I don't know what you mean. At first sight there's nothing unusual. Just a bunch of devices where the RSSI isn't implemented correctly.

There are a lot of "Unknown Parameter value for value key: “ messages from different devices in the boot log.txt file...

Am 13.11.2018 um 22:44 schrieb Daniel Perna<EMAIL_ADDRESS>please find attached the debug log. I pressed short on, short off, long on and long off.
Nope, nothing. So maybe they don't work. I guess we'll leave them out for now.
during boot up I noticed these messages from different sensors as well. Hope you can check this as well.
The log you have posted is huge, so I don't know what you mean. At first sight there's nothing unusual. Just a bunch of devices where the RSSI isn't implemented correctly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#issuecomment-438449432, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0MqBReDv7xZXK7StQwxoRKbtIZj7ks5uuz05gaJpZM4YE4tY.

Yes. For some that's normal. There's that one power meter sensor for example that has different operation modes. Depending on which one you use different parameters are used. Those messages only appear once during bootup because Home Assistant tries to get the current values. But detecting the mode is resource consuming, which is why we just let it have the error. It doesn't harm.
And for stuff like RSSI_DEVICE, RSSI_PEER and LOW_BAT it's just a matter of correct implementation. It doesn't harm if it's the incorrect paramter for the device. But if you report what device types you have that produce these errors, then it can be fixed. But if you report, please don't just post the big log. Just post the relevant lines, or which devices has which error (like HmIP-ABCD reports an error on RSSI_PEER).

Are you going to release the PCBS Device support in the Homematic/init.py in the upcoming release? Do I need to do something to support you?

Am 15.11.2018 um 23:21 schrieb Daniel Perna<EMAIL_ADDRESS>Closed #178 https://github.com/danielperna84/pyhomematic/issues/178 via 57c37e6 https://github.com/danielperna84/pyhomematic/commit/57c37e6d1b15e6106e6b3ab1b8f7f78349cbad37.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/danielperna84/pyhomematic/issues/178#event-1969909874, or mute the thread https://github.com/notifications/unsubscribe-auth/ASbx0J_0snT66pJXIEfhOhc_v-UFG9WAks5uvej9gaJpZM4YE4tY.

The PR for Home Assistant has already been merged: https://github.com/home-assistant/home-assistant/pull/18499
I think it was too late to get included in the next Home Assistant release. If so, then it will be in the next version after that. So there's nothing else to do than wait. 😉


Expose IncomingFrame

This will allow code written in async/await style, e.g.
const Promise = require('bluebird');
const stompit = require('stompit');
Promise.promisifyAll(stompit);

async function asyncEntry() {
    while (true) {
        let client = await stompit.connectAsync(connectOptions);
        let message = await client.subscribeAsync(subscribeHeaders);
        let body = await message.readStringAsync('utf-8');
        console.log(body);
    }
}

@gdaws can this get merged? I desparately need to use this library with async/await


Adding MongoDb replica set support

What does this PR do?
Adding an option to initialise MongoDb as a single node replica set.
To do this we need a keyfile generated with limited permissions, and add a wait strategy which will initialise the replica set on startup
Why is it important?
Some application would expect the Mongo server to be running in a replica set to improve resiliency, and would set read/write strategies on their commands, which will fail if a replica set is not initialised.
Related issues
There is already an open discussion about it, with some suggestions but no working solution. This PR provides a working implementation and closes #1154
How to test this PR
The single node replica set should behave mostly the same as a single mongo instance.
When running in a replica set, you can also call rs commands to get the status of the replica set.
e.g. the rs.status() command will display the status of the replica set.

The last test run should have been green, but somehow the container has crashed/stopped? Could someone try and re-run the last test run to see if it was an issue in the GitHub runner?

@HofmeisterAn I managed to re-run the tests- looks like an intermittent issue in GitHub actions. The tests are green now, and I've been using this code in my integration tests already
Let me know if anything else is needed to have this merged

Thank you for the pull request 🙏. I will try to test and review it in the coming days. I am aware there are a couple of module pull requests waiting to be reviewed. I have not forgotten them; I am addressing them one by one, prioritizing potential bugs and features that benefit the base library.

No rush, thank you very much @HofmeisterAn!

Hi, it's been almost two months since the PR was created. Is there anything we can do to help speed up the process to approve and merge this?

Hi, I am using it now via
_mongoDbContainer = new MongoDbBuilder()
.WithReplicaSet()
.WithImage("mongo:latest")
.WithUsername("")
.WithPassword("")
.WithPortBinding(_port, true)
.WithWaitStrategy(Wait.ForUnixContainer()
.UntilPortIsAvailable(_mongoPort))
.Build();
Because I've added transactions to my project, but running it this way makes mongodb fail on startup
the overall issue is
Message:
System.TimeoutException : A timeout occurred after 30000ms selecting a server using CompositeServerSelector{ Selectors = WritableServerSelector, LatencyLimitingServerSelector{ AllowedLatencyRange = 00:00:00.0150000 }, OperationsCountServerSelector }. Client view of cluster state is { ClusterId : "2", Type : "ReplicaSet", State : "Connected", Servers : [{ ServerId: "{ ClusterId : 2, EndPoint : "<IP_ADDRESS>:52699" }", EndPoint: "<IP_ADDRESS>:52699", ReasonChanged: "Heartbeat", State: "Connected", ServerVersion: 7.0.0, TopologyVersion: { "processId" : ObjectId("66d8951c02314d40f9304eac"), "counter" : NumberLong(0) }, Type: "ReplicaSetGhost", WireVersionRange: "[0, 21]", LastHeartbeatTimestamp: "2024-09-04T17:13:22.0736177Z", LastUpdateTimestamp: "2024-09-04T17:13:22.0736185Z" }] }.
Version="3.10.0"
Here is a file with full log from start to end. Sadly I am not good enough with mongodb/docker to say what's going wrong with it, I can just state that if I remove the WithReplicaSet() - tests that don't do transactions will go green, and everything works as a charm with this config I stated above
mongodblog.txt

Modules are pre-configured. If you are using them, it is not necessary to override the default configurations, such as wait strategies, etc. Doing so can even be a disadvantage and may break the module. Instead, use:
new MongoDbBuilder().WithReplicaSet().Build();

Override modules only if you are confident in what you are doing.

it is not necessary to override the default configurations

Didn't know that. Actually this helped and worked, thank you very much, looks much cleaner


Login Button

This login button needs to use the google API
https://www.npmjs.com/package/react-google-login
Restrict to cedarville.edu emails.
Once you login and get your JWT check it against the backend. If fail, go to register page
An example: https://github.com/CreativeSolutionsGroup/smart-events-admin/blob/master/src/components/Login.js

https://dev.to/sivaneshs/add-google-login-to-your-react-apps-in-10-mins-4del

Where did y'all get on this?

We implemented the component on the Dashboard and created a unique clientID. We are still working out logistics and understanding the process as a whole, but we have a decent foundation.


Add more samples to the web site

There is a couple of nice samples in the samples folder that are not currently on the web page. Adding a sample to the web page should be fairly easy and it is a fantastic way to learn Fable and contribute at the same time.
I recently added the D3 map and the commit is a good example of what needs to be done (it also does a few bug fixes you can ignore).

the d3map.fsx file is a good example of how to write docs (there are a few required things at the top)
in docs.fsx, you need to add the folder to the samples

And that is pretty much it - generally, follow what one of the other examples does. After modifying docs.fsx you can run:
./build.sh GenerateDocs
./build.sh BrowseDocs

The first will generate all docs (it compiles all samples, so do this just once). The second one starts local server and updates the samples when you change them. (On windows, use build.cmd)

I had to make a couple of changes to make it work on my machine but after that I just added the three.js tutorial and is like magic! Thanks a lot for your hard work, Tomas!

Just to complete Tomas' explanation:

The HTML for the sample will be generated automatically, but you can still keep some parts in the HTML head or body by wrapping the elements as can be seen here and here.
The first lines of the fsx script should also contain info for the generation of the HTML: the title, the tagline (or subtitle), the CSS inline **style** of the container that'll hold the running sample and an **intro** which comes right below the title.


Add phpcbf as app

phpcbf is widely used with phpcs, and can be installed just same as phpcs.
$ phpbrew app get phpcbf
Downloading https://squizlabs.github.io/PHP_CodeSniffer/phpcbf.phar via curl extension
[==================================================================] 511.50/511.50KB 100%
Changing permissions to 0755
Downloaded at /Users/username/.phpbrew/bin/phpcbf

Coverage decreased (-0.4%) to 51.172% when pulling ecdd82190d3bcf37b8957e6771a4bbaa3f2cfed7 on ikuwow:add_app_phpcbf into e10237ffb7ccd8acb38d2c0d44f9ed7acd994b91 on phpbrew:master.

Coverage increased (+0.01%) to 51.545% when pulling 1cd3857939f7d3364dfd934d2e825fa206bf83c9 on ikuwow:add_app_phpcbf into 5d24143cc30542f3381a5eeccaf930f35cc489ae on phpbrew:master.

Coverage increased (+0.01%) to 51.545% when pulling 111965e474a75a5c2265e7f80a8b389e043d0c8a on ikuwow:add_app_phpcbf into 7c7ca6bdec671dbfbfe0e8f1e7c29478604a762b on phpbrew:master.

Coverage increased (+0.01%) to 51.557% when pulling fd347764e0b5a74e9070333b67e24608bb73b246 on ikuwow:add_app_phpcbf into 03db92e5f07804496b8b8df1c3f83c1e328023db on phpbrew:master.

Does it have bugs? Or does it violate any guidelines?

@ikuwow it was conflicted, let's see if it's working.

Coverage increased (+1.2%) to 52.196% when pulling aeefee2fdbbe25e7040117d5d08c4efc92563830 on ikuwow:add_app_phpcbf into 29e0a11d82951fbd620e81af7bc8fbfe1a9c665e on phpbrew:master.

Coverage increased (+1.2%) to 52.196% when pulling aeefee2fdbbe25e7040117d5d08c4efc92563830 on ikuwow:add_app_phpcbf into 29e0a11d82951fbd620e81af7bc8fbfe1a9c665e on phpbrew:master.