Phew, sorry I have no clue. Will take it to the team and hopefully somebody has an idea.
You did not change anything on the hardware. Just switching from v0.8 to 0.9 on your vm
-
Homeduino receiving not working (Possibly not Pimatic fault)
pimatic v0.9 has been released!
Support Pimatic and get some free stickers
Like us on Facebookmake it so !
-
Yeah, I’ll try with 0.8 again on the same image later on. Its a bit odd, since the protocols are picked up. I would understand if the RF input was something that couldnt be translated to a protocol. …
-
UPDATE!
I tested Device autodiscover today. When I add the devices with discovery, receiving the switches work!! When adding the exact same thing manually, it does not work. I will check tomorrow (late here hehe… ) if there is any difference in config.
So, Pimatic 0.9 on my VM is now proven to be working. Great thing, now I can start making my more reliable setup. I will keep you posted.
-
Below is the Device config that is done with Autodiscover (that id and name is so terrible! ), and receiving is working!
{ "class": "HomeduinoRFSwitch", "protocols": [ { "name": "switch1", "options": { "id": 12157118, "unit": 2 } } ], "id": "coco-technologies-d-io-chacon-intertechno-klikaanklikuit-nexa-switch", "name": "CoCo Technologies/D-IO (Chacon)/Intertechno/KlikAanKlikUit/Nexa (switch)" } ],
And here is the config that I add manually with GUI, Receiving not working
{ "id": "swi-1", "name": "Swi-1", "class": "HomeduinoRFSwitch", "protocols": [ { "name": "switch1", "options": { "id": "12157118", "unit": 2 }, "send": true, "receive": true } ] },
I will continue testing for some time, if something else comes up.
-
Hi all,
I had the same findings as kitsunen. The debug is found but the gui switch is not updated if the hardware switch is used.
Also the switch is working by adding it during auto discovery. The switch was still working if I entered another name/id during the auto discovery.br
Michael -
Hi,
seems I found the “missing link”: If we add the device manually than the id information is not only the number but “NUMBER”e.g.: “id”: "12157118"
instead of “id”: 12157118,hope this helps
Br
Mike -
Hi all,
still not working. Below you find my example of the auto discovery which is working:
{ "class": "HomeduinoRFSwitch", "protocols": [ { "name": "switch1", "options": { "id": 20251446, "unit": 10 } } ], "id": "rf-rolladen-schlafzimmer-up", "name": "Rf_Rolladen_Schlafzimmer_up" },
and the not working entry by manually adding the switch:
{ "class": "HomeduinoRFSwitch", "protocols": [ { "name": "switch1", "options": { "id": 20251446, "unit": 10 } } ], "id": "rfswitch-rolladen-schlafzimmer-up", "name": "RfSwitch_Rolladen_Schlafzimmer_up" },
-
@merphun They look pretty similar apart from id and name. Is the class entry in the working example the first one after the opening brace? Maybe it just got lost in copy & paste.
Maybe it is not possible to access the same switch with different IDs. Have you tried with the manual entry without the autodiscovered one?
diff tells me, they are the same except opening brace, id, name and some additional whitespaces in the last line after the comma in the auto discovery.
-
Hi Marie,
yes the first “{” is there and just got lost in c/p.
I tried the manual entry first and it never functioned. Afterwards (after reading the topic here) I tried the auto discovery for my RF Shutters and these switches worked flawless.
Afterwards I looked the two config sections up and found the difference regarding the id and sort order of class protocol lines. So I corrected this in the config by editing the config linesNow the situation is as you wrote…there is hardly a difference to find. If it’s just me I would say I messed something up but as the OP has very much the same issue and workaround it cannot be this simple
I tried now to delete the auto discovery switch to but this still made the manual entry not working.
Maybe autodiscovery writes information in a file besides the config or in another config part?
Thanks for your fast response
BR
Mike -
I’m sorry, but now I’m clueless what may be wrong. As far as I can see, auto discovery does not write in some side files. On the other hand I just took a quick glance at the source code and have only a vague idea which file to look in for. All I’m left with is the standard IT question: did you try to turn it off and on again? sorry
-
@merphun It should work. Restart pimatic and check log for errors in case it still does not work.
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law