Closed Lateadapter closed 12 months ago
Hi Steffen,
thx for the detailed description and analysis, which really makes it easier for me to understand and reproduce the issues. Also thx for the notice of the upcoming change in XML-API. As for the issues:
Best Regards
PS.: Grüße von Bayern nach Thüringen ;)
Hi Sebastian,
many thanks for the fast response. Regarding the issues...
Viele Grüße ! Steffen
Hi Steffen,
have a look at the new style single_line in latest version 1.1.3. Hope that's what you need for point 4.
Regards
Hallo Sebastian,
it works very well as expected. Many thanks for your effort!
Regards, Steffen
Hi Sebastian,
I just want to give a hint that actual there is an update for refactored XML-API, which very probably wont work together with the MMM-Homematic module: https://github.com/homematic-community/XML-API Hopefully you will find some time in future for diving in...
Best regards, Steffen
Hi Steffen,
I implemented the authentication for XML-API 2.x in the new version 1.2.0. Just create a token for the XML-API and add it as ccuXmlApiTokenId in your module config and you should be fine. Tested it with XML-API 2.1.
Best Regards
Hi Sebastian, tested with XML-API 2.2. - works perfect. Many thanks!
Steffen
@Sickboy78 and @spitzlbergerj
Hi both, first I want to thank you for providing such nice module. I have tried in recent weeks several capabilities to show on MM data from my "smart home zoo", e.g. MMM-MQTT, MMM-ioBroker and now also MMM-Homematic. I'm not at all a programmer. So far I faced many challenges in introducing customizations. In the end I was able to achieve the best results with your module. I particularly like the ability to use custom local icons. I'm running the MM in server mode as docker container on Synology NAS. Homematic is runnig as Raspberrymatic on Pi 3. The physical mirror itself is disconnected from integration and just using fullpageos on Raspi.
Following few issues, I faced:
After installation the module was shown on MM only with headline and permanent "loading ..." message. It took me days to find out that the cause of the problem was a security setup in the Homematic-GUI. The option "Redirect to https" under "System control/ Security..." need to be unchecked! Otherwise there won't be any connection to the XML-API. It doesn't matter, if in the MMM the configuration option "ccuProtocol" will be choosen "http://" or "https://" - the only working combination was "http:" in the module and the unchecked box in CCU.
Looking for the route cause of the issue above I found some important information about running refactoring activities of XML-API https://homematic-forum.de/forum/viewtopic.php?f=41&t=77234 It would be very pitty, if after introduction of announced XML-API update the MMM-Homematic Module won't work anymore. Hopefully you are trying to cover the compatibility in future as well.
Special types , like ä, ü, ö (Umlaute) or the degrees sign (°) were not shown correctly in the data point section independent from definition for "locale". I did solve that "quick and dirty" by choosing special characters according https://toolstud.io/web/charmap.php?filter=*
I would have one wish to consider for future development: Beside the styles "lines" and "tables" it would be nice to have the possibility to write few data points one after each other in one line. It would better use the entire space of an mirror region. The sample below I did generate with the MMM-ioBroker
Again many thanks for your work and best regards from Thuringia, Steffen