You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used your nodes for a few days on node-red 0.20.x without any problems.
Great job, by the way.
After I upgraded to node-red 1.0 Kodi got caught in a rebbot loop, which could only be broken by disabling your nodes and a hard reset of Kodi.
This behavior couls easiely recreated by activating your nodes, primariely the kodi-out node.
Maybe the switch to (completely) asychronous messaging has something to do with it?
The text was updated successfully, but these errors were encountered:
have a similar problem, using node red 3.0.2 if kodi restarts for a reason not influenced by node-red after restarting it it is shutting down as soon as it connects to the network, if i stop node-red it starts normally after restarting node-red it works until the next crash of kodi (caused by current interruption or whatever else). is there something i can change (setting to not retain shutdown command?)
I used your nodes for a few days on node-red 0.20.x without any problems.
Great job, by the way.
After I upgraded to node-red 1.0 Kodi got caught in a rebbot loop, which could only be broken by disabling your nodes and a hard reset of Kodi.
This behavior couls easiely recreated by activating your nodes, primariely the kodi-out node.
Maybe the switch to (completely) asychronous messaging has something to do with it?
The text was updated successfully, but these errors were encountered: