Closed geeewizzz closed 4 years ago
The naming is pretty random at the moment, suggestions appreciated. Or did you want it to be switch
instead of light
?
I think it's technically possible. If the datapoints file is exported in the DPL format, some topology is included, which might make it possible to infer how things are connected. However, I have no documentation of that file format, and I haven't attempted to reverse engineer it, so for the time being, you have to connect them manually.
Can you see in the logs if it's attempting to send messages to the actuators? It certainly seems like it should work, but I haven't fiddled with generic_thermostat
, so I don't know if it's sending something strange. Does turning actuators on/off manually in the Home Assistant UI work?
2020/04/14 07:11:01 topic: xcomfort/22/set/switch, message: true 2020/04/14 07:11:02 rx: [c11670000100000000461004] 2020/04/14 07:11:02 Device 5733608 (channel 0-'1.etg liten gang vk') sent message (battery mains-powered, signal normal, cyclic false) status switched on 2020/04/14 07:11:30 topic: xcomfort/22/set/switch, message: false 2020/04/14 07:11:31 rx: [c11670000000000000431006] 2020/04/14 07:11:31 Device 5733608 (channel 0-'1.etg liten gang vk') sent message (battery mains-powered, signal good, cyclic false) status switched off
So manually turning it on off in "generic thermostat" works fine, but turning up the wanted temperature does nothing it seems. I'll play around with other thermostats and see if they work differently.
Could be that generic thermostat would play nicer with a switch instead of a light. I'll test and see later today.
By the way, did you turn the thermostat on (click the little flame)?
Ah damn, now i feel stupid. Thought that was "heater on/off". It works. I thought that flame would come on when i turned the desired temp over the current sensor temp.
Can I claim confusing UX? :)
No worries, took me ten minutes to figure that out too. 🥇 Agreed, HA has a ways to go wrt. usability still.
Possibly another dumb question, when restarting my home assistant all my devices and entities from this addon become unavailable, it seems i need to restart the addon manually for them to come back. Is this something I can configure somewhere to avoid?
I see the same issues here; could be the MQTT discovery that's somehow running into racing issues. I'll investigate when I have time.
A work-around:
Seems like additional sensors from Room Controller touch is not being added as entities? Added all sensors from 1.etg_dusj/bad now and seems like it is ignoring some of them.
The RCT has the following sensors : Temperatur (which is the devices own temperature sensor, room temp) Fuktighet (measures humidity in the room) Ekstern sensor(in my case measures the floor temp)
In addition 2 buttons that you can also connect.
It seems MRF has limitations here, for the RCT sensors it can only connect to 1 controller. I didnt realize that until this weekend. So since mine were connected to Sensio from before, I removed the sensio connection for this one device and now connected the all sensors to the USB stick instead.
Another bug in Eaton MRF: for some temperature sensors it seems to on random want to set them to send switching commands even though I specify in MRF that I want it to send temperature commands.
I have changed this manually in the data point file where I figured it is the first 0/1 that is controlling this. Since the switching command is not supported anyway, maybe it is wise to assume that to be a mistake and import it as a temperature sensor anyway? (and just print a warning in the logfile or something)
Created separate issues for the comments above.
I'm a bit of a noob when it comes to HA though, but let me try.
Seems to be working, other than the fact if I turn up the wanted temp to a temp above the actual temp right now it doesn't start heating (which I hoped it would).