ziv1234 / hass_dynalite_component Goto Github PK

I noticed an issue with changing names for entities, it won't "refresh" on rename.

For example, when i played with covers one was named cover.x
after i successfully set it up i changed name to cover.kitchen and set up additional covers.
New covers showed up on next restart but the first one instead of cover.kitchen was still cover.x
It is something i noticed many times in setting up this component and regulary "flushed" (erased all items) in core.device_registry file.
After deleting that item (or all since it was easier), new item is named OK on next restart.

Is component still using MQTT ?
If so, which topic ?

I tried with parameters "discovery_topic:" and "device_topic:" but it shows error, like invalid parameters.

Trying to get this component working on a fresh install of HassOS on a Raspberry PI 3 B+

Need bit more explanation on cover subtype, not sure what factor and max/min means.

My covers take two switches, one for up and other for down. Nothing smart.
I just take care that DDRC units don't ask up and down in the same time, since that can happen because Dynalite doesn't understand covers.

At least, that is what i know.

Is there any better way to do covers in Dynalite ?
Because of this limitations, i use timedcover which is also here on github.
Would be much better if Dynalite have something on its own.

Thanks

I thought you might want to know

Regarding presets.. when i look at:
https://www.home-assistant.io/integrations/scene/
Scenes in HA look as same thing like presets in Dynalite.

Programming all the scenes would be real PITA but earlier when i communicated with Troy it was interesting to try to import logical XML which is easily exported from Philips Envision?
I'm zero in coding and i understand this xml, so believe it is not that complicated to make component use this file.
I exported my setup, here is a link:
https://github.com/uzelac/hass-dynalite-component-support/blob/master/Uzelac_Logical.xml

The way i see it, it brings two extra benefits:

1. user get nice names for all those channels AND presets from naming scheme in Dynalite Envision which is much easier than naming in HA.
2. it can make link between channels and preset which we have now. At the moment, when one use presets in HA, lights will go on but HA won't know state of specific channels. To be more descriptive:

• at the moment, when i start preset " all living room lights ON 100%" two ligts in living room will go on, as preset
• HA will, through component, tell Dynalite to start preset which will turn on two living room lights and that is OK
• What is not OK is that HA will signal in its GUI and engine that specific Preset is ON, but won't know state of independent channels, they will be show as 0% even though they are 100% :)

Vice versa, if you, through specific channel controls, turn all lights off, preset will stay ON even though it is not true.
This thing is a bit of PITA, for me at least. I do use Presets mostly, but often i get this "no-sync" errors.

To be very clear, this component is already great, so don't think I'm not grateful :).
I would like to see it better, if possible. I'm no coder, unfortunately :/

Is it too difficult to configure fan cards in Dynalite as as a 4 preset fan template in the way a room is?1 Area, 4 presets, High/Medium/Low/Off

Error doing job: Task exception was never retrieved
8:47 PM /usr/src/homeassistant/homeassistant/core.py (ERROR) - message first occurred at 8:20 PM and shows up 303 times

Error doing job: Task exception was never retrieved

Traceback (most recent call last):
File "/usr/local/lib/python3.7/asyncio/coroutines.py", line 120, in coro
res = func(*args, **kw)
File "/usr/local/lib/python3.7/site-packages/dynalite_lib/dynet.py", line 414, in _receive
"{:02x}".format(ord(c)) for c in self._inBuffer[:8]
File "/usr/local/lib/python3.7/site-packages/dynalite_lib/dynet.py", line 414, in
"{:02x}".format(ord(c)) for c in self._inBuffer[:8]
TypeError: ord() expected string of length 1, but int found

Hello! Thanks for your work. Are there any plans to add motion sensors to the supported Home Assistant device types?