I added position options for covers now - but my guess is, that 0 and 100% is on the wrong side. let me know 
I also tried to add the missing knx devices you listed above as switches and sensors.
@Nicola_Trussardi: Yes - I totally forgot: of course you need a computer - like a raspberry - to run home-assistant. I thought you asked, if you would need a raspberry additionally to have access to the vimar bus. so user pod is right.
I have not yet been able to load the latest version but I have looked at the âcover.pyâ file.
and ⌠youâre right. the right way is:
fully open = 0%
fully closed = 100%
âEDITâ
I loaded the new version but it returns this error when I try to set the shutters to a certain opening
Thanks for the report. Should be fixed.
My python validator is currently not working⌠thus all those errors.
ok. in fact I did the update and it stopped detecting the shutters with the percentage command. while the simple ones (only up and down) still work.
red: percentage controll
green: only up&down
Any error messages?
yesâŚ
this:
and this:
2020-09-25 09:58:29 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/update_coordinator.py", line 118, in _handle_refresh_interval
await self.async_refresh()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/update_coordinator.py", line 192, in async_refresh
update_callback()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
self._async_write_ha_state()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 322, in _async_write_ha_state
attr.update(self.state_attributes or {})
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/cover/__init__.py", line 204, in state_attributes
current = self.current_cover_position
File "/home/homeassistant/.homeassistant/custom_components/vimar_platform/cover.py", line 64, in current_cover_position
return 100 - self.get_state('position')
TypeError: unsupported operand type(s) for -: 'int' and 'str'
I tried to open and close the shutters. the command is received correctly but home assistant does not update the status and reports the entity as disabled
uploaded a new version.
@pod in regards of the thermostats: do yours work now as expected? switching between heating, cooling and off mode?
Hi guys, first of all i have to congrat with you all, really great job! I buyed a Pi4 and tried to installa HA, configured Vimar andâŚit worked!!! (it took me almost 4 hours to do 
first time for me with a Raspberry) Thanks a lot, i can control lights and thermostats! I also linked for Alexa and voice commands for light works great!
Iâm trying to understand how it works, but seems all goodâŚthe only problem i have is that i canât see controls of roller shutters, i canât see in the list.
And also in the Vimar By Web i had some âscenarioâ (switch on all light on first floor, shitch off all lights, all roller shutters up, all roller shutters down) and they donât work anymore (i tried to update again in the By Me the database without successâŚi see that scenario in the list of HA (switch.off_luci for example which should turn off all lights) but they donât work, and now also in the Vimar webpage (or app)
Now i asked my electrician to send me the XML of my house and i will try to reinstall in the Vimar Server, letâs hope!
Hello
I loaded the latest version and now the thermostats and shutters seem to be working correctly.
Only one thermostat, the external one, is not detected correctly. I think because instead of using the internal probe it uses an external one.
I am attaching the attributes below:
external thermostat, not recognized
Row000005: '22734','forzatura off','-1','0'
Row000006: '22736','allarme_massetto','-1','0'
Row000007: '22738','regolazione','-1','0'
Row000008: '22742','modalita_fancoil','-1','0'
Row000009: '22744','velocita_fancoil','-1','0'
Row000010: '22746','funzionamento','-1','6'
Row000011: '22754','setpoint','-1','20.00'
Row000012: '22763','temporizzazione','-1','1'
Row000013: '22775','temperatura_misurata','-1','15.10'
Row000014: '22780','stato_boost on/off','-1','0'
Row000015: '22781','stato_principale_condizionamento on/off','-1','0'
Row000016: '22782','stato_principale_riscaldamento on/off','-1','0'
Row000017: '23448','uscita4','-1','non_utilizzata'
Row000018: '23449','uscita3','-1','non_utilizzata'
Row000019: '23450','uscita2','-1','non_utilizzata'
Row000020: '23451','uscita1','-1','non_utilizzata'
Row000022: '77148','T1','-1',''
Row000023: '77149','T2','-1',''
Row000024: '77150','T3','-1',''
garage thermostat, recognized (for comparison)
Row000069: '61608','forzatura off','-1','0'
Row000070: '61610','allarme_massetto','-1','0'
Row000071: '61612','regolazione','-1','2'
Row000072: '61616','modalita_fancoil','-1','0'
Row000073: '61618','velocita_fancoil','-1','0'
Row000074: '61620','funzionamento','-1','6'
Row000075: '61628','setpoint','-1','40.00'
Row000076: '61636','temporizzazione','-1','1'
Row000077: '61647','temperatura_misurata','-1','22.80'
Row000078: '61650','stato_boost on/off','-1','0'
Row000079: '61651','stato_principale_condizionamento on/off','-1','0'
Row000080: '61652','stato_principale_riscaldamento on/off','-1','0'
Row000081: '62460','uscita4','-1','non_utilizzata'
Row000082: '62461','uscita3','-1','non_utilizzata'
Row000083: '62462','uscita2','-1','non_utilizzata'
Row000084: '62463','uscita1','-1','non_utilizzata'
Row000085: '77253','T1','-1',''
Row000086: '77254','T2','-1',''
Row000087: '77255','T3','-1',''
errore in HA
2020-09-29 11:02:00 DEBUG (SyncWorker_62) [custom_components.vimar_platform.vimarlink] get_remote_devices started - from 0 to 300
2020-09-29 11:02:01 WARNING (SyncWorker_62) [custom_components.vimar_platform.vimarlink] Unknown object returned from web server: CH_HVAC / Esterno - Clima
2020-09-29 11:02:01 DEBUG (SyncWorker_62) [custom_components.vimar_platform.vimarlink] Unknown object has states: {'forzatura off': {'status_id': '22734', 'status_value': '0', 'status_range': ''}, 'allarme_massetto': {'status_id': '22736', 'status_value': '0', 'status_range': 'min=0|max=1'}, 'regolazione': {'status_id': '22738', 'status_value': '0', 'status_range': ''}, 'modalita_fancoil': {'status_id': '22742', 'status_value': '0', 'status_range': 'min=0|max=1'}, 'velocita_fancoil': {'status_id': '22744', 'status_value': '0', 'status_range': 'min=0|max=100'}, 'funzionamento': {'status_id': '22746', 'status_value': '6', 'status_range': ''}, 'setpoint': {'status_id': '22754', 'status_value': '20.00', 'status_range': 'min=-273|max=670760'}, 'temporizzazione': {'status_id': '22763', 'status_value': '1', 'status_range': 'min=0|max=65535'}, 'temperatura_misurata': {'status_id': '22775', 'status_value': '14.40', 'status_range': 'min=-273|max=670760'}, 'stato_boost on/off': {'status_id': '22780', 'status_value': '0', 'status_range': 'min=0|max=1'}, 'stato_principale_condizionamento on/off': {'status_id': '22781', 'status_value': '0', 'status_range': 'min=0|max=1'}, 'stato_principale_riscaldamento on/off': {'status_id': '22782', 'status_value': '0', 'status_range': 'min=0|max=1'}, 'uscita4': {'status_id': '23448', 'status_value': 'non_utilizzata', 'status_range': 'principale_riscaldamento=0|principale_condizionamento=0|boost_riscaldamento=0|boost_condizionamento=0'}, 'uscita3': {'status_id': '23449', 'status_value': 'non_utilizzata', 'status_range': 'principale_riscaldamento=0|principale_condizionamento=0|boost_riscaldamento=0|boost_condizionamento=0'}, 'uscita2': {'status_id': '23450', 'status_value': 'non_utilizzata', 'status_range': 'principale_riscaldamento=0|principale_condizionamento=0|boost_riscaldamento=0|boost_condizionamento=0'}, 'uscita1': {'status_id': '23451', 'status_value': 'non_utilizzata', 'status_range': 'principale_riscaldamento=0|principale_condizionamento=0|boost_riscaldamento=0|boost_condizionamento=0'}}
Another problem concerns the scenarios created by vimar.
The scenarios are recognized by HA as âswitchesâ but in reality, for the Vimar server, they are single impulses. When you try to activate a scenario in HA, nothing happens and it remains blocked on ON.
Attributes below:
Row000001: 'ID','NAME','STATUS_ID','CURRENT_VALUE'
Row000002: '229','_DPAD_DBCONSTANT_VIMAR_BYME_TRIGGEROBJECT_VIDEOMESSAGE_UNHANDLED','-1','0'
Row000003: '265','_DPAD_DBCONSTANT_VIMAR_BYME_TRIGGEROBJECT_SENSORS_HUMIDITY_ALARM','-1','0'
Row000004: '270','_DPAD_DBCONSTANT_VIMAR_BYME_TRIGGEROBJECT_SAI2_LOG_ALARM','-1','1'
Row000005: '1160','indice','-1','9'
Row000006: '1161','comando','-1','1'
Row000007: '31561','_DPAD_PRODUCT_VIMARBYME_CERTIFICATE_TRIGGER','-1','0'
Unfortunately I havenât had time yet to test the knx components you have integrated. I will do it as soon as possible.
I see - I will add CH_HVAC next. it seems they do have the same attributes.
about the scenes - you are right. I added them as switches - didnât use them so far but only just now saw, that there is a platform for scenes already in hass - iâll have a look at that as well.
Hello everybody. Thanks for what you do. I am new to this world. anyway, I have a system Vimar by me but with web server 01946 (light version) version 2.6. I bought a raspberry PI4 8gb and installed home assistant 64bit, but I cannot install the vimar integration. Can you kindly post a video for all beginners like me? Thanks a lot anyway. I just canât. This is the error I find
Logger: homeassistant.setup
Source: custom_components/vimar_platform/init.py:118
First occurred: 21:18:10 (1 occurrences)
Last logged: 21:18:10
Error during setup of component vimar_platform
Traceback (most recent call last):
File â/usr/src/homeassistant/homeassistant/setup.pyâ, line 213, in _async_setup_component
result = await task
File â/config/custom_components/vimar_platform/init.pyâ, line 118, in async_setup
raise PlatformNotReady
homeassistant.exceptions.PlatformNotReady
Please help me. Im becoming crazy
Hello,
I am not sure if this integration will work with 01946 - as far as I know we only tested it on 01945.
the PlatformNotReady exception is thrown when the login to the webserver does not work properly. This could be either an invalid url/user or password - or the login process to the web server light version is different.
how does your vimar_platform part of the configuration.yaml look like? did you check the example configurations on the github page: https://github.com/h4de5/home-assistant-vimar#problems-with-ssl-connection ?
Good morning. Thanks for the reply. I tried to insert all the âvimar platformâ configurations including the http one, but nothing. Iâll try to install everything again, even raspberry (where I had some problems and maybe the problem is him. Maybe?).
Hereâs what happened to me
Can these problems cause the vimar platform to not work?
If I go to raspberry on integrations - entities I see this Invalid config message - The following integrations and platforms could not be set up: - [vimar_platform] (https://github.com/h4de5/home-assistant-vimar) Please check your config .
I kindly ask you to help me step by step
Thanks a lot
unfortunatelly I canât really help you with the home-assistant setup itself. I have not setup Samba or duckdns for my installation, sorry. If the forum does not yield any help for you, you may try out other community support options here: https://www.home-assistant.io/help/
Grazie Comunque. Continuo a provare e se riesco a far funzionare tutto con il web server 01946, vi aggiorno. Ciao
Grazie molto 
the integration distinguishes now between normal switches and scenes
Hello.
I also tested the latest update and everything works very well. The scenarios work perfectly. And now it also recognizes the external thermostat that it did not recognize before. Great!
I noticed that when I go to deactivate the auxiliary heating this error comes out:
Traceback (most recent call last):
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/websocket_api/commands.py", line 143, in handle_call_service
connection.context(msg),
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/core.py", line 1335, in async_call
task.result()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/core.py", line 1370, in _execute_service
await handler.func(service_call)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity_component.py", line 205, in handle_service
self._platforms.values(), func, call, required_features
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 470, in entity_service_call
future.result() # pop exception if have
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/entity.py", line 655, in async_request_call
await coro
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/helpers/service.py", line 507, in _handle_entity_call
await result
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/climate/__init__.py", line 526, in async_service_aux_heat
await entity.async_turn_aux_heat_off()
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/climate/__init__.py", line 462, in async_turn_aux_heat_off
await self.hass.async_add_executor_job(self.turn_aux_heat_off)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.7/site-packages/homeassistant/components/climate/__init__.py", line 458, in turn_aux_heat_off
raise NotImplementedError()
NotImplementedError
âŚstill great work Andi!
according to the vimar docs, the aux heater is a read only attribute, so you can only see if the heater is activated or off - but cannot change it. Is this true or are you able to change the status using the vimar webserver?